[Touch-packages] [Bug 1943359] Re: Cherry-pick crypt_checksalt fix

2021-10-18 Thread Jeremy Bicha
** Changed in: pam (Ubuntu)
   Status: Incomplete => New

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

Title:
  Cherry-pick crypt_checksalt fix

Status in pam package in Ubuntu:
  New

Bug description:
  Please cherry-pick this commit (included in Debian's pam 1.4.0-10 or
  upstream 1.5.2)

  https://github.com/linux-pam/linux-pam/commit/980d90c9232fe5

  The pam upstream bug is
  https://github.com/linux-pam/linux-pam/issues/367

  I believe we need this fix before updating libxcrypt to 1:4.4.22-1

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


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


[Touch-packages] [Bug 1947452] [NEW] Please remove maliit from Ubuntu

2021-10-16 Thread Jeremy Bicha
Public bug reported:

Please remove maliit-framework & maliit-inputcontext-gtk from Ubuntu.

They have no reverse dependencies.

https://tracker.debian.org/pkg/maliit-framework was uploaded to Debian
experimental once but was removed.

I think the packages were added as part of the Unity 8 project and
aren't actively maintained in Ubuntu since Canonical stopped work there.

** Affects: maliit-framework (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: maliit-inputcontext-gtk (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: jammy

** Also affects: maliit-inputcontext-gtk (Ubuntu)
   Importance: Undecided
   Status: New

** Description changed:

- Please remove maliit-framework & maliit-context-gtk from Ubuntu.
+ Please remove maliit-framework & maliit-inputcontext-gtk from Ubuntu.
  
  They have no reverse dependencies.
  
  https://tracker.debian.org/pkg/maliit-framework was uploaded to Debian
  experimental once but was removed.
  
  I think the packages were added as part of the Unity 8 project and
  aren't actively maintained in Ubuntu since Canonical stopped work there.

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

Title:
  Please remove maliit from Ubuntu

Status in maliit-framework package in Ubuntu:
  New
Status in maliit-inputcontext-gtk package in Ubuntu:
  New

Bug description:
  Please remove maliit-framework & maliit-inputcontext-gtk from Ubuntu.

  They have no reverse dependencies.

  https://tracker.debian.org/pkg/maliit-framework was uploaded to Debian
  experimental once but was removed.

  I think the packages were added as part of the Unity 8 project and
  aren't actively maintained in Ubuntu since Canonical stopped work
  there.

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


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


[Touch-packages] [Bug 1472288] Re: Add additional attributes in /etc/os-release

2021-10-14 Thread Jeremy Bicha
Why do you want /etc/os-release to contain CPE_NAME?

It is an optional field and it seems easier to parse the other fields to
figure out that you are running Ubuntu 21.04.

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

Title:
  Add additional attributes in /etc/os-release

Status in base-files package in Ubuntu:
  Confirmed

Bug description:
  Please add 'CPE_NAME' and 'BUILD_ID' to /etc/os-release.

  More at http://www.freedesktop.org/software/systemd/man/os-
  release.html.

  I'm not sure BUILD_ID should be something like 'vivid' etc, but it
  would be a nice use. Or introduce a new attribute/value pair like

  NICKNAME_ID="vivid"

  No rush. Thanks for adopting this convention so quickly.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: base-files 7.2ubuntu9
  Uname: Linux 4.1.0-rc5carif-7-ga8b253b x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jul  7 10:26:02 2015
  Dependencies:
   
  InstallationDate: Installed on 2014-11-04 (245 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: base-files
  UpgradeStatus: Upgraded to vivid on 2015-04-25 (73 days ago)

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


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


[Touch-packages] [Bug 1944481] Re: Distrust "DST Root CA X3"

2021-10-09 Thread Jeremy Bicha
** No longer affects: ca-certificates (Fluxbuntu)

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

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

Title:
  Distrust "DST Root CA X3"

Status in ca-certificates package in Ubuntu:
  Fix Released
Status in ca-certificates source package in Trusty:
  Fix Released
Status in ca-certificates source package in Xenial:
  Fix Released
Status in ca-certificates source package in Bionic:
  Fix Released
Status in ca-certificates source package in Focal:
  Fix Released
Status in ca-certificates source package in Hirsute:
  Fix Released
Status in ca-certificates source package in Impish:
  Fix Released
Status in ca-certificates package in Debian:
  Unknown

Bug description:
  [Impact]

   * ca-certificates trusts the letsencrypt CA certificate "ISRG Root X1"
   * ca-certificates also trusts the CA certificate "DST Root CA X3" which 
cross-signs letencrypt CA
   * "DST Root CA X3" is about to expire, however it has issued an updated 
cross-signature to letsencrypt beyond its own expiry
   * This causes issues with older implementations of openssl & gnutls that 
reject such chains when offered to clients by servers.
   * We have provided fixes for openssl in xenial and gnutls in bionic/xenial, 
however trusty systems remain affected. Also any self built old copies of 
openssl/gnutls remain suspeptible to this expiry.
   * One solution is to blacklist the "DST Root CA X3" from the ca-certificates 
package as described at 
https://blog.devgenius.io/rhel-centos-7-fix-for-lets-encrypt-change-8af2de587fe4
 - connectivity to sites chained to "DST Root CA X3" will be unaffected, and 
servers that chain to both "ISRG Root X1" and "DST Root CA X3" should start to 
work unmodified.
   * This is similar to how this was handled for AddTrust before

  "* mozilla/blacklist.txt: blacklist expired AddTrust External Root
  CA."

  [Test Plan]

   * Install old/current ca-certificates faketime wget curl
  libcurl3-gnutls

  # faketime 2021-10-01 wget https://pskov.surgut.co.uk
  --2021-10-01 00:00:00--  https://pskov.surgut.co.uk/
  Resolving pskov.surgut.co.uk (pskov.surgut.co.uk)... 2a01:4f8:c17:3dd8::1, 
49.12.37.5
  Connecting to pskov.surgut.co.uk 
(pskov.surgut.co.uk)|2a01:4f8:c17:3dd8::1|:443... connected.
  ERROR: cannot verify pskov.surgut.co.uk's certificate, issued by 
'/C=US/O=Let\'s Encrypt/CN=R3':
    Issued certificate has expired.
  To connect to pskov.surgut.co.uk insecurely, use `--no-check-certificate'.

  # LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libcurl-gnutls.so.4 faketime 
2021-10-01 curl https://pskov.surgut.co.uk >/dev/null
    % Total% Received % Xferd  Average Speed   TimeTime Time  
Current
   Dload  Upload   Total   SpentLeft  Speed
    0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0
  curl: (60) SSL certificate problem: certificate has expired

   * Install new ca-certificates package

  # faketime 2021-10-01 wget https://pskov.surgut.co.uk
  --2021-10-01 00:00:00--  https://pskov.surgut.co.uk/
  Resolving pskov.surgut.co.uk (pskov.surgut.co.uk)... 2a01:4f8:c17:3dd8::1, 
49.12.37.5
  Connecting to pskov.surgut.co.uk 
(pskov.surgut.co.uk)|2a01:4f8:c17:3dd8::1|:443... connected.
  HTTP request sent, awaiting response... 200 OK
  Length: 612 [text/html]
  Saving to: 'index.html.3'

  100%[>] 612
  --.-K/s   in 0s

  2021-10-01 00:00:00 (71.7 MB/s) - 'index.html.3' saved [612/612]

   LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libcurl-gnutls.so.4 faketime 2021-10-01 
curl https://pskov.surgut.co.uk >/dev/null
    % Total% Received % Xferd  Average Speed   TimeTime Time  
Current
   Dload  Upload   Total   SpentLeft  Speed
  100   612  100   6120 0   5794  0 --:--:-- --:--:-- --:--:--  5828

  Download is successful.

  [Where problems could occur]

   * Connectivity to "DST Root CA X3" websites only, even under faketime
  set to dates prior to 30th of September 2021 will not work, as "DST
  Root CA X3" certificate is no longer installed. users should locally
  install and enable that CA certificate, or allow dangerous unverified
  connectivity to websites using expired CA certs.

  [Other Info]

   * Related openssl and gnutls28 bugs are
  https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1928989 and
  https://bugs.launchpad.net/ubuntu/+source/gnutls28/+bug/1928648

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


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

[Touch-packages] [Bug 1944481] Re: Distrust "DST Root CA X3"

2021-10-09 Thread Jeremy Bicha
** Bug watch added: Debian Bug tracker #995432
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995432

** Also affects: ca-certificates (Fluxbuntu) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995432
   Importance: Unknown
   Status: Unknown

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

Title:
  Distrust "DST Root CA X3"

Status in ca-certificates package in Ubuntu:
  Fix Released
Status in ca-certificates source package in Trusty:
  Fix Released
Status in ca-certificates source package in Xenial:
  Fix Released
Status in ca-certificates source package in Bionic:
  Fix Released
Status in ca-certificates source package in Focal:
  Fix Released
Status in ca-certificates source package in Hirsute:
  Fix Released
Status in ca-certificates source package in Impish:
  Fix Released
Status in ca-certificates package in Fluxbuntu:
  Unknown

Bug description:
  [Impact]

   * ca-certificates trusts the letsencrypt CA certificate "ISRG Root X1"
   * ca-certificates also trusts the CA certificate "DST Root CA X3" which 
cross-signs letencrypt CA
   * "DST Root CA X3" is about to expire, however it has issued an updated 
cross-signature to letsencrypt beyond its own expiry
   * This causes issues with older implementations of openssl & gnutls that 
reject such chains when offered to clients by servers.
   * We have provided fixes for openssl in xenial and gnutls in bionic/xenial, 
however trusty systems remain affected. Also any self built old copies of 
openssl/gnutls remain suspeptible to this expiry.
   * One solution is to blacklist the "DST Root CA X3" from the ca-certificates 
package as described at 
https://blog.devgenius.io/rhel-centos-7-fix-for-lets-encrypt-change-8af2de587fe4
 - connectivity to sites chained to "DST Root CA X3" will be unaffected, and 
servers that chain to both "ISRG Root X1" and "DST Root CA X3" should start to 
work unmodified.
   * This is similar to how this was handled for AddTrust before

  "* mozilla/blacklist.txt: blacklist expired AddTrust External Root
  CA."

  [Test Plan]

   * Install old/current ca-certificates faketime wget curl
  libcurl3-gnutls

  # faketime 2021-10-01 wget https://pskov.surgut.co.uk
  --2021-10-01 00:00:00--  https://pskov.surgut.co.uk/
  Resolving pskov.surgut.co.uk (pskov.surgut.co.uk)... 2a01:4f8:c17:3dd8::1, 
49.12.37.5
  Connecting to pskov.surgut.co.uk 
(pskov.surgut.co.uk)|2a01:4f8:c17:3dd8::1|:443... connected.
  ERROR: cannot verify pskov.surgut.co.uk's certificate, issued by 
'/C=US/O=Let\'s Encrypt/CN=R3':
    Issued certificate has expired.
  To connect to pskov.surgut.co.uk insecurely, use `--no-check-certificate'.

  # LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libcurl-gnutls.so.4 faketime 
2021-10-01 curl https://pskov.surgut.co.uk >/dev/null
    % Total% Received % Xferd  Average Speed   TimeTime Time  
Current
   Dload  Upload   Total   SpentLeft  Speed
    0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0
  curl: (60) SSL certificate problem: certificate has expired

   * Install new ca-certificates package

  # faketime 2021-10-01 wget https://pskov.surgut.co.uk
  --2021-10-01 00:00:00--  https://pskov.surgut.co.uk/
  Resolving pskov.surgut.co.uk (pskov.surgut.co.uk)... 2a01:4f8:c17:3dd8::1, 
49.12.37.5
  Connecting to pskov.surgut.co.uk 
(pskov.surgut.co.uk)|2a01:4f8:c17:3dd8::1|:443... connected.
  HTTP request sent, awaiting response... 200 OK
  Length: 612 [text/html]
  Saving to: 'index.html.3'

  100%[>] 612
  --.-K/s   in 0s

  2021-10-01 00:00:00 (71.7 MB/s) - 'index.html.3' saved [612/612]

   LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libcurl-gnutls.so.4 faketime 2021-10-01 
curl https://pskov.surgut.co.uk >/dev/null
    % Total% Received % Xferd  Average Speed   TimeTime Time  
Current
   Dload  Upload   Total   SpentLeft  Speed
  100   612  100   6120 0   5794  0 --:--:-- --:--:-- --:--:--  5828

  Download is successful.

  [Where problems could occur]

   * Connectivity to "DST Root CA X3" websites only, even under faketime
  set to dates prior to 30th of September 2021 will not work, as "DST
  Root CA X3" certificate is no longer installed. users should locally
  install and enable that CA certificate, or allow dangerous unverified
  connectivity to websites using expired CA certs.

  [Other Info]

   * Related openssl and gnutls28 bugs are
  https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1928989 and
  https://bugs.launchpad.net/ubuntu/+source/gnutls28/+bug/1928648

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


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

[Touch-packages] [Bug 1931582] Re: Add LOGO to /etc/os-release

2021-09-26 Thread Jeremy Bicha
What package would contain the distro logos? Would we need to have base-
files Depend on that package?

** Description changed:

  /etc/os-release can provide a logo file, this is now used by gnome-
  control-center to show the logo into the info panel.
  
  If ubuntu would provide its logo name in such file we would be able to
  remove the downstream patch that forces the usage of
- /usr/share/icons/vendor/scalable/emblems/emblem-vendor.svg
+ /usr/share/pixmaps/ubuntu-logo-icon.png
+ 
+ References
+ ---
+ https://www.freedesktop.org/software/systemd/man/os-release.html
+ 
+ https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/985
+ GNOME Control Center, as of version 41, can look for variations of the named 
LOGO. So we should offer those variations if possible too.

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

Title:
  Add LOGO to /etc/os-release

Status in base-files package in Ubuntu:
  Triaged
Status in base-files package in Debian:
  New

Bug description:
  /etc/os-release can provide a logo file, this is now used by gnome-
  control-center to show the logo into the info panel.

  If ubuntu would provide its logo name in such file we would be able to
  remove the downstream patch that forces the usage of
  /usr/share/pixmaps/ubuntu-logo-icon.png

  References
  ---
  https://www.freedesktop.org/software/systemd/man/os-release.html

  https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/985
  GNOME Control Center, as of version 41, can look for variations of the named 
LOGO. So we should offer those variations if possible too.

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


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


[Touch-packages] [Bug 1822156] Re: Cannot parse m3u8 playlist

2021-09-19 Thread Jeremy Bicha
Sorry for the very late response.

I verified your sample file works with totem-pl-parser 3.26.5-5ubuntu1
on Ubuntu 21.10 (development). That version of totem-pl-parser is also
available in Ubuntu 20.04 LTS so it probably works there too.

** Changed in: totem-pl-parser (Ubuntu)
   Status: New => Fix Released

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

Title:
  Cannot parse m3u8 playlist

Status in totem-pl-parser package in Ubuntu:
  Fix Released

Bug description:
  Hello,

  I have a m3u8 (utf8 format) playlist, but many players do not understand that 
file.
  Neither does totem-pl-parser.
  Ref: https://developer.gnome.org/totem-pl-parser/stable/

  
  radio.m3u8 attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: libtotem-plparser-dev 3.26.3-1ubuntu1
  Uname: Linux 5.0.1-050001-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 28 16:06:11 2019
  InstallationDate: Installed on 2019-03-06 (21 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  SourcePackage: totem-pl-parser
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/totem-pl-parser/+bug/1822156/+subscriptions


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


[Touch-packages] [Bug 1934028] Re: Update to version 3.26.6

2021-09-19 Thread Jeremy Bicha
This bug was fixed in the package totem-pl-parser - 3.26.6-1

---
totem-pl-parser (3.26.6-1) unstable; urgency=medium

  * New upstream release
  * Don't depend on libquvi: the video helper feature has been removed
  * debian/docs: README -> README.md
  * Build-Depend on dh-sequence-gir & dh-sequence-gnome
  * debian/rules: Stop managing shlib versions by hand
  * debian/rules: Clean up a bit
  * Refresh patches

 -- Jeremy Bicha   Sun, 19 Sep 2021 09:53:18 -0400

** Changed in: totem-pl-parser (Ubuntu)
   Status: New => Fix Released

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

Title:
  Update to version 3.26.6

Status in totem-pl-parser package in Ubuntu:
  Fix Released
Status in totem-pl-parser package in Debian:
  New

Bug description:
  Dear Maintainer,

  1. Quite a lot of RSS and Atom related fixes have gone into 3.26.6. This
  provides better RSS / Atom data to apps ( e.g. Rhythmbox ).

  2. Parsing feeds is now faster ( 150x ) for some feeds ( e.g. bbc ) in
  debian/ubuntu, now that videosite checking is disabled unless explicitly
  requested.

  Refer https://gitlab.gnome.org/GNOME/totem-pl-parser/-/issues/25 for more
  details.

  3. Garbage CDATA issue has been fixed in xine xml parser.

  Refer https://gitlab.gnome.org/GNOME/totem-pl-parser/-/issues/30 for more
  details.

  Thanks,
  crvi

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/totem-pl-parser/+bug/1934028/+subscriptions


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


[Touch-packages] [Bug 1943359] [NEW] Cherry-pick crypt_checksalt fix

2021-09-12 Thread Jeremy Bicha
Public bug reported:

Please cherry-pick this commit (included in Debian's pam 1.4.0-10 or
upstream 1.5.2)

https://github.com/linux-pam/linux-pam/commit/980d90c9232fe5

The pam upstream bug is
https://github.com/linux-pam/linux-pam/issues/367

I believe we need this fix before updating libxcrypt to 1:4.4.22-1

** Affects: pam (Ubuntu)
 Importance: High
 Status: New


** Tags: impish

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

Title:
  Cherry-pick crypt_checksalt fix

Status in pam package in Ubuntu:
  New

Bug description:
  Please cherry-pick this commit (included in Debian's pam 1.4.0-10 or
  upstream 1.5.2)

  https://github.com/linux-pam/linux-pam/commit/980d90c9232fe5

  The pam upstream bug is
  https://github.com/linux-pam/linux-pam/issues/367

  I believe we need this fix before updating libxcrypt to 1:4.4.22-1

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


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


[Touch-packages] [Bug 1866841] Re: Add chrome-gnome-shell to ubuntu-desktop recommends

2020-04-16 Thread Jeremy Bicha
We can do #3. Do you want to update the bug description for that? We'll
need to file this as a potential SRU, but it might get fixed before the
20.04 LTS release.

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

Title:
  Add chrome-gnome-shell to ubuntu-desktop recommends

Status in One Hundred Papercuts:
  Opinion
Status in chrome-gnome-shell package in Ubuntu:
  Invalid
Status in ubuntu-meta package in Ubuntu:
  Opinion

Bug description:
  Please, consider adding the chrome-gnome-shell package as a
  recommended dependency for ubuntu-desktop package in Ubuntu 20.04. The
  chrome-gnome-shell package provides GNOME Shell integration
  (connector) for Firefox, Chrome, Chromium and other web browsers that
  is necessary for users to be able to manage GNOME Shell extensions
  using a extensions.gnome.org website. Since the Shell Extensions
  support was removed from gnome-software since 3.36 and the replacement
  Extensions application cannot be used to find and install new
  extensions, there is not any user friendly way to install new Shell
  Extensions without having the chrome-gnome-shell package installed.

  More information:
  https://wiki.gnome.org/Projects/GnomeShellIntegrationForChrome

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

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


[Touch-packages] [Bug 1866841] Re: Add chrome-gnome-shell to ubuntu-desktop recommends

2020-04-15 Thread Jeremy Bicha
@AsciiWorld, unless things changed in Ubuntu 20.04 LTS, you can use the
Software app to install GNOME Shell extensions.

chrome-gnome-shell is in universe. It needs to be in main before it can
be installed by default in the Canonical-supported flavors. See
https://wiki.ubuntu.com/MainInclusionProcess and bug 1695565

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

Title:
  Add chrome-gnome-shell to ubuntu-desktop recommends

Status in One Hundred Papercuts:
  Opinion
Status in chrome-gnome-shell package in Ubuntu:
  Invalid
Status in ubuntu-meta package in Ubuntu:
  Opinion

Bug description:
  Please, consider adding the chrome-gnome-shell package as a
  recommended dependency for ubuntu-desktop package in Ubuntu 20.04. The
  chrome-gnome-shell package provides GNOME Shell integration
  (connector) for Firefox, Chrome, Chromium and other web browsers that
  is necessary for users to be able to manage GNOME Shell extensions
  using a extensions.gnome.org website. Since the Shell Extensions
  support was removed from gnome-software since 3.36 and the replacement
  Extensions application cannot be used to find and install new
  extensions, there is not any user friendly way to install new Shell
  Extensions without having the chrome-gnome-shell package installed.

  More information:
  https://wiki.gnome.org/Projects/GnomeShellIntegrationForChrome

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

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


[Touch-packages] [Bug 1869716] Re: Removing libpango1.0-0 broke Minecraft Launcher

2020-04-12 Thread Jeremy Bicha
** Bug watch added: Debian Bug tracker #956520
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956520

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

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

Title:
  Removing  libpango1.0-0  broke Minecraft Launcher

Status in pango1.0 package in Ubuntu:
  Fix Released
Status in pango1.0 package in Debian:
  Unknown

Bug description:
  I just updated my machine, and when I did libpango1.0-0 was removed.
  This removed minecraft-launcher - the (very) popular launcher for
  Minecraft Java edition.

  I have reported this upstream, in case they can update their package
  https://bugs.mojang.com/browse/MCL-13512

  I am filing this bug so we can track it internally. I personally think
  this shouldn't have been done this late in the cycle, but there may
  well have been good reasons for it.

  As a result of the change though, it's now not possible to install
  Minecraft on Ubuntu 20.04.

  $ sudo apt install ./Minecraft\(1\).deb 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Note, selecting 'minecraft-launcher' instead of './Minecraft(1).deb'
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies.
   minecraft-launcher : Depends: libpango1.0-0 (>= 1.14.0) but it is not 
installable
  E: Unable to correct problems, you have held broken packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1869716/+subscriptions

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


[Touch-packages] [Bug 1871972] Re: Update pango for Unicode 13.0

2020-04-10 Thread Jeremy Bicha
Yes, only 20.04.

** Description changed:

  Unicode 13 was released a month ago. The Pango library needs to be
  updated for the new emoji sequences for emoji that are implemented by
  multiple emoji in sequence to appear as a single character instead of as
  separate parts. For instance, https://emojipedia.org/black-cat/
  
- Pango is used by many apps (particularly GTK apps) to display emoji.
- 
- By doing this update for Ubuntu 18.04 LTS now, it will be easier to get
+ By doing this update for Ubuntu 20.04 LTS now, it will be easier to get
  full Unicode 13 support once Ubuntu's color emoji font (fonts-noto-
  color-emoji) is released with Unicode 13 support in a few months.
  
  I don't believe a freeze exception is necessary for this improvement
  now.
  
- References
- =-
  https://gitlab.gnome.org/GNOME/pango/-/commit/06aab3539
- https://emojipedia.org/emoji-13.0/
- https://github.com/googlefonts/noto-emoji/releases

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

Title:
  Update pango for Unicode 13.0

Status in pango1.0 package in Ubuntu:
  Fix Committed

Bug description:
  Unicode 13 was released a month ago. The Pango library needs to be
  updated for the new emoji sequences for emoji that are implemented by
  multiple emoji in sequence to appear as a single character instead of
  as separate parts. For instance, https://emojipedia.org/black-cat/

  By doing this update for Ubuntu 20.04 LTS now, it will be easier to
  get full Unicode 13 support once Ubuntu's color emoji font (fonts-
  noto-color-emoji) is released with Unicode 13 support in a few months.

  I don't believe a freeze exception is necessary for this improvement
  now.

  https://gitlab.gnome.org/GNOME/pango/-/commit/06aab3539

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1871972/+subscriptions

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


[Touch-packages] [Bug 1871972] Re: Update pango for Unicode 13.0

2020-04-09 Thread Jeremy Bicha
** Description changed:

  Unicode 13 was released a month ago. The Pango library needs to be
  updated for the new emoji sequences for emoji that are implemented by
  multiple emoji in sequence to appear as a single character instead of as
  separate parts. For instance, https://emojipedia.org/black-cat/
+ 
+ Pango is used by many apps (particularly GTK apps) to display emoji.
  
  By doing this update for Ubuntu 18.04 LTS now, it will be easier to get
  full Unicode 13 support once Ubuntu's color emoji font (fonts-noto-
  color-emoji) is released with Unicode 13 support in a few months.
  
  I don't believe a freeze exception is necessary for this improvement
  now.
  
+ References
+ =-
  https://gitlab.gnome.org/GNOME/pango/-/commit/06aab3539
+ https://emojipedia.org/emoji-13.0/
+ https://github.com/googlefonts/noto-emoji/releases

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

Title:
  Update pango for Unicode 13.0

Status in pango1.0 package in Ubuntu:
  New

Bug description:
  Unicode 13 was released a month ago. The Pango library needs to be
  updated for the new emoji sequences for emoji that are implemented by
  multiple emoji in sequence to appear as a single character instead of
  as separate parts. For instance, https://emojipedia.org/black-cat/

  Pango is used by many apps (particularly GTK apps) to display emoji.

  By doing this update for Ubuntu 18.04 LTS now, it will be easier to
  get full Unicode 13 support once Ubuntu's color emoji font (fonts-
  noto-color-emoji) is released with Unicode 13 support in a few months.

  I don't believe a freeze exception is necessary for this improvement
  now.

  References
  =-
  https://gitlab.gnome.org/GNOME/pango/-/commit/06aab3539
  https://emojipedia.org/emoji-13.0/
  https://github.com/googlefonts/noto-emoji/releases

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1871972/+subscriptions

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


[Touch-packages] [Bug 1871972] [NEW] Update pango for Unicode 13.0

2020-04-09 Thread Jeremy Bicha
Public bug reported:

Unicode 13 was released a month ago. The Pango library needs to be
updated for the new emoji sequences for emoji that are implemented by
multiple emoji in sequence to appear as a single character instead of as
separate parts. For instance, https://emojipedia.org/black-cat/

By doing this update for Ubuntu 18.04 LTS now, it will be easier to get
full Unicode 13 support once Ubuntu's color emoji font (fonts-noto-
color-emoji) is released with Unicode 13 support in a few months.

I don't believe a freeze exception is necessary for this improvement
now.

https://gitlab.gnome.org/GNOME/pango/-/commit/06aab3539

** Affects: pango1.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: focal

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

Title:
  Update pango for Unicode 13.0

Status in pango1.0 package in Ubuntu:
  New

Bug description:
  Unicode 13 was released a month ago. The Pango library needs to be
  updated for the new emoji sequences for emoji that are implemented by
  multiple emoji in sequence to appear as a single character instead of
  as separate parts. For instance, https://emojipedia.org/black-cat/

  By doing this update for Ubuntu 18.04 LTS now, it will be easier to
  get full Unicode 13 support once Ubuntu's color emoji font (fonts-
  noto-color-emoji) is released with Unicode 13 support in a few months.

  I don't believe a freeze exception is necessary for this improvement
  now.

  https://gitlab.gnome.org/GNOME/pango/-/commit/06aab3539

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1871972/+subscriptions

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


[Touch-packages] [Bug 1851046] Re: Enable Last.fm provider

2019-11-03 Thread Jeremy Bicha
It is disabled by default in GNOME. I don't know (or remember) why it's
disabled there.

https://gitlab.gnome.org/GNOME/gnome-online-
accounts/blob/master/meson_options.txt#L26

** Changed in: gnome-online-accounts (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  Enable Last.fm provider

Status in gnome-online-accounts package in Ubuntu:
  New

Bug description:
  Since a while now GOA supports Last.fm accounts but for some reason this 
provider is excluded in the Ubuntu build parameters of this package.
  Is there a specific reason why this is not enabled? Would it be possible to 
enable this provider as well?

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-online-accounts 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Nov  2 16:07:05 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-11-26 (1437 days ago)
  InstallationMedia: It
  SourcePackage: gnome-online-accounts
  UpgradeStatus: Upgraded to eoan on 2019-10-20 (13 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1851046/+subscriptions

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


[Touch-packages] [Bug 1410544] Re: Upgrade to Python 2.7.9 (backporting features from PEP 466)

2019-10-25 Thread Jeremy Bicha
** Summary changed:

- Upgrade to Python 2.7.9 (backporting features from PEP 466)
+ Upgrade to Python 2.7.17 (backporting features from PEP 466)

** Tags removed: precise trusty utopic
** Tags added: bionic xenial

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

Title:
  Upgrade to Python 2.7.17 (backporting features from PEP 466)

Status in python-defaults package in Ubuntu:
  New

Bug description:
  Following @actionparsnip's suggestion, re-filing
  https://answers.launchpad.net/ubuntu/+source/python-
  defaults/+question/260428 as a bug. Quoted from the original question:

  "What are the official plans for Python 2.7.9 (and further 2.7 patch
  releases) in supported releases? As per PEP 466
  (https://www.python.org/dev/peps/pep-0466/), these will receive
  handpicked security-related feature additions from the Python 3
  series. Will these new releases be included in released-and-still-
  supported Ubuntu versions? (I realise Ubuntu releases don't generally
  get new upstream software versions, but I feel this case might warrant
  an exception.)

  Note that I'm specifically asking about the *features* mentioned in
  PEP 466 (and any future additions), i.e. the new functions in the hmac
  and hashlib modules and the backported ssl module, not any security
  issues in existing functionality."

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

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


[Touch-packages] [Bug 1844992] Re: Update to 1.18.0 not this cycle

2019-10-25 Thread Jeremy Bicha
autosynced for 20.04 LTS

** Changed in: v4l-utils (Ubuntu)
   Status: New => Fix Released

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

Title:
  Update to 1.18.0 not this cycle

Status in v4l-utils package in Ubuntu:
  Fix Released

Bug description:
  The new version has new features and it's late for this cycle

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

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


[Touch-packages] [Bug 1819183] Re: FFe: Update pygobject to 3.32

2019-03-11 Thread Jeremy Bicha
This bug was fixed in the package pygobject - 3.32.0-1

---
pygobject (3.32.0-1) experimental; urgency=medium

  * New upstream release

 -- Jeremy Bicha   Sun, 10 Mar 2019 12:59:34 -0400

pygobject (3.31.4-1) experimental; urgency=medium

  * New upstream release
  * Bump minimum glib to 2.48.0

 -- Jeremy Bicha   Fri, 08 Mar 2019 09:45:40 -0500

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

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

Title:
  FFe: Update pygobject to 3.32

Status in pygobject package in Ubuntu:
  Fix Released

Bug description:
  Feature Freeze exception request
  
  Since we're updating the rest of GNOME to 3.32 (including glib and 
gobject-introspection), it seems like it would be a good idea to update 
pygobject also.

  3.32.0-1 is in Debian experimental ready to be synced over once this
  FFe is approved.

  https://gitlab.gnome.org/GNOME/pygobject/blob/master/NEWS
  https://gitlab.gnome.org/GNOME/pygobject/compare/3.30.4...3.32.0 (includes 
several commits that were already included in the current 3.30.4 version)

  Justification for lateness
  --
  Sorry, we've been a bit busy and this wasn't a high priority.

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

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


[Touch-packages] [Bug 1819183] Re: FFe: Update pygobject to 3.32

2019-03-10 Thread Jeremy Bicha
** Tags added: upgrade-software-version

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

Title:
  FFe: Update pygobject to 3.32

Status in pygobject package in Ubuntu:
  New

Bug description:
  Feature Freeze exception request
  
  Since we're updating the rest of GNOME to 3.32 (including glib and 
gobject-introspection), it seems like it would be a good idea to update 
pygobject also.

  3.32.0-1 is in Debian experimental ready to be synced over once this
  FFe is approved.

  https://gitlab.gnome.org/GNOME/pygobject/blob/master/NEWS
  https://gitlab.gnome.org/GNOME/pygobject/compare/3.30.4...3.32.0 (includes 
several commits that were already included in the current 3.30.4 version)

  Justification for lateness
  --
  Sorry, we've been a bit busy and this wasn't a high priority.

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

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


[Touch-packages] [Bug 1819183] Re: FFe: Update pygobject to 3.32

2019-03-10 Thread Jeremy Bicha
** Description changed:

  Feature Freeze exception request
  
  Since we're updating the rest of GNOME to 3.32 (including glib and 
gobject-introspection), it seems like it would be a good idea to update 
pygobject also.
  
- 3.31.4-1 is in Debian experimental ready to be synced over once this FFe
- is approved. 3.32.0 is expected next week.
+ 3.32.0-1 is in Debian experimental ready to be synced over once this FFe
+ is approved.
  
  https://gitlab.gnome.org/GNOME/pygobject/blob/master/NEWS
- https://gitlab.gnome.org/GNOME/pygobject/compare/3.30.4...3.31.4 (includes 
several commits that were already included in the current 3.30.4 version)
+ https://gitlab.gnome.org/GNOME/pygobject/compare/3.30.4...3.32.0 (includes 
several commits that were already included in the current 3.30.4 version)
  
  Justification for lateness
  --
  Sorry, we've been a bit busy and this wasn't a high priority.

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

Title:
  FFe: Update pygobject to 3.32

Status in pygobject package in Ubuntu:
  New

Bug description:
  Feature Freeze exception request
  
  Since we're updating the rest of GNOME to 3.32 (including glib and 
gobject-introspection), it seems like it would be a good idea to update 
pygobject also.

  3.32.0-1 is in Debian experimental ready to be synced over once this
  FFe is approved.

  https://gitlab.gnome.org/GNOME/pygobject/blob/master/NEWS
  https://gitlab.gnome.org/GNOME/pygobject/compare/3.30.4...3.32.0 (includes 
several commits that were already included in the current 3.30.4 version)

  Justification for lateness
  --
  Sorry, we've been a bit busy and this wasn't a high priority.

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

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


[Touch-packages] [Bug 1717951] Re: UIFe: Drop imagemagick-display from the default install

2019-03-10 Thread Jeremy Bicha
amano, please open a new bug for new issues instead of commenting on old
closed bugs.

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

Title:
  UIFe: Drop imagemagick-display from the default install

Status in ubuntu-settings package in Ubuntu:
  Fix Released
Status in imagemagick package in Debian:
  New

Bug description:
  Impact
  ==
  I'm proposing to drop the ImageMagick app from the default Ubuntu 17.10.

  It is visible in the Show Applications view of the Activities Overview
  so this could impact screenshots.

  Justification
  =
  imagemagick is a collection of commandline utilities for working with images, 
photos, etc. It is a required dependency for many things and will still be 
installed by default.

  Bundled with imagemagick is the "display" app, which is an app with an
  unusual, difficult-to-use UI. It was not intentionally included in the
  default Ubuntu install but was only there because it was packaged
  together.

  I am proposing splitting the display app to a separate binary package
  so that it is available for install for the few who do want to use the
  app.

  I tried proposing this to Debian. See comment #60 on the attached
  Debian bug but the Debian maintainer doesn't seem interested in
  accepting my proposal any time soon. (I emailed him directly a few
  months ago too.)

  List Notifications
  ==
  https://lists.ubuntu.com/archives/ubuntu-doc/2017-September/020534.html
  
https://lists.ubuntu.com/archives/ubuntu-translators/2017-September/007403.html

  Other Info
  ==
  I will be attaching a patch for review by the Desktop Team here soon.

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

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


[Touch-packages] [Bug 1819183] [NEW] FFe: Update pygobject to 3.32

2019-03-08 Thread Jeremy Bicha
Public bug reported:

Feature Freeze exception request

Since we're updating the rest of GNOME to 3.32 (including glib and 
gobject-introspection), it seems like it would be a good idea to update 
pygobject also.

3.31.4-1 is in Debian experimental ready to be synced over once this FFe
is approved. 3.32.0 is expected next week.

https://gitlab.gnome.org/GNOME/pygobject/blob/master/NEWS
https://gitlab.gnome.org/GNOME/pygobject/compare/3.30.4...3.31.4 (includes 
several commits that were already included in the current 3.30.4 version)

Justification for lateness
--
Sorry, we've been a bit busy and this wasn't a high priority.

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


** Tags: disco

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

Title:
  FFe: Update pygobject to 3.32

Status in pygobject package in Ubuntu:
  New

Bug description:
  Feature Freeze exception request
  
  Since we're updating the rest of GNOME to 3.32 (including glib and 
gobject-introspection), it seems like it would be a good idea to update 
pygobject also.

  3.31.4-1 is in Debian experimental ready to be synced over once this
  FFe is approved. 3.32.0 is expected next week.

  https://gitlab.gnome.org/GNOME/pygobject/blob/master/NEWS
  https://gitlab.gnome.org/GNOME/pygobject/compare/3.30.4...3.31.4 (includes 
several commits that were already included in the current 3.30.4 version)

  Justification for lateness
  --
  Sorry, we've been a bit busy and this wasn't a high priority.

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

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


[Touch-packages] [Bug 1798861] Re: Tooltips flicker constantly in GTK3 applications

2019-02-26 Thread Jeremy Bicha
The fix for this has completed verification and is rolling out as an
update to Ubuntu 18.10 computers over the next few days.

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

Title:
  Tooltips flicker constantly in GTK3 applications

Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Cosmic:
  Fix Released
Status in gtk+3.0 package in Debian:
  Fix Released

Bug description:
  Tooltips are flicker constantly (i.e. repeatedly shown and the hidden
  again) in GTK3 applications under XFCE.

  It is a regression in the recent GTK 3.24.

  This is the upstream report and fix:
  https://gitlab.gnome.org/GNOME/gtk/issues/1371
  
https://gitlab.gnome.org/GNOME/gtk/commit/9b7d886b723132eade2e76f3fd179cf81b7601f2

  A workaround for XFCE is as follows:

  Open Settings Editor.
  Set xsettings -> Gtk -> CursorThemeSize to 16.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libgtk-3-0 3.24.1-1ubuntu2
  Uname: Linux 4.19.0-041900rc8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  Date: Fri Oct 19 12:23:53 2018
  InstallationDate: Installed on 2017-02-01 (624 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gtk+3.0
  UpgradeStatus: Upgraded to cosmic on 2018-10-18 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1798861/+subscriptions

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


[Touch-packages] [Bug 1807721] Re: Fix variant selection in emoji chooser

2019-02-25 Thread Jeremy Bicha
I was able to successfully insert people variant emojis with libgtk-3-0
3.24.4-0ubuntu1 on Ubuntu 18.10 and with 3.22.30-1ubuntu2 on Ubuntu
18.04 LTS.

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

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

Title:
  Fix variant selection in emoji chooser

Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Bionic:
  Fix Committed
Status in gtk+3.0 source package in Cosmic:
  Fix Committed

Bug description:
  Impact
  ==
  The variant selector in the emoji chooser was broken and will crash the app 
if used.

  Test Case
  =
  In an app like gedit, right click in the text area and select Insert Emoji
  Look for one of the "people" emoji.
  Right-click (or long-click) on the emoji and select one of the skin tones 
instead of the default yellow.
  The emoji with the skin tone you selected should be added to the text area.

  Regression Potential
  
  This fix was included in the gtk 3.24.2 release. There is a standing 
microrelease exception for GNOME point releases.

  GTK 3.24 was a big enough release (with some bumped dependencies) that
  it's not very practical to push to Ubuntu 18.04 LTS so we selectively
  cherry-pick fixes there.

  https://wiki.ubuntu.com/StableReleaseUpdates#GNOME

  https://gitlab.gnome.org/GNOME/gtk/commit/dbbc7b3859f4b
  https://gitlab.gnome.org/GNOME/gtk/issues/1398

  Other Info
  ==
  This bug is fixed in gtk 3.24.2. Its SRU for cosmic is being tracked in LP: 
#1808233

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1807721/+subscriptions

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


[Touch-packages] [Bug 1798861] Re: Tooltips flicker constantly in GTK3 applications

2019-02-25 Thread Jeremy Bicha
I am marking this fixed since we have a proposed fix in progress tracked
at https://launchpad.net/bugs/1808233

** Changed in: gtk+3.0 (Ubuntu Cosmic)
   Status: In Progress => Fix Released

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

Title:
  Tooltips flicker constantly in GTK3 applications

Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Cosmic:
  Fix Released
Status in gtk+3.0 package in Debian:
  Fix Released

Bug description:
  Tooltips are flicker constantly (i.e. repeatedly shown and the hidden
  again) in GTK3 applications under XFCE.

  It is a regression in the recent GTK 3.24.

  This is the upstream report and fix:
  https://gitlab.gnome.org/GNOME/gtk/issues/1371
  
https://gitlab.gnome.org/GNOME/gtk/commit/9b7d886b723132eade2e76f3fd179cf81b7601f2

  A workaround for XFCE is as follows:

  Open Settings Editor.
  Set xsettings -> Gtk -> CursorThemeSize to 16.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libgtk-3-0 3.24.1-1ubuntu2
  Uname: Linux 4.19.0-041900rc8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  Date: Fri Oct 19 12:23:53 2018
  InstallationDate: Installed on 2017-02-01 (624 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gtk+3.0
  UpgradeStatus: Upgraded to cosmic on 2018-10-18 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1798861/+subscriptions

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


[Touch-packages] [Bug 1813591] Re: pygobject ftbfs in 18.04 LTS

2019-02-25 Thread Jeremy Bicha
pygobject built successfully on Ubuntu 18.04 LTS and the autopkgtests
confirm that it still works.

https://people.canonical.com/~ubuntu-archive/proposed-migration/bionic/update_excuses.html#pygobject
https://autopkgtest.ubuntu.com/packages/p/pygobject

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

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

Title:
  pygobject ftbfs in 18.04 LTS

Status in pygobject package in Ubuntu:
  Fix Released
Status in pygobject source package in Bionic:
  Fix Committed

Bug description:
  Impact
  --
  pygobject doesn't build from source which means someone would need to fix 
that problem before fixing any bugs in the pygobject package for Ubuntu 18.04 
LTS.

  Test Case
  -
  Does pygobject build successfully?

  Regression Potential
  
  pygobject 3.28 is the intended version to match glib 2.56 but it missed the 
deadline for Ubuntu 18.04 LTS. So this fix is cherry-picking a small commit to 
fix the build tests with 18.04's glib2.0 2.56.

  The only change that is made in this upload is to the tests. There
  should be no effect on anything else.

  https://gitlab.gnome.org/GNOME/pygobject/commit/550bd7c7

  Original Bug Report
  ---
  according to
  
http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html

  pygobject ftbfs.

  ==
  FAIL: test_filenames (test_glib.TestGLib)
  --
  Traceback (most recent call last):
    File "/<>/tests/test_glib.py", line 66, in test_filenames
  self.assertTrue(isinstance(res, bytes))
  AssertionError: False is not true

  --
  Ran 1211 tests in 4.072s

  FAILED (failures=1, skipped=4, expected failures=12)

   torture test 1 (1 iterations): 0.012186 secs
   torture test 2 (1 iterations): 0.068459 secs
   torture test 3 (1 iterations): 0.029216 secs
   torture test 4 (1 iterations): 0.065890 secs
   
   Total: 0.175751 sec
  Makefile:905: recipe for target 'check.real' failed
  make[5]: *** [check.real] Error 1
  make[5]: Leaving directory '/<>/build-3.6/tests'
  Makefile:900: recipe for target 'check-local' failed
  make[4]: *** [check-local] Error 2
  Makefile:738: recipe for target 'check-am' failed
  make[3]: *** [check-am] Error 2
  Makefile:691: recipe for target 'check-recursive' failed
  make[2]: *** [check-recursive] Error 1

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

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


[Touch-packages] [Bug 1807719] Re: Some emoji in emoji chooser are black & white

2019-02-25 Thread Jeremy Bicha
I confirmed that all emoji in the emoji chooser appear to be in full
color with libgtk-3-0 3.24.4-0ubuntu1 on Ubuntu 18.10 and with
3.22.30-1ubuntu2 on Ubuntu 18.04 LTS.

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

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

Title:
  Some emoji in emoji chooser are black & white

Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Bionic:
  Fix Committed
Status in gtk+3.0 source package in Cosmic:
  Fix Committed

Bug description:
  Impact
  ==
  Some emoji in the emoji chooser show as black & white.

  This is because these emoji default to "text presentation" instead of
  "emoji presentation".

  More information and a screenshot can be found in the pango issue
  linked below.

  Test Case
  =
  In an app like gedit, right click in the text area and select Insert Emoji
  Browse through the emoji list. All should be in full color.

  Regression Potential
  
  This fix was included in the gtk 3.24.2 release. There is a standing 
microrelease exception for GNOME point releases.

  GTK 3.24 was a big enough release (with some bumped dependencies) that
  it's not very practical to push to Ubuntu 18.04 LTS so we selectively
  cherry-pick fixes there.

  https://wiki.ubuntu.com/StableReleaseUpdates#GNOME

  https://gitlab.gnome.org/GNOME/pango/issues/334
  https://gitlab.gnome.org/GNOME/gtk/commit/aac38198a3f5
  https://gitlab.gnome.org/GNOME/gtk/commit/b74e3209a5af0

  Other Info
  ==
  This adds an extra variation selector byte to each emoji added via the emoji 
chooser. (Many emoji are made up of multiple bytes.) This will not affect emoji 
added to GTK apps in other ways, such as copying and pasting from an app where 
the emoji doesn't have that variation selector added to it.

  This bug is fixed in gtk 3.24.2. Its SRU for cosmic is being tracked
  in LP: #1808233

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1807719/+subscriptions

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


[Touch-packages] [Bug 1808233] Re: Update gtk to 3.24.4

2019-02-25 Thread Jeremy Bicha
I verified the Xfce bug by installing the xfce4 metapackage on top of
Ubuntu 18.10. I could see the cursor flickering (and missing tooltip) by
hovering over the text for one of the links in Archive Manager's Help.

After installing libgtk-3-0 (and related packages) 3.24.4-0ubuntu1, the
tooltip displayed correctly without flickering.

I also ran several gtk3 apps in Ubuntu 18.10 and verified that they
worked fine. I confirmed that switches looked ok with the Yaru and
Adwaita themes.

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

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

Title:
  Update gtk to 3.24.4

Status in gtk+3.0 package in Ubuntu:
  Fix Committed
Status in gtk+3.0 source package in Cosmic:
  Fix Committed

Bug description:
  Impact
  ==
  There is a new release in the stable 3.24 series.

  This also bundles the emoji fixes from LP: #1807719 and LP: #1807721
  and the Xfce flickering fix from LP: #1798861.

  https://gitlab.gnome.org/GNOME/gtk/blob/gtk-3-24/NEWS
  https://gitlab.gnome.org/GNOME/gtk/compare/3.24.1...3.24.4

  Test Case
  =
  Run several apps in the default Ubuntu install and make sure that there are 
no visible regressions.

  Make sure that GTK switches look OK.

  We will also be checking Xfce to validate the fix for LP: #1798861.

  Regression Potential
  
  There is a standing microrelease exception for GNOME point releases.

  I believe this is the second time in recent history that we've pushed
  a gtk point release as an SRU. The other example was 3.22.25 for
  Ubuntu 17.10 (LP: #1728421). We never ended up doing one for Ubuntu
  18.04 LTS since it already included 3.22.30, the final 3.22 release.
  It hasn't been practical to update 18.04's gtk to  the 3.24 series
  (bumped dependencies are one problem).

  https://wiki.ubuntu.com/StableReleaseUpdates#GNOME

  By the way, pre-release gtk3 is actually getting a bit more testing
  than a year ago since more developers and users are using development
  Flatpak releases of popular GNOME apps. (On the other hand, there were
  a few regressions in the 3.24.2 and 3.24.3 releases.)

  This update changes the ON/OFF switches for GNOME's default Adwaita
  theme to use ❙/○ for all languages (or ⏽/⭘ if they are supported in a
  font you have installed: currently, that's fonts-symbola which we no
  longer install by default). Previously, it was ❙/○ for most languages
  but ON/OFF for English (because English has short words that could fit
  on a switch). This doesn't affect default Ubuntu 18.10 which uses Yaru
  which doesn't use labels on its switches. This is technically a UI
  change, but it is useful for compatibility with Flatpak apps that are
  being built with the new GTK. This change is small enough that it
  could be reverted for Ubuntu 18.10 if necessary.

  Other Info
  ==
  The commit history shows themeing changes to the GNOME default themes 
(Adwaita and Adwaita Dark which are bundled inside gtk3). But those changes 
were reverted for this release to make it easier for distros like us to push 
the update to our stable release.

  The next scheduled gtk3 release (3.24.5 ? in March?) will include
  those changes. See https://blog.gtk.org/2019/01/14/theme-changes-in-
  gtk-3/ for more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1808233/+subscriptions

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


[Touch-packages] [Bug 1817494] Re: libsoup2.4-dev missing dependencies

2019-02-24 Thread Jeremy Bicha
This bug was fixed in the package libsoup2.4 - 2.65.91-2

---
libsoup2.4 (2.65.91-2) experimental; urgency=medium

  * Have libsoup2.4-dev depend on libpsl-dev & libsqlite3-dev

 -- Jeremy Bicha   Sun, 24 Feb 2019 19:19:55 -0500

** Changed in: libsoup2.4 (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  libsoup2.4-dev missing dependencies

Status in libsoup2.4 package in Ubuntu:
  Fix Released

Bug description:
  libsoup changed its .pc file so we have to add a few more dependencies
  (as seen in the failed midori build).

  Please sync libsoup2.4 2.65.91-2 from experimental when it's
  available.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libsoup2.4/+bug/1817494/+subscriptions

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


[Touch-packages] [Bug 1817494] [NEW] libsoup2.4-dev missing dependencies

2019-02-24 Thread Jeremy Bicha
Public bug reported:

libsoup changed its .pc file so we have to add a few more dependencies
(as seen in the failed midori build).

Please sync libsoup2.4 2.65.91-2 from experimental when it's available.

** Affects: libsoup2.4 (Ubuntu)
 Importance: High
 Status: Triaged


** Tags: block-proposed disco

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

Title:
  libsoup2.4-dev missing dependencies

Status in libsoup2.4 package in Ubuntu:
  Triaged

Bug description:
  libsoup changed its .pc file so we have to add a few more dependencies
  (as seen in the failed midori build).

  Please sync libsoup2.4 2.65.91-2 from experimental when it's
  available.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libsoup2.4/+bug/1817494/+subscriptions

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


[Touch-packages] [Bug 1796622] Re: NetworkManager IPv6 DAD lifetime behavior introduce security risk

2019-02-24 Thread Jeremy Bicha
The bionic fix is included in the upstream 1.10.14 release:
https://launchpad.net/ubuntu/+source/network-manager/1.10.14-0ubuntu1

1.12.6 has the fix for cosmic.

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

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

Title:
  NetworkManager IPv6 DAD lifetime behavior introduce security risk

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Bionic:
  Fix Committed
Status in network-manager source package in Cosmic:
  New
Status in network-manager source package in Disco:
  Fix Released

Bug description:
  Description:
  When performing IPv6 certification test, two DAD test cases (3.2.5c and d) 
check the remaining lifetime feature of the IPv6 packets.  The Network trace 
shows that the remaining lifetime becomes infinite when running these test 
cases.  Hence when running in IPv6 environment with Network Manager enabled, 
there is a risk of packets travelling in network which has valid lifetime 
always. If these packets are snooped by a hacker he can reply to these packets 
and they can send legitimate packets which are actually not.  

  According to https://tools.ietf.org/search/rfc4862, page 19:
  "The above rules address a specific denial-of-service attack in which a bogus 
advertisement could contain prefixes with very small Valid Lifetimes.  Without 
the above rules, a single unauthenticated advertisement containing bogus Prefix 
Information options with short Valid Lifetimes could cause all of a node's 
addresses to expire prematurely.  The above rules ensure that legitimate 
advertisements (which are sent periodically) will "cancel" the short Valid 
Lifetimes before they actually take effect."

  Other notes:
  - 2 test cases pass without NetworkManager.
  - Tested with different Linux Desktop Distributions, as long as 
NetworkManager is running, those DAD test cases fail.

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

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


[Touch-packages] [Bug 1796622] Re: NetworkManager IPv6 DAD lifetime behavior introduce security risk

2019-02-24 Thread Jeremy Bicha
This is fixed in Disco; I opened Bionic and Cosmic tasks since the bug
needs to be open in some way for it to be tracked.

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

** Also affects: network-manager (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Also affects: network-manager (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: network-manager (Ubuntu Bionic)
   Status: New => Fix Committed

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

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

Title:
  NetworkManager IPv6 DAD lifetime behavior introduce security risk

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Bionic:
  Fix Committed
Status in network-manager source package in Cosmic:
  New
Status in network-manager source package in Disco:
  Fix Released

Bug description:
  Description:
  When performing IPv6 certification test, two DAD test cases (3.2.5c and d) 
check the remaining lifetime feature of the IPv6 packets.  The Network trace 
shows that the remaining lifetime becomes infinite when running these test 
cases.  Hence when running in IPv6 environment with Network Manager enabled, 
there is a risk of packets travelling in network which has valid lifetime 
always. If these packets are snooped by a hacker he can reply to these packets 
and they can send legitimate packets which are actually not.  

  According to https://tools.ietf.org/search/rfc4862, page 19:
  "The above rules address a specific denial-of-service attack in which a bogus 
advertisement could contain prefixes with very small Valid Lifetimes.  Without 
the above rules, a single unauthenticated advertisement containing bogus Prefix 
Information options with short Valid Lifetimes could cause all of a node's 
addresses to expire prematurely.  The above rules ensure that legitimate 
advertisements (which are sent periodically) will "cancel" the short Valid 
Lifetimes before they actually take effect."

  Other notes:
  - 2 test cases pass without NetworkManager.
  - Tested with different Linux Desktop Distributions, as long as 
NetworkManager is running, those DAD test cases fail.

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

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


[Touch-packages] [Bug 1814562] Re: Update to new upstream 1.0.2

2019-02-21 Thread Jeremy Bicha
** Changed in: zeitgeist (Ubuntu)
   Status: New => Fix Committed

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

Title:
  Update to new upstream 1.0.2

Status in zeitgeist package in Ubuntu:
  Fix Committed

Bug description:
  There is a new upstream release which fixes issues with valac 0.43/44

  https://launchpad.net/zeitgeist/+milestone/1.0.2

  2018-01-31: Zeitgeist 1.0.2 "Phoenix"
  ---
  Overall:
   - Fix compile errors and warnings with new vala
   - fts: Correctly implement the org.gnome.zeitgeist.Index DBus interface
   - test-log: Use correct free function for ZeitgeistResultSet
   - Do not require rapper as it is not used anymore
   - Make ontology2code work with python3
   - Properly fallback with the Zeitgeist version
   - rdflib directly to parse the trig files
   - Update Ontology2code to ba able to specify the output path

  Libzeitgeist:
   - Asynchronous out-parameters are only allowed at the end of argument lists
 *** THIS IS AN UNAVOIDABLE VALA API BREAK ***

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

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


[Touch-packages] [Bug 1816271] Re: no sound

2019-02-16 Thread Jeremy Bicha
** Description changed:

  19.04,kern 4.19.0-13
  just took update and now does not recognize soundcard or something plugged in 
to headphones jack. pulled bug. Now if I unplug headphones and plug back in, it 
wakes up and recognizes it and works fine. I thought I had this prob a few days 
ago and restored back to the 10th, and updated all but alsa and worked fine. 
This morning I checked and a bunch of alsa stuff was no longer showing in 
updates, took everything, and worked fine. Just took updates (Software 
Updater), and checked speakers and no go. When this happened, it also would not 
allow sound to HDTV via HDMI, no matter what. Just tested and was able to get 
sound via hdmi, but remember, I have already "woken it up" by unplugging and 
plugging headphones (actually sony vaio computer speakers)
  ThinkPad T530-2394-3J8, i5-3380M 2.9GHz, Dual boot (BIOS/MBR): Grub, Ubuntu 
19.04dev / Win7 Pro x64 . 8GB(15GB/s), Sammy 250GB SSD. Fast!
- kris@kris-ThinkPad-T530:~$ lsb_release -rd
- Description:  Ubuntu Disco Dingo (development branch)
- Release:  19.04
- kris@kris-ThinkPad-T530:~$ 
- 
- kris@kris-ThinkPad-T530:~$ uname -a
- Linux kris-ThinkPad-T530 4.19.0-13-generic #14-Ubuntu SMP Thu Feb 7 21:51:25 
UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
- kris@kris-ThinkPad-T530:~$ 
- 
- kris@kris-ThinkPad-T530:~$ apt-cache policy pkgname
- N: Unable to locate package pkgname
- kris@kris-ThinkPad-T530:~$ 
  
  I expected sound to recognize soundcard/speakers. It did not until I
  unplug/replug headphones.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gstreamer1.0-plugins-good 1.15.1-1ubuntu2
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 16 19:20:26 2019
  InstallationDate: Installed on 2019-02-09 (7 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: gst-plugins-good1.0
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  no sound

Status in gst-plugins-good1.0 package in Ubuntu:
  New

Bug description:
  19.04,kern 4.19.0-13
  just took update and now does not recognize soundcard or something plugged in 
to headphones jack. pulled bug. Now if I unplug headphones and plug back in, it 
wakes up and recognizes it and works fine. I thought I had this prob a few days 
ago and restored back to the 10th, and updated all but alsa and worked fine. 
This morning I checked and a bunch of alsa stuff was no longer showing in 
updates, took everything, and worked fine. Just took updates (Software 
Updater), and checked speakers and no go. When this happened, it also would not 
allow sound to HDTV via HDMI, no matter what. Just tested and was able to get 
sound via hdmi, but remember, I have already "woken it up" by unplugging and 
plugging headphones (actually sony vaio computer speakers)
  ThinkPad T530-2394-3J8, i5-3380M 2.9GHz, Dual boot (BIOS/MBR): Grub, Ubuntu 
19.04dev / Win7 Pro x64 . 8GB(15GB/s), Sammy 250GB SSD. Fast!

  I expected sound to recognize soundcard/speakers. It did not until I
  unplug/replug headphones.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gstreamer1.0-plugins-good 1.15.1-1ubuntu2
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 16 19:20:26 2019
  InstallationDate: Installed on 2019-02-09 (7 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gst-plugins-good1.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-good1.0/+bug/1816271/+subscriptions

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


[Touch-packages] [Bug 1815317] Re: Update gnome-online-accounts to 3.31.90

2019-02-13 Thread Jeremy Bicha
** Changed in: gnome-online-accounts (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  Update gnome-online-accounts to 3.31.90

Status in gnome-online-accounts package in Ubuntu:
  Fix Committed

Bug description:
  We should update gnome-online-accounts to 3.31.90 (Debian experimental
  has the update).

  GNOME has dropped its .png icons and replaced them with 128px .svg's.
  If we did the same, we could drop our binary patch since an .svg isn't
  a binary file.

  GNOME also includes a 16px symbolic .svg but I don't think those are
  used right now.

  So although getting the 128px .svg from Canonical Design isn't
  technically a blocker, I think it would be nice to get it for
  consistency (and simplifying our patches a bit).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1815317/+subscriptions

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


[Touch-packages] [Bug 1814562] Re: Update to new upstream 1.0.2

2019-02-12 Thread Jeremy Bicha
I am unsubscribing ubuntu-sponsors. Please feel free to resubscribe when
you have something ready for sponsoring.

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

Title:
  Update to new upstream 1.0.2

Status in zeitgeist package in Ubuntu:
  New

Bug description:
  There is a new upstream release which fixes issues with valac 0.43/44

  https://launchpad.net/zeitgeist/+milestone/1.0.2

  2018-01-31: Zeitgeist 1.0.2 "Phoenix"
  ---
  Overall:
   - Fix compile errors and warnings with new vala
   - fts: Correctly implement the org.gnome.zeitgeist.Index DBus interface
   - test-log: Use correct free function for ZeitgeistResultSet
   - Do not require rapper as it is not used anymore
   - Make ontology2code work with python3
   - Properly fallback with the Zeitgeist version
   - rdflib directly to parse the trig files
   - Update Ontology2code to ba able to specify the output path

  Libzeitgeist:
   - Asynchronous out-parameters are only allowed at the end of argument lists
 *** THIS IS AN UNAVOIDABLE VALA API BREAK ***

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

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


[Touch-packages] [Bug 1815317] [NEW] Update gnome-online-accounts to 3.31.90

2019-02-09 Thread Jeremy Bicha
Public bug reported:

We should update gnome-online-accounts to 3.31.90 (Debian experimental
has the update).

GNOME has dropped its .png icons and replaced them with 128px .svg's. If
we did the same, we could drop our binary patch since an .svg isn't a
binary file.

GNOME also includes a 16px symbolic .svg but I don't think those are
used right now.

So although getting the 128px .svg from Canonical Design isn't
technically a blocker, I think it would be nice to get it for
consistency (and simplifying our patches a bit).

** Affects: gnome-online-accounts (Ubuntu)
 Importance: Wishlist
 Status: New


** Tags: disco upgrade-software-version

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

Title:
  Update gnome-online-accounts to 3.31.90

Status in gnome-online-accounts package in Ubuntu:
  New

Bug description:
  We should update gnome-online-accounts to 3.31.90 (Debian experimental
  has the update).

  GNOME has dropped its .png icons and replaced them with 128px .svg's.
  If we did the same, we could drop our binary patch since an .svg isn't
  a binary file.

  GNOME also includes a 16px symbolic .svg but I don't think those are
  used right now.

  So although getting the 128px .svg from Canonical Design isn't
  technically a blocker, I think it would be nice to get it for
  consistency (and simplifying our patches a bit).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1815317/+subscriptions

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


[Touch-packages] [Bug 1814562] Re: Update to new upstream 1.0.2

2019-02-04 Thread Jeremy Bicha
There is nothing here ready to be sponsored…

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

Title:
  Update to new upstream 1.0.2

Status in zeitgeist package in Ubuntu:
  New

Bug description:
  There is a new upstream release which fixes issues with valac 0.43/44

  https://launchpad.net/zeitgeist/+milestone/1.0.2

  2018-01-31: Zeitgeist 1.0.2 "Phoenix"
  ---
  Overall:
   - Fix compile errors and warnings with new vala
   - fts: Correctly implement the org.gnome.zeitgeist.Index DBus interface
   - test-log: Use correct free function for ZeitgeistResultSet
   - Do not require rapper as it is not used anymore
   - Make ontology2code work with python3
   - Properly fallback with the Zeitgeist version
   - rdflib directly to parse the trig files
   - Update Ontology2code to ba able to specify the output path

  Libzeitgeist:
   - Asynchronous out-parameters are only allowed at the end of argument lists
 *** THIS IS AN UNAVOIDABLE VALA API BREAK ***

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

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


[Touch-packages] [Bug 1805418] Re: Update pre-populator patch with correct desktop names

2019-01-30 Thread Jeremy Bicha
https://launchpad.net/ubuntu/+source/zeitgeist/1.0.1-1ubuntu2

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

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

Title:
  Update pre-populator patch with correct desktop names

Status in zeitgeist package in Ubuntu:
  Fix Released

Bug description:
  Use correct desktop names for totem, gedit and gnome-calculator.

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

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


[Touch-packages] [Bug 1813587] Re: libunistring ftbfs on 18.04 LTS

2019-01-29 Thread Jeremy Bicha
** Changed in: libunistring (Ubuntu Bionic)
   Status: Triaged => In Progress

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

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

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

Title:
  libunistring ftbfs on 18.04 LTS

Status in libunistring package in Ubuntu:
  Fix Released
Status in libunistring source package in Bionic:
  In Progress
Status in libunistring package in Debian:
  Unknown

Bug description:
  Impact
  --
  libunistring doesn't build from source which means someone would need to fix 
that problem before fixing any bugs in the libunistring package for Ubuntu 
18.04 LTS.

  Test Case
  -
  Does libunistring build successfully?

  Regression Potential
  
  We are simply backporting the workaround we applied in Ubuntu 18.10.

  Original Bug Report
  ---
  according to
  
http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html

  libunistring ftbfs.

  FAIL: test-thread_create
  

  glthread_create failed
  FAIL test-thread_create (exit status: 1)

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

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


[Touch-packages] [Bug 1805418] Re: Update pre-populator patch with correct desktop names

2019-01-29 Thread Jeremy Bicha
** Changed in: zeitgeist (Ubuntu)
   Status: Confirmed => Fix Committed

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

Title:
  Update pre-populator patch with correct desktop names

Status in zeitgeist package in Ubuntu:
  Fix Committed

Bug description:
  Use correct desktop names for totem, gedit and gnome-calculator.

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

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


[Touch-packages] [Bug 1813587] Re: libunistring ftbfs on 18.04 LTS

2019-01-29 Thread Jeremy Bicha
** Description changed:

+ Impact
+ --
+ libunistring doesn't build from source which means someone would need to fix 
that problem before fixing any bugs in the libunistring package for Ubuntu 
18.04 LTS.
+ 
+ Test Case
+ -
+ Does libunistring build successfully?
+ 
+ Regression Potential
+ 
+ We are simply backporting the workaround we applied in Ubuntu 18.10.
+ 
+ Original Bug Report
+ ---
  according to
  
http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html
  
  libunistring ftbfs.
  
  FAIL: test-thread_create
  
  
  glthread_create failed
  FAIL test-thread_create (exit status: 1)

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

Title:
  libunistring ftbfs on 18.04 LTS

Status in libunistring package in Ubuntu:
  Fix Released
Status in libunistring source package in Bionic:
  Triaged

Bug description:
  Impact
  --
  libunistring doesn't build from source which means someone would need to fix 
that problem before fixing any bugs in the libunistring package for Ubuntu 
18.04 LTS.

  Test Case
  -
  Does libunistring build successfully?

  Regression Potential
  
  We are simply backporting the workaround we applied in Ubuntu 18.10.

  Original Bug Report
  ---
  according to
  
http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html

  libunistring ftbfs.

  FAIL: test-thread_create
  

  glthread_create failed
  FAIL test-thread_create (exit status: 1)

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

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


[Touch-packages] [Bug 1763520] Re: after upgrade to bionic, printing fails without explanation / logs / debuggability

2019-01-29 Thread Jeremy Bicha
** No longer affects: cups-filters (Ubuntu Bionic)

** No longer affects: cups-filters (Ubuntu Cosmic)

** Changed in: gtk+3.0 (Ubuntu Bionic)
   Importance: Undecided => High

** Changed in: gtk+3.0 (Ubuntu Cosmic)
   Importance: Undecided => High

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

Title:
  after upgrade to bionic, printing fails without explanation / logs /
  debuggability

Status in cups-filters package in Ubuntu:
  Invalid
Status in gtk+3.0 package in Ubuntu:
  In Progress
Status in gtk+3.0 source package in Bionic:
  In Progress
Status in gtk+3.0 source package in Cosmic:
  In Progress

Bug description:
  [Impact]

  The problem occurs when the printer's driver package is updated and
  with this the PPD is replaced and one of the default settings of the
  queue is not available any more in the new PPD file. Then the setting
  is prefixed with "Custom." and with this the jobs fail.

  See comment #15 for more info.

  [Test Case]

  - Create a print queue with a PPD.
  - evince an arbitrary PDF file
  - Click the print icon
  - In the print dialog choose the newly created queue and choose some uncommon 
paper size (not custom). Click "Print".
  - Check /var/log/cups/error_log, the page size gets correctly received.
  - Close evince.
  - Stop CUPS, edit the PPD file removing the paper size you have selected for 
your job in the PageSize, PageRegion, PaperDimension, and ImageableArea lines.
  - Start CUPS.
  - Open the same PDF file again with evince, click Print and then select 
"Print" in the print dialog without changing anything.
  - The job fails, in /var/log/cups/error_log you see that the page size is 
prefixed with "Custom.".

  With the fixed package installed the job will print.

  [Regression Potential]

  The change applies only to saved settings of the print dialog not
  matching with any of the settings available in the PPD file. In rare
  cases the fix could fail by mis-understanding the setting and this way
  not being effective. For options which do not support setting custom
  values (the vast majority) the patch should always prevent a job
  failure though.

  [Other Info]

  Complete info about the bug and the fix in comment #15,

  Original bug description:

  I am unable to print to my network-attached printer after upgrade to
  bionic.  ps shows:

  lp   26047  0.0  0.0  91668  5756 ?S15:06   0:00  \_ 
HP-ENVY-4500-new 473 vorlon USCIS Form I-9 1 print-content-optimize=auto 
print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery 
noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB 
Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b 
job-originating-host-name=localhost date-time-at-creation= 
date-time-at-processing= time-at-creation=1523570792 
time-at-processing=1523570792 print-quality=4
  lp   26050  0.1  0.0  0 0 ?Z15:06   0:00  |   \_ [gs] 

  lp   26048  0.0  0.0  79908  3836 ?S15:06   0:00  \_ 
HP-ENVY-4500-new 473 vorlon USCIS Form I-9 1 print-content-optimize=auto 
print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery 
noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB 
Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b 
job-originating-host-name=localhost date-time-at-creation= 
date-time-at-processing= time-at-creation=1523570792 
time-at-processing=1523570792 print-quality=4
  root 26049  0.0  0.0  84388  6192 ?S15:06   0:00  \_ 
ipp://HP645106EA160E.local:631/ipp/print 473 vorlon USCIS Form I-9 1 
print-content-optimize=auto print-rendering-intent=auto cupsPrintQuality=4 
number-up=1 MediaType=Stationery noCollate print-scaling=auto 
PageSize=Custom.Letter.SM ColorModel=RGB Duplex=DuplexNoTumble 
job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b 
job-originating-host-name=localhost date-time-at-creation= 
date-time-at-processing= time-at-creation=1523570792 
time-at-processing=1523570792 print-quality=4

  Note the un-reaped gs process.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cups 2.2.7-1ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 12 15:07:49 2018
  InstallationDate: Installed on 2010-09-24 (2757 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  MachineType: LENOVO 2306CTO
  Papersize: letter
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: Upgraded to bionic on 2018-03-21 (21 days ago)
  dmi.bios.date: 

[Touch-packages] [Bug 1813587] Re: libunistring ftbfs on 18.04 LTS

2019-01-29 Thread Jeremy Bicha
** Tags removed: rls-bb-incoming
** Tags added: bionic

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

Title:
  libunistring ftbfs on 18.04 LTS

Status in libunistring package in Ubuntu:
  Fix Released
Status in libunistring source package in Bionic:
  Triaged

Bug description:
  according to
  
http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html

  libunistring ftbfs.

  FAIL: test-thread_create
  

  glthread_create failed
  FAIL test-thread_create (exit status: 1)

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

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


[Touch-packages] [Bug 1813591] Re: pygobject ftbfs in 18.04 LTS

2019-01-29 Thread Jeremy Bicha
** Tags removed: rls-bb-incoming
** Tags added: bionic

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

Title:
  pygobject ftbfs in 18.04 LTS

Status in pygobject package in Ubuntu:
  Fix Released
Status in pygobject source package in Bionic:
  In Progress

Bug description:
  Impact
  --
  pygobject doesn't build from source which means someone would need to fix 
that problem before fixing any bugs in the pygobject package for Ubuntu 18.04 
LTS.

  Test Case
  -
  Does pygobject build successfully?

  Regression Potential
  
  pygobject 3.28 is the intended version to match glib 2.56 but it missed the 
deadline for Ubuntu 18.04 LTS. So this fix is cherry-picking a small commit to 
fix the build tests with 18.04's glib2.0 2.56.

  The only change that is made in this upload is to the tests. There
  should be no effect on anything else.

  https://gitlab.gnome.org/GNOME/pygobject/commit/550bd7c7

  Original Bug Report
  ---
  according to
  
http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html

  pygobject ftbfs.

  ==
  FAIL: test_filenames (test_glib.TestGLib)
  --
  Traceback (most recent call last):
    File "/<>/tests/test_glib.py", line 66, in test_filenames
  self.assertTrue(isinstance(res, bytes))
  AssertionError: False is not true

  --
  Ran 1211 tests in 4.072s

  FAILED (failures=1, skipped=4, expected failures=12)

   torture test 1 (1 iterations): 0.012186 secs
   torture test 2 (1 iterations): 0.068459 secs
   torture test 3 (1 iterations): 0.029216 secs
   torture test 4 (1 iterations): 0.065890 secs
   
   Total: 0.175751 sec
  Makefile:905: recipe for target 'check.real' failed
  make[5]: *** [check.real] Error 1
  make[5]: Leaving directory '/<>/build-3.6/tests'
  Makefile:900: recipe for target 'check-local' failed
  make[4]: *** [check-local] Error 2
  Makefile:738: recipe for target 'check-am' failed
  make[3]: *** [check-am] Error 2
  Makefile:691: recipe for target 'check-recursive' failed
  make[2]: *** [check-recursive] Error 1

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

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


[Touch-packages] [Bug 1813587] Re: libunistring ftbfs on 18.04 LTS

2019-01-29 Thread Jeremy Bicha
** Changed in: libunistring (Ubuntu Bionic)
 Assignee: (unassigned) => Jeremy Bicha (jbicha)

** Changed in: libunistring (Ubuntu Bionic)
   Status: New => Triaged

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

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

Title:
  libunistring ftbfs on 18.04 LTS

Status in libunistring package in Ubuntu:
  Fix Released
Status in libunistring source package in Bionic:
  Triaged

Bug description:
  according to
  
http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html

  libunistring ftbfs.

  FAIL: test-thread_create
  

  glthread_create failed
  FAIL test-thread_create (exit status: 1)

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

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


[Touch-packages] [Bug 1813591] Re: pygobject ftbfs in 18.04 LTS

2019-01-29 Thread Jeremy Bicha
** Changed in: pygobject (Ubuntu Bionic)
   Status: Triaged => In Progress

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

Title:
  pygobject ftbfs in 18.04 LTS

Status in pygobject package in Ubuntu:
  Fix Released
Status in pygobject source package in Bionic:
  In Progress

Bug description:
  Impact
  --
  pygobject doesn't build from source which means someone would need to fix 
that problem before fixing any bugs in the pygobject package for Ubuntu 18.04 
LTS.

  Test Case
  -
  Does pygobject build successfully?

  Regression Potential
  
  pygobject 3.28 is the intended version to match glib 2.56 but it missed the 
deadline for Ubuntu 18.04 LTS. So this fix is cherry-picking a small commit to 
fix the build tests with 18.04's glib2.0 2.56.

  The only change that is made in this upload is to the tests. There
  should be no effect on anything else.

  https://gitlab.gnome.org/GNOME/pygobject/commit/550bd7c7

  Original Bug Report
  ---
  according to
  
http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html

  pygobject ftbfs.

  ==
  FAIL: test_filenames (test_glib.TestGLib)
  --
  Traceback (most recent call last):
    File "/<>/tests/test_glib.py", line 66, in test_filenames
  self.assertTrue(isinstance(res, bytes))
  AssertionError: False is not true

  --
  Ran 1211 tests in 4.072s

  FAILED (failures=1, skipped=4, expected failures=12)

   torture test 1 (1 iterations): 0.012186 secs
   torture test 2 (1 iterations): 0.068459 secs
   torture test 3 (1 iterations): 0.029216 secs
   torture test 4 (1 iterations): 0.065890 secs
   
   Total: 0.175751 sec
  Makefile:905: recipe for target 'check.real' failed
  make[5]: *** [check.real] Error 1
  make[5]: Leaving directory '/<>/build-3.6/tests'
  Makefile:900: recipe for target 'check-local' failed
  make[4]: *** [check-local] Error 2
  Makefile:738: recipe for target 'check-am' failed
  make[3]: *** [check-am] Error 2
  Makefile:691: recipe for target 'check-recursive' failed
  make[2]: *** [check-recursive] Error 1

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

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


[Touch-packages] [Bug 1813591] Re: pygobject ftbfs in 18.04 LTS

2019-01-29 Thread Jeremy Bicha
** Description changed:

+ Impact
+ --
+ pygobject doesn't build from source which means someone would need to fix 
that problem before fixing any bugs in the pygobject package for Ubuntu 18.04 
LTS.
+ 
+ Test Case
+ -
+ Does pygobject build successfully?
+ 
+ Regression Potential
+ 
+ pygobject 3.28 is the intended version to match glib 2.56 but it missed the 
deadline for Ubuntu 18.04 LTS. So this fix is cherry-picking a small commit to 
fix the build tests with 18.04's glib2.0 2.56.
+ 
+ The only change that is made in this upload is to the tests. There
+ should be no effect on anything else.
+ 
+ https://gitlab.gnome.org/GNOME/pygobject/commit/550bd7c7
+ 
+ Original Bug Report
+ ---
  according to
  
http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html
  
  pygobject ftbfs.
  
  ==
  FAIL: test_filenames (test_glib.TestGLib)
  --
  Traceback (most recent call last):
-   File "/<>/tests/test_glib.py", line 66, in test_filenames
- self.assertTrue(isinstance(res, bytes))
+   File "/<>/tests/test_glib.py", line 66, in test_filenames
+ self.assertTrue(isinstance(res, bytes))
  AssertionError: False is not true
  
  --
  Ran 1211 tests in 4.072s
  
  FAILED (failures=1, skipped=4, expected failures=12)
  
-   torture test 1 (1 iterations): 0.012186 secs
-   torture test 2 (1 iterations): 0.068459 secs
-   torture test 3 (1 iterations): 0.029216 secs
-   torture test 4 (1 iterations): 0.065890 secs
-   
-   Total: 0.175751 sec
+  torture test 1 (1 iterations): 0.012186 secs
+  torture test 2 (1 iterations): 0.068459 secs
+  torture test 3 (1 iterations): 0.029216 secs
+  torture test 4 (1 iterations): 0.065890 secs
+  
+  Total: 0.175751 sec
  Makefile:905: recipe for target 'check.real' failed
  make[5]: *** [check.real] Error 1
  make[5]: Leaving directory '/<>/build-3.6/tests'
  Makefile:900: recipe for target 'check-local' failed
  make[4]: *** [check-local] Error 2
  Makefile:738: recipe for target 'check-am' failed
  make[3]: *** [check-am] Error 2
  Makefile:691: recipe for target 'check-recursive' failed
  make[2]: *** [check-recursive] Error 1

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

Title:
  pygobject ftbfs in 18.04 LTS

Status in pygobject package in Ubuntu:
  Fix Released
Status in pygobject source package in Bionic:
  In Progress

Bug description:
  Impact
  --
  pygobject doesn't build from source which means someone would need to fix 
that problem before fixing any bugs in the pygobject package for Ubuntu 18.04 
LTS.

  Test Case
  -
  Does pygobject build successfully?

  Regression Potential
  
  pygobject 3.28 is the intended version to match glib 2.56 but it missed the 
deadline for Ubuntu 18.04 LTS. So this fix is cherry-picking a small commit to 
fix the build tests with 18.04's glib2.0 2.56.

  The only change that is made in this upload is to the tests. There
  should be no effect on anything else.

  https://gitlab.gnome.org/GNOME/pygobject/commit/550bd7c7

  Original Bug Report
  ---
  according to
  
http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html

  pygobject ftbfs.

  ==
  FAIL: test_filenames (test_glib.TestGLib)
  --
  Traceback (most recent call last):
    File "/<>/tests/test_glib.py", line 66, in test_filenames
  self.assertTrue(isinstance(res, bytes))
  AssertionError: False is not true

  --
  Ran 1211 tests in 4.072s

  FAILED (failures=1, skipped=4, expected failures=12)

   torture test 1 (1 iterations): 0.012186 secs
   torture test 2 (1 iterations): 0.068459 secs
   torture test 3 (1 iterations): 0.029216 secs
   torture test 4 (1 iterations): 0.065890 secs
   
   Total: 0.175751 sec
  Makefile:905: recipe for target 'check.real' failed
  make[5]: *** [check.real] Error 1
  make[5]: Leaving directory '/<>/build-3.6/tests'
  Makefile:900: recipe for target 'check-local' failed
  make[4]: *** [check-local] Error 2
  Makefile:738: recipe for target 'check-am' failed
  make[3]: *** [check-am] Error 2
  Makefile:691: recipe for target 'check-recursive' failed
  make[2]: *** [check-recursive] Error 1

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post 

[Touch-packages] [Bug 1813591] Re: pygobject ftbfs in 18.04 LTS

2019-01-29 Thread Jeremy Bicha
** Changed in: pygobject (Ubuntu Bionic)
 Assignee: (unassigned) => Jeremy Bicha (jbicha)

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

** Changed in: pygobject (Ubuntu Bionic)
   Status: New => Triaged

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

Title:
  pygobject ftbfs in 18.04 LTS

Status in pygobject package in Ubuntu:
  Fix Released
Status in pygobject source package in Bionic:
  Triaged

Bug description:
  according to
  
http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html

  pygobject ftbfs.

  ==
  FAIL: test_filenames (test_glib.TestGLib)
  --
  Traceback (most recent call last):
File "/<>/tests/test_glib.py", line 66, in test_filenames
  self.assertTrue(isinstance(res, bytes))
  AssertionError: False is not true

  --
  Ran 1211 tests in 4.072s

  FAILED (failures=1, skipped=4, expected failures=12)

torture test 1 (1 iterations): 0.012186 secs
torture test 2 (1 iterations): 0.068459 secs
torture test 3 (1 iterations): 0.029216 secs
torture test 4 (1 iterations): 0.065890 secs

Total: 0.175751 sec
  Makefile:905: recipe for target 'check.real' failed
  make[5]: *** [check.real] Error 1
  make[5]: Leaving directory '/<>/build-3.6/tests'
  Makefile:900: recipe for target 'check-local' failed
  make[4]: *** [check-local] Error 2
  Makefile:738: recipe for target 'check-am' failed
  make[3]: *** [check-am] Error 2
  Makefile:691: recipe for target 'check-recursive' failed
  make[2]: *** [check-recursive] Error 1

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

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


[Touch-packages] [Bug 1812143] Re: gsettings-desktop-schemas 3.31 breaks mutter 3.30

2019-01-24 Thread Jeremy Bicha
** Tags removed: block-proposed

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

Title:
  gsettings-desktop-schemas 3.31 breaks mutter 3.30

Status in gsettings-desktop-schemas package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Triaged
Status in ukwm package in Ubuntu:
  Confirmed

Bug description:
  We need to package mutter 3.31 and add a Breaks: mutter < 3.31 to
  gsettings-desktop-schemas.

  Running gsettings-desktop-schemas 3.31 with mutter 3.30 will result in
  gdm/gnome-shell being unable to start.

  Also, ukwm is a fork of mutter so the Kylin devs need to backport the
  relevant commits from mutter.

  The problematic gsettings commit was:
  https://gitlab.gnome.org/GNOME/gsettings-desktop-schemas/commit/c7eee129c

  I think the mutter commits can be found at
  https://gitlab.gnome.org/GNOME/mutter/merge_requests/133

  We could easily add a dummy key with the old name but I'm thinking the
  way forward is just to package the newer mutter.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1812143/+subscriptions

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


[Touch-packages] [Bug 1792544] Re: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x)

2019-01-23 Thread Jeremy Bicha
** Also affects: ubuntu-core-meta (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2
  (10.x)

Status in aide package in Ubuntu:
  Incomplete
Status in anope package in Ubuntu:
  Incomplete
Status in apache2 package in Ubuntu:
  Triaged
Status in apr-util package in Ubuntu:
  Fix Released
Status in clamav package in Ubuntu:
  Fix Released
Status in exim4 package in Ubuntu:
  Incomplete
Status in freeradius package in Ubuntu:
  Incomplete
Status in git package in Ubuntu:
  Fix Committed
Status in glib2.0 package in Ubuntu:
  Incomplete
Status in grep package in Ubuntu:
  Incomplete
Status in haproxy package in Ubuntu:
  Fix Released
Status in libpam-mount package in Ubuntu:
  Fix Released
Status in libselinux package in Ubuntu:
  Triaged
Status in nginx package in Ubuntu:
  Incomplete
Status in nmap package in Ubuntu:
  Incomplete
Status in pcre3 package in Ubuntu:
  Confirmed
Status in php-defaults package in Ubuntu:
  Triaged
Status in php7.2 package in Ubuntu:
  Won't Fix
Status in postfix package in Ubuntu:
  Incomplete
Status in python-pyscss package in Ubuntu:
  Incomplete
Status in quagga package in Ubuntu:
  Invalid
Status in rasqal package in Ubuntu:
  Incomplete
Status in slang2 package in Ubuntu:
  Incomplete
Status in sssd package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Triaged
Status in ubuntu-core-meta package in Ubuntu:
  New
Status in vte2.91 package in Ubuntu:
  Fix Released
Status in wget package in Ubuntu:
  Fix Committed
Status in zsh package in Ubuntu:
  Incomplete

Bug description:
  https://people.canonical.com/~ubuntu-
  archive/transitions/html/pcre2-main.html

  demotion of pcre3 in favor of pcre2. These packages need analysis what
  needs to be done for the demotion of pcre3:

  Packages which are ready to build with pcre2 should be marked as
  'Triaged', packages which are not ready should be marked as
  'Incomplete'.

  --
  For clarification: pcre2 is actually newer than pcre3.  pcre3 is just poorly 
named.

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

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


[Touch-packages] [Bug 1792544] Re: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x)

2019-01-23 Thread Jeremy Bicha
libslang2-modules is in universe although it's built from the slang2
source. I guess that means we can mark it invalid here?

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

Title:
  demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2
  (10.x)

Status in aide package in Ubuntu:
  Incomplete
Status in anope package in Ubuntu:
  New
Status in apache2 package in Ubuntu:
  New
Status in apr-util package in Ubuntu:
  Fix Released
Status in clamav package in Ubuntu:
  Fix Released
Status in exim4 package in Ubuntu:
  Incomplete
Status in freeradius package in Ubuntu:
  Incomplete
Status in git package in Ubuntu:
  Fix Committed
Status in glib2.0 package in Ubuntu:
  Incomplete
Status in grep package in Ubuntu:
  Incomplete
Status in haproxy package in Ubuntu:
  Fix Released
Status in libpam-mount package in Ubuntu:
  Fix Released
Status in libselinux package in Ubuntu:
  Triaged
Status in nginx package in Ubuntu:
  Incomplete
Status in nmap package in Ubuntu:
  Incomplete
Status in pcre3 package in Ubuntu:
  Confirmed
Status in php-defaults package in Ubuntu:
  Triaged
Status in php7.2 package in Ubuntu:
  Won't Fix
Status in postfix package in Ubuntu:
  Incomplete
Status in python-pyscss package in Ubuntu:
  Incomplete
Status in quagga package in Ubuntu:
  Invalid
Status in rasqal package in Ubuntu:
  Incomplete
Status in slang2 package in Ubuntu:
  Incomplete
Status in sssd package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Triaged
Status in vte2.91 package in Ubuntu:
  Fix Released
Status in wget package in Ubuntu:
  Fix Committed
Status in zsh package in Ubuntu:
  Incomplete

Bug description:
  https://people.canonical.com/~ubuntu-
  archive/transitions/html/pcre2-main.html

  demotion of pcre3 in favor of pcre2. These packages need analysis what
  needs to be done for the demotion of pcre3:

  Packages which are ready to build with pcre2 should be marked as
  'Triaged', packages which are not ready should be marked as
  'Incomplete'.

  --
  For clarification: pcre2 is actually newer than pcre3.  pcre3 is just poorly 
named.

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

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


[Touch-packages] [Bug 1792544] Re: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x)

2019-01-23 Thread Jeremy Bicha
quagga was another false Build-Depends so I filed a Debian bug
requesting they drop the pcre3 Build-Depends.

** Changed in: quagga (Ubuntu)
   Status: Incomplete => Invalid

** Description changed:

+ https://people.canonical.com/~ubuntu-
+ archive/transitions/html/pcre2-main.html
+ 
  demotion of pcre3 in favor of pcre2. These packages need analysis what
  needs to be done for the demotion of pcre3:
  
  Packages which are ready to build with pcre2 should be marked as
  'Triaged', packages which are not ready should be marked as
  'Incomplete'.
  
- aide
- apache2
- apr-util
- clamav
- exim4
- freeradius
- git
- glib2.0
- grep
- haproxy
- libpam-mount
- libselinux
- nginx
- nmap
- php7.2
- postfix
- python-pyscss
- quagga
- rasqal
- slang2
- sssd
- wget
- zsh
- 
  --
- 
- For clarification: pcre2 is actually newer than pcre3.  pcre3 is just
- poorly named (according to jbicha).
+ For clarification: pcre2 is actually newer than pcre3.  pcre3 is just poorly 
named.

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

Title:
  demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2
  (10.x)

Status in aide package in Ubuntu:
  Incomplete
Status in anope package in Ubuntu:
  New
Status in apache2 package in Ubuntu:
  New
Status in apr-util package in Ubuntu:
  Fix Released
Status in clamav package in Ubuntu:
  Fix Released
Status in exim4 package in Ubuntu:
  Incomplete
Status in freeradius package in Ubuntu:
  Incomplete
Status in git package in Ubuntu:
  Fix Committed
Status in glib2.0 package in Ubuntu:
  Incomplete
Status in grep package in Ubuntu:
  Incomplete
Status in haproxy package in Ubuntu:
  Fix Released
Status in libpam-mount package in Ubuntu:
  Fix Released
Status in libselinux package in Ubuntu:
  Triaged
Status in nginx package in Ubuntu:
  Incomplete
Status in nmap package in Ubuntu:
  Incomplete
Status in pcre3 package in Ubuntu:
  Confirmed
Status in php-defaults package in Ubuntu:
  Triaged
Status in php7.2 package in Ubuntu:
  Won't Fix
Status in postfix package in Ubuntu:
  Incomplete
Status in python-pyscss package in Ubuntu:
  Incomplete
Status in quagga package in Ubuntu:
  Invalid
Status in rasqal package in Ubuntu:
  Incomplete
Status in slang2 package in Ubuntu:
  Incomplete
Status in sssd package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Triaged
Status in vte2.91 package in Ubuntu:
  Fix Released
Status in wget package in Ubuntu:
  Fix Committed
Status in zsh package in Ubuntu:
  Incomplete

Bug description:
  https://people.canonical.com/~ubuntu-
  archive/transitions/html/pcre2-main.html

  demotion of pcre3 in favor of pcre2. These packages need analysis what
  needs to be done for the demotion of pcre3:

  Packages which are ready to build with pcre2 should be marked as
  'Triaged', packages which are not ready should be marked as
  'Incomplete'.

  --
  For clarification: pcre2 is actually newer than pcre3.  pcre3 is just poorly 
named.

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

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


[Touch-packages] [Bug 1792544] Re: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x)

2019-01-23 Thread Jeremy Bicha
** Also affects: anope (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2
  (10.x)

Status in aide package in Ubuntu:
  Incomplete
Status in anope package in Ubuntu:
  New
Status in apache2 package in Ubuntu:
  New
Status in apr-util package in Ubuntu:
  Fix Released
Status in clamav package in Ubuntu:
  Fix Released
Status in exim4 package in Ubuntu:
  Incomplete
Status in freeradius package in Ubuntu:
  Incomplete
Status in git package in Ubuntu:
  Fix Committed
Status in glib2.0 package in Ubuntu:
  Incomplete
Status in grep package in Ubuntu:
  Incomplete
Status in haproxy package in Ubuntu:
  Fix Released
Status in libpam-mount package in Ubuntu:
  Fix Released
Status in libselinux package in Ubuntu:
  Triaged
Status in nginx package in Ubuntu:
  Incomplete
Status in nmap package in Ubuntu:
  Incomplete
Status in pcre3 package in Ubuntu:
  Confirmed
Status in php-defaults package in Ubuntu:
  Triaged
Status in php7.2 package in Ubuntu:
  Won't Fix
Status in postfix package in Ubuntu:
  Incomplete
Status in python-pyscss package in Ubuntu:
  Incomplete
Status in quagga package in Ubuntu:
  Incomplete
Status in rasqal package in Ubuntu:
  Incomplete
Status in slang2 package in Ubuntu:
  Incomplete
Status in sssd package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Triaged
Status in vte2.91 package in Ubuntu:
  Fix Released
Status in wget package in Ubuntu:
  Fix Committed
Status in zsh package in Ubuntu:
  Incomplete

Bug description:
  demotion of pcre3 in favor of pcre2. These packages need analysis what
  needs to be done for the demotion of pcre3:

  Packages which are ready to build with pcre2 should be marked as
  'Triaged', packages which are not ready should be marked as
  'Incomplete'.

  aide
  apache2
  apr-util
  clamav
  exim4
  freeradius
  git
  glib2.0
  grep
  haproxy
  libpam-mount
  libselinux
  nginx
  nmap
  php7.2
  postfix
  python-pyscss
  quagga
  rasqal
  slang2
  sssd
  wget
  zsh

  --

  For clarification: pcre2 is actually newer than pcre3.  pcre3 is just
  poorly named (according to jbicha).

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

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


[Touch-packages] [Bug 1751006] Re: Journalctl compiled without pattern matching support, pcre2 is not in main

2019-01-23 Thread Jeremy Bicha
pcre2 was promoted to main today for Ubuntu 19.04.

** No longer affects: pcre2 (Ubuntu)

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  Journalctl compiled without pattern matching support, pcre2 is not in
  main

Status in systemd package in Ubuntu:
  Triaged

Bug description:
  Please add pattern matching support to journalctl.  At the moment, the
  -g (--grep) option as described in the man page doesn't work:

  ╰─▶ journalctl --grep=xhci-hcd 
  Compiled without pattern matching support

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

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


[Touch-packages] [Bug 1792544] Re: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x)

2019-01-23 Thread Jeremy Bicha
** Changed in: clamav (Ubuntu)
   Status: Triaged => Fix Committed

** Package changed: php7.3 (Ubuntu) => php-defaults (Ubuntu)

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

Title:
  demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2
  (10.x)

Status in aide package in Ubuntu:
  Incomplete
Status in apache2 package in Ubuntu:
  New
Status in apr-util package in Ubuntu:
  Fix Released
Status in clamav package in Ubuntu:
  Fix Committed
Status in exim4 package in Ubuntu:
  Incomplete
Status in freeradius package in Ubuntu:
  Incomplete
Status in git package in Ubuntu:
  Fix Committed
Status in glib2.0 package in Ubuntu:
  Incomplete
Status in grep package in Ubuntu:
  Incomplete
Status in haproxy package in Ubuntu:
  Fix Released
Status in libpam-mount package in Ubuntu:
  Fix Released
Status in libselinux package in Ubuntu:
  Triaged
Status in nginx package in Ubuntu:
  Incomplete
Status in nmap package in Ubuntu:
  Incomplete
Status in pcre3 package in Ubuntu:
  Confirmed
Status in php-defaults package in Ubuntu:
  Triaged
Status in php7.2 package in Ubuntu:
  Won't Fix
Status in postfix package in Ubuntu:
  Incomplete
Status in python-pyscss package in Ubuntu:
  Incomplete
Status in quagga package in Ubuntu:
  Incomplete
Status in rasqal package in Ubuntu:
  Incomplete
Status in slang2 package in Ubuntu:
  Incomplete
Status in sssd package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Triaged
Status in vte2.91 package in Ubuntu:
  Fix Released
Status in wget package in Ubuntu:
  Fix Committed
Status in zsh package in Ubuntu:
  Incomplete

Bug description:
  demotion of pcre3 in favor of pcre2. These packages need analysis what
  needs to be done for the demotion of pcre3:

  Packages which are ready to build with pcre2 should be marked as
  'Triaged', packages which are not ready should be marked as
  'Incomplete'.

  aide
  apache2
  apr-util
  clamav
  exim4
  freeradius
  git
  glib2.0
  grep
  haproxy
  libpam-mount
  libselinux
  nginx
  nmap
  php7.2
  postfix
  python-pyscss
  quagga
  rasqal
  slang2
  sssd
  wget
  zsh

  --

  For clarification: pcre2 is actually newer than pcre3.  pcre3 is just
  poorly named (according to jbicha).

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

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


[Touch-packages] [Bug 1792544] Re: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x)

2019-01-23 Thread Jeremy Bicha
** Changed in: wget (Ubuntu)
   Status: Incomplete => Fix Committed

** Changed in: libpam-mount (Ubuntu)
   Status: Triaged => Fix Committed

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

Title:
  demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2
  (10.x)

Status in aide package in Ubuntu:
  Incomplete
Status in apache2 package in Ubuntu:
  New
Status in apr-util package in Ubuntu:
  Fix Released
Status in clamav package in Ubuntu:
  Triaged
Status in exim4 package in Ubuntu:
  Incomplete
Status in freeradius package in Ubuntu:
  Incomplete
Status in git package in Ubuntu:
  Fix Committed
Status in glib2.0 package in Ubuntu:
  Incomplete
Status in grep package in Ubuntu:
  Incomplete
Status in haproxy package in Ubuntu:
  Fix Released
Status in libpam-mount package in Ubuntu:
  Fix Committed
Status in libselinux package in Ubuntu:
  Triaged
Status in nginx package in Ubuntu:
  Incomplete
Status in nmap package in Ubuntu:
  Incomplete
Status in pcre3 package in Ubuntu:
  Confirmed
Status in php7.2 package in Ubuntu:
  Won't Fix
Status in php7.3 package in Ubuntu:
  Triaged
Status in postfix package in Ubuntu:
  Incomplete
Status in python-pyscss package in Ubuntu:
  Incomplete
Status in quagga package in Ubuntu:
  Incomplete
Status in rasqal package in Ubuntu:
  Incomplete
Status in slang2 package in Ubuntu:
  Incomplete
Status in sssd package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Triaged
Status in vte2.91 package in Ubuntu:
  Fix Released
Status in wget package in Ubuntu:
  Fix Committed
Status in zsh package in Ubuntu:
  Incomplete

Bug description:
  demotion of pcre3 in favor of pcre2. These packages need analysis what
  needs to be done for the demotion of pcre3:

  Packages which are ready to build with pcre2 should be marked as
  'Triaged', packages which are not ready should be marked as
  'Incomplete'.

  aide
  apache2
  apr-util
  clamav
  exim4
  freeradius
  git
  glib2.0
  grep
  haproxy
  libpam-mount
  libselinux
  nginx
  nmap
  php7.2
  postfix
  python-pyscss
  quagga
  rasqal
  slang2
  sssd
  wget
  zsh

  --

  For clarification: pcre2 is actually newer than pcre3.  pcre3 is just
  poorly named (according to jbicha).

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

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


[Touch-packages] [Bug 1792544] Re: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x)

2019-01-23 Thread Jeremy Bicha
** Changed in: vte2.91 (Ubuntu)
   Status: Triaged => Fix Committed

** Changed in: haproxy (Ubuntu)
   Status: Triaged => Fix Committed

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

** Changed in: vte2.91 (Ubuntu)
   Status: Fix Committed => Fix Released

** Changed in: git (Ubuntu)
   Status: Triaged => Fix Committed

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

Title:
  demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2
  (10.x)

Status in aide package in Ubuntu:
  Incomplete
Status in apache2 package in Ubuntu:
  New
Status in apr-util package in Ubuntu:
  Fix Released
Status in clamav package in Ubuntu:
  Triaged
Status in exim4 package in Ubuntu:
  Incomplete
Status in freeradius package in Ubuntu:
  Incomplete
Status in git package in Ubuntu:
  Fix Committed
Status in glib2.0 package in Ubuntu:
  Incomplete
Status in grep package in Ubuntu:
  Incomplete
Status in haproxy package in Ubuntu:
  Fix Released
Status in libpam-mount package in Ubuntu:
  Triaged
Status in libselinux package in Ubuntu:
  Triaged
Status in nginx package in Ubuntu:
  Incomplete
Status in nmap package in Ubuntu:
  Incomplete
Status in pcre3 package in Ubuntu:
  Confirmed
Status in php7.2 package in Ubuntu:
  Won't Fix
Status in php7.3 package in Ubuntu:
  Triaged
Status in postfix package in Ubuntu:
  Incomplete
Status in python-pyscss package in Ubuntu:
  Incomplete
Status in quagga package in Ubuntu:
  Incomplete
Status in rasqal package in Ubuntu:
  Incomplete
Status in slang2 package in Ubuntu:
  Incomplete
Status in sssd package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Triaged
Status in vte2.91 package in Ubuntu:
  Fix Released
Status in wget package in Ubuntu:
  Incomplete
Status in zsh package in Ubuntu:
  Incomplete

Bug description:
  demotion of pcre3 in favor of pcre2. These packages need analysis what
  needs to be done for the demotion of pcre3:

  Packages which are ready to build with pcre2 should be marked as
  'Triaged', packages which are not ready should be marked as
  'Incomplete'.

  aide
  apache2
  apr-util
  clamav
  exim4
  freeradius
  git
  glib2.0
  grep
  haproxy
  libpam-mount
  libselinux
  nginx
  nmap
  php7.2
  postfix
  python-pyscss
  quagga
  rasqal
  slang2
  sssd
  wget
  zsh

  --

  For clarification: pcre2 is actually newer than pcre3.  pcre3 is just
  poorly named (according to jbicha).

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

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


[Touch-packages] [Bug 1812903] Re: Please remove libproxy1-plugin-mozjs/s390x on disco

2019-01-22 Thread Jeremy Bicha
** Package changed: ubuntu => libproxy (Ubuntu)

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

Title:
  Please remove libproxy1-plugin-mozjs/s390x on disco

Status in libproxy package in Ubuntu:
  New

Bug description:
  Please remove the NBS libproxy1-plugiin-mozjs from s390x.

  It does not show up on
  https://people.canonical.com/~ubuntu-archive/nbs.html

  But it does show at
  
https://people.canonical.com/~ubuntu-archive/proposed-migration/disco_uninst.txt

  The binary package is intentionally not built on s390x because mozjs60
  is not available on s390x currently.

  $ rmadison libproxy1-plugin-mozjs
   libproxy1-plugin-mozjs | 0.4.15-3 | disco/universe | s390x
   libproxy1-plugin-mozjs | 0.4.15-5 | disco/universe | amd64, arm64, armhf, 
i386, ppc64el

  $ rmadison libproxy
   libproxy | 0.4.15-2 | cosmic   | source
   libproxy | 0.4.15-5 | disco| source

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

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


[Touch-packages] [Bug 1771031] Re: Please remove libgnome and friends from Ubuntu

2019-01-22 Thread Jeremy Bicha
Steve said he'd prefer to handle the removals semi-automatically when
they're removed from Debian so I'm closing this bug to not clutter the
Archive Admin bug queue.

** Changed in: libgnome-keyring (Ubuntu)
   Status: New => Invalid

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

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

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

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

Title:
  Please remove libgnome and friends from Ubuntu

Status in gnome-vfs package in Ubuntu:
  Invalid
Status in libbonobo package in Ubuntu:
  Invalid
Status in libbonoboui package in Ubuntu:
  Invalid
Status in libgnome package in Ubuntu:
  Invalid
Status in libgnome-keyring package in Ubuntu:
  Invalid
Status in libgnomeui package in Ubuntu:
  Invalid
Status in linsmith package in Ubuntu:
  Invalid
Status in orbit2 package in Ubuntu:
  Invalid
Status in resapplet package in Ubuntu:
  Fix Released
Status in winefish package in Ubuntu:
  Fix Released

Bug description:
  libgnome has been removed from Debian Testing and will not be included
  in the Debian 10 "Buster" release. We should do the same. If we do it
  now, maybe some projects will do the needed porting work away from
  libgnome (porting to gtk3 is probably needed) in time for Ubuntu 20.04
  LTS or Debian 10. Users who are hurt by these removals can keep using
  Ubuntu 18.04 LTS for a few years.

  resapplet and winefish are unmaintained and aren't in Debian.

  linsmith is in Debian and will be either ported to gtk3 or removed
  eventually, but I don't think Ubuntu needs to wait for that.

  This bug depends on these other removals:
  DONE: gnome-python LP: #1739800
  DONE: gnome-sharp2 LP: #1771025
  DONE: shutter LP: #1771030

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

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


[Touch-packages] [Bug 1771031] Re: Please remove libgnome and friends from Ubuntu

2019-01-22 Thread Jeremy Bicha
** Changed in: gnome-vfs (Ubuntu)
   Status: New => Invalid

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

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

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

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

Title:
  Please remove libgnome and friends from Ubuntu

Status in gnome-vfs package in Ubuntu:
  Invalid
Status in libbonobo package in Ubuntu:
  Invalid
Status in libbonoboui package in Ubuntu:
  Invalid
Status in libgnome package in Ubuntu:
  Invalid
Status in libgnome-keyring package in Ubuntu:
  Invalid
Status in libgnomeui package in Ubuntu:
  Invalid
Status in linsmith package in Ubuntu:
  Invalid
Status in orbit2 package in Ubuntu:
  Invalid
Status in resapplet package in Ubuntu:
  Fix Released
Status in winefish package in Ubuntu:
  Fix Released

Bug description:
  libgnome has been removed from Debian Testing and will not be included
  in the Debian 10 "Buster" release. We should do the same. If we do it
  now, maybe some projects will do the needed porting work away from
  libgnome (porting to gtk3 is probably needed) in time for Ubuntu 20.04
  LTS or Debian 10. Users who are hurt by these removals can keep using
  Ubuntu 18.04 LTS for a few years.

  resapplet and winefish are unmaintained and aren't in Debian.

  linsmith is in Debian and will be either ported to gtk3 or removed
  eventually, but I don't think Ubuntu needs to wait for that.

  This bug depends on these other removals:
  DONE: gnome-python LP: #1739800
  DONE: gnome-sharp2 LP: #1771025
  DONE: shutter LP: #1771030

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

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


[Touch-packages] [Bug 1763628] Re: autopkgtests are failing on valgrind

2019-01-22 Thread Jeremy Bicha
I asked bdmurray in #ubuntu-devel and he'd rather not have an SRU just
to fix an autopkgtest like this.

I'm closing since this issue is fixed in the current development
release.

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

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

Title:
  autopkgtests are failing on valgrind

Status in colord package in Ubuntu:
  Fix Released

Bug description:
  This happens now

  autopkgtest [07:42:07]: test make-check: ---]
  autopkgtest [07:42:08]: test make-check:  - - - - - - - - - - results - - - - 
- - - - - -
  make-check   FAIL stderr: ==9257== 8 bytes in 1 blocks are definitely 
lost in loss record 67 of 368
  autopkgtest [07:42:08]: test make-check:  - - - - - - - - - - stderr - - - - 
- - - - - -
  ==9257== 8 bytes in 1 blocks are definitely lost in loss record 67 of 368
  ==9257==at 0x4C2FB0F: malloc (in 
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
  ==9257==by 0x18EF2D: xmalloc (in /bin/bash)
  ==9257==by 0x18898A: set_default_locale (in /bin/bash)
  ==9257==by 0x137E66: main (in /bin/bash)
  ==9257== 
  ==9505== 8 bytes in 1 blocks are definitely lost in loss record 67 of 368
  ==9505==at 0x4C2FB0F: malloc (in 
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
  ==9505==by 0x18EF2D: xmalloc (in /bin/bash)
  ==9505==by 0x18898A: set_default_locale (in /bin/bash)
  ==9505==by 0x137E66: main (in /bin/bash)
  ==9505== 
  autopkgtest [07:42:08]:  summary
  make-check   FAIL stderr: ==9257== 8 bytes in 1 blocks are definitely 
lost in loss record 67 of 368

  From http://autopkgtest.ubuntu.com/packages/c/colord/bionic/amd64 it
  looks like it's cause by the new glib2.0, but I just tried on my
  machine without that package and it still happened.

  Could you have a look please? Looks like it might not actually be
  colord's fault here, but maybe we want to reconsider running under
  valgrind at least for the autopktests?

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

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


[Touch-packages] [Bug 1762391] Re: pam_group.so is not evaluated by gnome-terminal

2019-01-22 Thread Jeremy Bicha
** No longer affects: gnome-terminal (Ubuntu Bionic)

** No longer affects: gnome-terminal (Ubuntu Cosmic)

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

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

Status in systemd:
  New
Status in gnome-terminal package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  New
Status in systemd source package in Bionic:
  New
Status in systemd source package in Cosmic:
  New

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

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


[Touch-packages] [Bug 1763628] Re: autopkgtests are failing on valgrind

2019-01-21 Thread Jeremy Bicha
autopkgtests pass now in cosmic and in disco (well once my 1.4.3-4
upload autosyncs in a few hours).

Do you think it's worth doing a bionic SRU if we can identify what fixed
the autopkgtests in newer versions?

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

Title:
  autopkgtests are failing on valgrind

Status in colord package in Ubuntu:
  New

Bug description:
  This happens now

  autopkgtest [07:42:07]: test make-check: ---]
  autopkgtest [07:42:08]: test make-check:  - - - - - - - - - - results - - - - 
- - - - - -
  make-check   FAIL stderr: ==9257== 8 bytes in 1 blocks are definitely 
lost in loss record 67 of 368
  autopkgtest [07:42:08]: test make-check:  - - - - - - - - - - stderr - - - - 
- - - - - -
  ==9257== 8 bytes in 1 blocks are definitely lost in loss record 67 of 368
  ==9257==at 0x4C2FB0F: malloc (in 
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
  ==9257==by 0x18EF2D: xmalloc (in /bin/bash)
  ==9257==by 0x18898A: set_default_locale (in /bin/bash)
  ==9257==by 0x137E66: main (in /bin/bash)
  ==9257== 
  ==9505== 8 bytes in 1 blocks are definitely lost in loss record 67 of 368
  ==9505==at 0x4C2FB0F: malloc (in 
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
  ==9505==by 0x18EF2D: xmalloc (in /bin/bash)
  ==9505==by 0x18898A: set_default_locale (in /bin/bash)
  ==9505==by 0x137E66: main (in /bin/bash)
  ==9505== 
  autopkgtest [07:42:08]:  summary
  make-check   FAIL stderr: ==9257== 8 bytes in 1 blocks are definitely 
lost in loss record 67 of 368

  From http://autopkgtest.ubuntu.com/packages/c/colord/bionic/amd64 it
  looks like it's cause by the new glib2.0, but I just tried on my
  machine without that package and it still happened.

  Could you have a look please? Looks like it might not actually be
  colord's fault here, but maybe we want to reconsider running under
  valgrind at least for the autopktests?

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

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


[Touch-packages] [Bug 1808233] Re: Update gtk to 3.24.4

2019-01-21 Thread Jeremy Bicha
** Summary changed:

- Update gtk to 3.24.3
+ Update gtk to 3.24.4

** Description changed:

  Impact
  ==
  There is a new release in the stable 3.24 series.
  
  This also bundles the emoji fixes from LP: #1807719 and LP: #1807721 and
  the Xfce flickering fix from LP: #1798861.
  
  https://gitlab.gnome.org/GNOME/gtk/blob/gtk-3-24/NEWS
- https://gitlab.gnome.org/GNOME/gtk/compare/3.24.1...3.24.3
+ https://gitlab.gnome.org/GNOME/gtk/compare/3.24.1...3.24.4
  
  Test Case
  =
  Run several apps in the default Ubuntu install and make sure that there are 
no visible regressions.
+ 
+ Make sure that GTK switches look OK.
  
  We will also be checking Xfce to validate the fix for LP: #1798861.
  
  Regression Potential
  
  There is a standing microrelease exception for GNOME point releases.
  
  I believe this is the second time in recent history that we've pushed a
  gtk point release as an SRU. The other example was 3.22.25 for Ubuntu
  17.10 (LP: #1728421). We never ended up doing one for Ubuntu 18.04 LTS
  since it already included 3.22.30, the final 3.22 release. It hasn't
  been practical to update 18.04's gtk to  the 3.24 series (bumped
  dependencies are one problem).
  
  https://wiki.ubuntu.com/StableReleaseUpdates#GNOME
  
  By the way, pre-release gtk3 is actually getting a bit more testing than
  a year ago since more developers and users are using development Flatpak
  releases of popular GNOME apps. (On the other hand, there were a few
- regressions in the 3.24.2 release.)
+ regressions in the 3.24.2 and 3.24.3 releases.)
  
  This update changes the ON/OFF switches for GNOME's default Adwaita
- theme to use ⏽/⭘. Previously, it was ❙/○ for most languages but ON/OFF
- for English (because English has short words that could fit on a
- switch). This doesn't affect default Ubuntu 18.10 which uses Yaru which
- doesn't use labels on its switches. This is technically a UI change, but
- it is useful for compatibility with Flatpak apps that are being built
- with the new GTK. This change is small enough that it could be reverted
- for Ubuntu 18.10 if necessary.
+ theme to use ❙/○ for all languages (or ⏽/⭘ if they are supported in a
+ font you have installed: currently, that's fonts-symbola which we no
+ longer install by default). Previously, it was ❙/○ for most languages
+ but ON/OFF for English (because English has short words that could fit
+ on a switch). This doesn't affect default Ubuntu 18.10 which uses Yaru
+ which doesn't use labels on its switches. This is technically a UI
+ change, but it is useful for compatibility with Flatpak apps that are
+ being built with the new GTK. This change is small enough that it could
+ be reverted for Ubuntu 18.10 if necessary.
  
  Other Info
  ==
  The commit history shows themeing changes to the GNOME default themes 
(Adwaita and Adwaita Dark which are bundled inside gtk3). But those changes 
were reverted for this release to make it easier for distros like us to push 
the update to our stable release.
  
- The next scheduled gtk3 release (3.24.4 ? in March?) will include those
+ The next scheduled gtk3 release (3.24.5 ? in March?) will include those
  changes. See https://blog.gtk.org/2019/01/14/theme-changes-in-gtk-3/ for
  more details.

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

Title:
  Update gtk to 3.24.4

Status in gtk+3.0 package in Ubuntu:
  Fix Committed
Status in gtk+3.0 source package in Cosmic:
  In Progress

Bug description:
  Impact
  ==
  There is a new release in the stable 3.24 series.

  This also bundles the emoji fixes from LP: #1807719 and LP: #1807721
  and the Xfce flickering fix from LP: #1798861.

  https://gitlab.gnome.org/GNOME/gtk/blob/gtk-3-24/NEWS
  https://gitlab.gnome.org/GNOME/gtk/compare/3.24.1...3.24.4

  Test Case
  =
  Run several apps in the default Ubuntu install and make sure that there are 
no visible regressions.

  Make sure that GTK switches look OK.

  We will also be checking Xfce to validate the fix for LP: #1798861.

  Regression Potential
  
  There is a standing microrelease exception for GNOME point releases.

  I believe this is the second time in recent history that we've pushed
  a gtk point release as an SRU. The other example was 3.22.25 for
  Ubuntu 17.10 (LP: #1728421). We never ended up doing one for Ubuntu
  18.04 LTS since it already included 3.22.30, the final 3.22 release.
  It hasn't been practical to update 18.04's gtk to  the 3.24 series
  (bumped dependencies are one problem).

  https://wiki.ubuntu.com/StableReleaseUpdates#GNOME

  By the way, pre-release gtk3 is actually getting a bit more testing
  than a year ago since more developers and users are using development
  Flatpak releases of popular GNOME apps. (On the other hand, there were
  a few regressions in the 3.24.2 and 

[Touch-packages] [Bug 1771031] Re: Please remove libgnome and friends from Ubuntu

2019-01-20 Thread Jeremy Bicha
** Description changed:

  libgnome has been removed from Debian Testing and will not be included
  in the Debian 10 "Buster" release. We should do the same. If we do it
  now, maybe some projects will do the needed porting work away from
  libgnome (porting to gtk3 is probably needed) in time for Ubuntu 20.04
  LTS or Debian 10. Users who are hurt by these removals can keep using
  Ubuntu 18.04 LTS for a few years.
  
  resapplet and winefish are unmaintained and aren't in Debian.
  
  linsmith is in Debian and will be either ported to gtk3 or removed
  eventually, but I don't think Ubuntu needs to wait for that.
  
  This bug depends on these other removals:
- gnome-python LP: #1739800
+ DONE: gnome-python LP: #1739800
  DONE: gnome-sharp2 LP: #1771025
  DONE: shutter LP: #1771030

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

Title:
  Please remove libgnome and friends from Ubuntu

Status in gnome-vfs package in Ubuntu:
  New
Status in libbonobo package in Ubuntu:
  New
Status in libbonoboui package in Ubuntu:
  New
Status in libgnome package in Ubuntu:
  New
Status in libgnome-keyring package in Ubuntu:
  New
Status in libgnomeui package in Ubuntu:
  New
Status in linsmith package in Ubuntu:
  New
Status in orbit2 package in Ubuntu:
  New
Status in resapplet package in Ubuntu:
  New
Status in winefish package in Ubuntu:
  New

Bug description:
  libgnome has been removed from Debian Testing and will not be included
  in the Debian 10 "Buster" release. We should do the same. If we do it
  now, maybe some projects will do the needed porting work away from
  libgnome (porting to gtk3 is probably needed) in time for Ubuntu 20.04
  LTS or Debian 10. Users who are hurt by these removals can keep using
  Ubuntu 18.04 LTS for a few years.

  resapplet and winefish are unmaintained and aren't in Debian.

  linsmith is in Debian and will be either ported to gtk3 or removed
  eventually, but I don't think Ubuntu needs to wait for that.

  This bug depends on these other removals:
  DONE: gnome-python LP: #1739800
  DONE: gnome-sharp2 LP: #1771025
  DONE: shutter LP: #1771030

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

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


[Touch-packages] [Bug 1812143] [NEW] gsettings-desktop-schemas 3.31 breaks mutter 3.30

2019-01-16 Thread Jeremy Bicha
Public bug reported:

We need to package mutter 3.31 and add a Breaks: mutter < 3.31 to
gsettings-desktop-schemas.

Running gsettings-desktop-schemas 3.31 with mutter 3.30 will result in
gdm/gnome-shell being unable to start.

Also, ukwm is a fork of mutter so the Kylin devs need to backport the
relevant commits from mutter.

The problematic gsettings commit was:
https://gitlab.gnome.org/GNOME/gsettings-desktop-schemas/commit/c7eee129c

I think the mutter commits can be found at
https://gitlab.gnome.org/GNOME/mutter/merge_requests/133

** Affects: gsettings-desktop-schemas (Ubuntu)
 Importance: High
 Status: Triaged

** Affects: mutter (Ubuntu)
 Importance: High
 Status: Triaged

** Affects: ukwm (Ubuntu)
 Importance: High
 Status: New


** Tags: block-proposed disco

** Changed in: gsettings-desktop-schemas (Ubuntu)
   Status: New => Triaged

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

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

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

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

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

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

Title:
  gsettings-desktop-schemas 3.31 breaks mutter 3.30

Status in gsettings-desktop-schemas package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Triaged
Status in ukwm package in Ubuntu:
  New

Bug description:
  We need to package mutter 3.31 and add a Breaks: mutter < 3.31 to
  gsettings-desktop-schemas.

  Running gsettings-desktop-schemas 3.31 with mutter 3.30 will result in
  gdm/gnome-shell being unable to start.

  Also, ukwm is a fork of mutter so the Kylin devs need to backport the
  relevant commits from mutter.

  The problematic gsettings commit was:
  https://gitlab.gnome.org/GNOME/gsettings-desktop-schemas/commit/c7eee129c

  I think the mutter commits can be found at
  https://gitlab.gnome.org/GNOME/mutter/merge_requests/133

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1812143/+subscriptions

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


[Touch-packages] [Bug 1807721] Re: Fix variant selection in emoji chooser

2019-01-15 Thread Jeremy Bicha
Uploaded to the cosmic queue now that 3.24.3 was released.

** Changed in: gtk+3.0 (Ubuntu Cosmic)
   Status: Triaged => In Progress

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

Title:
  Fix variant selection in emoji chooser

Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Bionic:
  In Progress
Status in gtk+3.0 source package in Cosmic:
  In Progress

Bug description:
  Impact
  ==
  The variant selector in the emoji chooser was broken and will crash the app 
if used.

  Test Case
  =
  In an app like gedit, right click in the text area and select Insert Emoji
  Look for one of the "people" emoji.
  Right-click (or long-click) on the emoji and select one of the skin tones 
instead of the default yellow.
  The emoji with the skin tone you selected should be added to the text area.

  Regression Potential
  
  This fix was included in the gtk 3.24.2 release. There is a standing 
microrelease exception for GNOME point releases.

  GTK 3.24 was a big enough release (with some bumped dependencies) that
  it's not very practical to push to Ubuntu 18.04 LTS so we selectively
  cherry-pick fixes there.

  https://wiki.ubuntu.com/StableReleaseUpdates#GNOME

  https://gitlab.gnome.org/GNOME/gtk/commit/dbbc7b3859f4b
  https://gitlab.gnome.org/GNOME/gtk/issues/1398

  Other Info
  ==
  This bug is fixed in gtk 3.24.2. Its SRU for cosmic is being tracked in LP: 
#1808233

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1807721/+subscriptions

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


[Touch-packages] [Bug 1798861] Re: Tooltips flicker constantly in GTK3 applications

2019-01-15 Thread Jeremy Bicha
** Also affects: gtk+3.0 (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Changed in: gtk+3.0 (Ubuntu Cosmic)
   Status: New => In Progress

** Changed in: gtk+3.0 (Ubuntu Cosmic)
   Importance: Undecided => Low

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

Title:
  Tooltips flicker constantly in GTK3 applications

Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Cosmic:
  In Progress
Status in gtk+3.0 package in Debian:
  Fix Released

Bug description:
  Tooltips are flicker constantly (i.e. repeatedly shown and the hidden
  again) in GTK3 applications under XFCE.

  It is a regression in the recent GTK 3.24.

  This is the upstream report and fix:
  https://gitlab.gnome.org/GNOME/gtk/issues/1371
  
https://gitlab.gnome.org/GNOME/gtk/commit/9b7d886b723132eade2e76f3fd179cf81b7601f2

  A workaround for XFCE is as follows:

  Open Settings Editor.
  Set xsettings -> Gtk -> CursorThemeSize to 16.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libgtk-3-0 3.24.1-1ubuntu2
  Uname: Linux 4.19.0-041900rc8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  Date: Fri Oct 19 12:23:53 2018
  InstallationDate: Installed on 2017-02-01 (624 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gtk+3.0
  UpgradeStatus: Upgraded to cosmic on 2018-10-18 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1798861/+subscriptions

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


[Touch-packages] [Bug 1807719] Re: Some emoji in emoji chooser are black & white

2019-01-15 Thread Jeremy Bicha
** Changed in: gtk+3.0 (Ubuntu Cosmic)
   Status: Triaged => In Progress

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

Title:
  Some emoji in emoji chooser are black & white

Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Bionic:
  In Progress
Status in gtk+3.0 source package in Cosmic:
  In Progress

Bug description:
  Impact
  ==
  Some emoji in the emoji chooser show as black & white.

  This is because these emoji default to "text presentation" instead of
  "emoji presentation".

  More information and a screenshot can be found in the pango issue
  linked below.

  Test Case
  =
  In an app like gedit, right click in the text area and select Insert Emoji
  Browse through the emoji list. All should be in full color.

  Regression Potential
  
  This fix was included in the gtk 3.24.2 release. There is a standing 
microrelease exception for GNOME point releases.

  GTK 3.24 was a big enough release (with some bumped dependencies) that
  it's not very practical to push to Ubuntu 18.04 LTS so we selectively
  cherry-pick fixes there.

  https://wiki.ubuntu.com/StableReleaseUpdates#GNOME

  https://gitlab.gnome.org/GNOME/pango/issues/334
  https://gitlab.gnome.org/GNOME/gtk/commit/aac38198a3f5
  https://gitlab.gnome.org/GNOME/gtk/commit/b74e3209a5af0

  Other Info
  ==
  This adds an extra variation selector byte to each emoji added via the emoji 
chooser. (Many emoji are made up of multiple bytes.) This will not affect emoji 
added to GTK apps in other ways, such as copying and pasting from an app where 
the emoji doesn't have that variation selector added to it.

  This bug is fixed in gtk 3.24.2. Its SRU for cosmic is being tracked
  in LP: #1808233

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1807719/+subscriptions

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


[Touch-packages] [Bug 1808233] Re: Update gtk to 3.24.3

2019-01-15 Thread Jeremy Bicha
** Changed in: gtk+3.0 (Ubuntu Cosmic)
   Status: Triaged => In Progress

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

Title:
  Update gtk to 3.24.3

Status in gtk+3.0 package in Ubuntu:
  Fix Committed
Status in gtk+3.0 source package in Cosmic:
  In Progress

Bug description:
  Impact
  ==
  There is a new release in the stable 3.24 series.

  This also bundles the emoji fixes from LP: #1807719 and LP: #1807721
  and the Xfce flickering fix from LP: #1798861.

  https://gitlab.gnome.org/GNOME/gtk/blob/gtk-3-24/NEWS
  https://gitlab.gnome.org/GNOME/gtk/compare/3.24.1...3.24.3

  Test Case
  =
  Run several apps in the default Ubuntu install and make sure that there are 
no visible regressions.

  We will also be checking Xfce to validate the fix for LP: #1798861.

  Regression Potential
  
  There is a standing microrelease exception for GNOME point releases.

  I believe this is the second time in recent history that we've pushed
  a gtk point release as an SRU. The other example was 3.22.25 for
  Ubuntu 17.10 (LP: #1728421). We never ended up doing one for Ubuntu
  18.04 LTS since it already included 3.22.30, the final 3.22 release.
  It hasn't been practical to update 18.04's gtk to  the 3.24 series
  (bumped dependencies are one problem).

  https://wiki.ubuntu.com/StableReleaseUpdates#GNOME

  By the way, pre-release gtk3 is actually getting a bit more testing
  than a year ago since more developers and users are using development
  Flatpak releases of popular GNOME apps. (On the other hand, there were
  a few regressions in the 3.24.2 release.)

  This update changes the ON/OFF switches for GNOME's default Adwaita
  theme to use ⏽/⭘. Previously, it was ❙/○ for most languages but ON/OFF
  for English (because English has short words that could fit on a
  switch). This doesn't affect default Ubuntu 18.10 which uses Yaru
  which doesn't use labels on its switches. This is technically a UI
  change, but it is useful for compatibility with Flatpak apps that are
  being built with the new GTK. This change is small enough that it
  could be reverted for Ubuntu 18.10 if necessary.

  Other Info
  ==
  The commit history shows themeing changes to the GNOME default themes 
(Adwaita and Adwaita Dark which are bundled inside gtk3). But those changes 
were reverted for this release to make it easier for distros like us to push 
the update to our stable release.

  The next scheduled gtk3 release (3.24.4 ? in March?) will include
  those changes. See https://blog.gtk.org/2019/01/14/theme-changes-in-
  gtk-3/ for more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1808233/+subscriptions

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


[Touch-packages] [Bug 1808233] Re: Update gtk to 3.24.3

2019-01-15 Thread Jeremy Bicha
** Description changed:

  Impact
  ==
  There is a new release in the stable 3.24 series.
  
  This also bundles the emoji fixes from LP: #1807719 and LP: #1807721 and
  the Xfce flickering fix from LP: #1798861.
  
  https://gitlab.gnome.org/GNOME/gtk/blob/gtk-3-24/NEWS
- https://gitlab.gnome.org/GNOME/gtk/compare/3.24.1...3.24.2
+ https://gitlab.gnome.org/GNOME/gtk/compare/3.24.1...3.24.3
  
  Test Case
  =
  Run several apps in the default Ubuntu install and make sure that there are 
no visible regressions.
  
  We will also be checking Xfce to validate the fix for LP: #1798861.
  
  Regression Potential
  
  There is a standing microrelease exception for GNOME point releases.
  
  I believe this is the second time in recent history that we've pushed a
  gtk point release as an SRU. The other example was 3.22.25 for Ubuntu
  17.10 (LP: #1728421). We never ended up doing one for Ubuntu 18.04 LTS
  since it already included 3.22.30, the final 3.22 release. It hasn't
  been practical to update 18.04's gtk to  the 3.24 series (bumped
  dependencies are one problem).
  
  https://wiki.ubuntu.com/StableReleaseUpdates#GNOME
  
  By the way, pre-release gtk3 is actually getting a bit more testing than
  a year ago since more developers and users are using development Flatpak
- releases of popular GNOME apps.
+ releases of popular GNOME apps. (On the other hand, there were a few
+ regressions in the 3.24.2 release.)
+ 
+ This update changes the ON/OFF switches for GNOME's default Adwaita
+ theme to use ⏽/⭘. Previously, it was ❙/○ for most languages but ON/OFF
+ for English (because English has short words that could fit on a
+ switch). This doesn't affect default Ubuntu 18.10 which uses Yaru which
+ doesn't use labels on its switches. This is technically a UI change, but
+ it is useful for compatibility with Flatpak apps that are being built
+ with the new GTK. This change is small enough that it could be reverted
+ for Ubuntu 18.10 if necessary.
  
  Other Info
  ==
- One of the bigger changes in the git commit history were theming changes to 
the GNOME default themes (Adwaita and Adwaita Dark which are bundled inside 
gtk3. Ubuntu 18.10 uses the Yaru theme as default instead.). But those changes 
were reverted for this release to make it easier for distros like us to push 
the update to our stable release.
+ The commit history shows themeing changes to the GNOME default themes 
(Adwaita and Adwaita Dark which are bundled inside gtk3). But those changes 
were reverted for this release to make it easier for distros like us to push 
the update to our stable release.
+ 
+ The next scheduled gtk3 release (3.24.4 ? in March?) will include those
+ changes. See https://blog.gtk.org/2019/01/14/theme-changes-in-gtk-3/ for
+ more details.

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

Title:
  Update gtk to 3.24.3

Status in gtk+3.0 package in Ubuntu:
  Fix Committed
Status in gtk+3.0 source package in Cosmic:
  Triaged

Bug description:
  Impact
  ==
  There is a new release in the stable 3.24 series.

  This also bundles the emoji fixes from LP: #1807719 and LP: #1807721
  and the Xfce flickering fix from LP: #1798861.

  https://gitlab.gnome.org/GNOME/gtk/blob/gtk-3-24/NEWS
  https://gitlab.gnome.org/GNOME/gtk/compare/3.24.1...3.24.3

  Test Case
  =
  Run several apps in the default Ubuntu install and make sure that there are 
no visible regressions.

  We will also be checking Xfce to validate the fix for LP: #1798861.

  Regression Potential
  
  There is a standing microrelease exception for GNOME point releases.

  I believe this is the second time in recent history that we've pushed
  a gtk point release as an SRU. The other example was 3.22.25 for
  Ubuntu 17.10 (LP: #1728421). We never ended up doing one for Ubuntu
  18.04 LTS since it already included 3.22.30, the final 3.22 release.
  It hasn't been practical to update 18.04's gtk to  the 3.24 series
  (bumped dependencies are one problem).

  https://wiki.ubuntu.com/StableReleaseUpdates#GNOME

  By the way, pre-release gtk3 is actually getting a bit more testing
  than a year ago since more developers and users are using development
  Flatpak releases of popular GNOME apps. (On the other hand, there were
  a few regressions in the 3.24.2 release.)

  This update changes the ON/OFF switches for GNOME's default Adwaita
  theme to use ⏽/⭘. Previously, it was ❙/○ for most languages but ON/OFF
  for English (because English has short words that could fit on a
  switch). This doesn't affect default Ubuntu 18.10 which uses Yaru
  which doesn't use labels on its switches. This is technically a UI
  change, but it is useful for compatibility with Flatpak apps that are
  being built with the new GTK. This change is small enough that it
  could be reverted for 

[Touch-packages] [Bug 1808233] Re: Update gtk to 3.24.3

2019-01-15 Thread Jeremy Bicha
** Summary changed:

- Update gtk to 3.24.2
+ Update gtk to 3.24.3

** Changed in: gtk+3.0 (Ubuntu)
   Status: Fix Released => Fix Committed

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

Title:
  Update gtk to 3.24.3

Status in gtk+3.0 package in Ubuntu:
  Fix Committed
Status in gtk+3.0 source package in Cosmic:
  Triaged

Bug description:
  Impact
  ==
  There is a new release in the stable 3.24 series.

  This also bundles the emoji fixes from LP: #1807719 and LP: #1807721
  and the Xfce flickering fix from LP: #1798861.

  https://gitlab.gnome.org/GNOME/gtk/blob/gtk-3-24/NEWS
  https://gitlab.gnome.org/GNOME/gtk/compare/3.24.1...3.24.2

  Test Case
  =
  Run several apps in the default Ubuntu install and make sure that there are 
no visible regressions.

  We will also be checking Xfce to validate the fix for LP: #1798861.

  Regression Potential
  
  There is a standing microrelease exception for GNOME point releases.

  I believe this is the second time in recent history that we've pushed
  a gtk point release as an SRU. The other example was 3.22.25 for
  Ubuntu 17.10 (LP: #1728421). We never ended up doing one for Ubuntu
  18.04 LTS since it already included 3.22.30, the final 3.22 release.
  It hasn't been practical to update 18.04's gtk to  the 3.24 series
  (bumped dependencies are one problem).

  https://wiki.ubuntu.com/StableReleaseUpdates#GNOME

  By the way, pre-release gtk3 is actually getting a bit more testing
  than a year ago since more developers and users are using development
  Flatpak releases of popular GNOME apps.

  Other Info
  ==
  One of the bigger changes in the git commit history were theming changes to 
the GNOME default themes (Adwaita and Adwaita Dark which are bundled inside 
gtk3. Ubuntu 18.10 uses the Yaru theme as default instead.). But those changes 
were reverted for this release to make it easier for distros like us to push 
the update to our stable release.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1808233/+subscriptions

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


[Touch-packages] [Bug 1805857] Re: network-manager dep8 failure blocks dnsmasq proposed migration

2019-01-07 Thread Jeremy Bicha
** Tags removed: rls-dd-incoming
** Tags added: disco

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

Title:
  network-manager dep8 failure blocks dnsmasq proposed migration

Status in network-manager package in Ubuntu:
  Triaged
Status in network-manager source package in Disco:
  Triaged

Bug description:
  dnsmasq 2.80-1 is blocked from migrating to the release pocket because
  of, amongst other things, a network-manager dep8 regression.

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

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


[Touch-packages] [Bug 1771031] Re: Please remove libgnome from Ubuntu

2019-01-07 Thread Jeremy Bicha
** No longer affects: gnome-translate (Ubuntu)

** Also affects: gnome-vfs (Ubuntu)
   Importance: Undecided
   Status: New

** Description changed:

  libgnome has been removed from Debian Testing and will not be included
  in the Debian 10 "Buster" release. We should do the same. If we do it
  now, maybe some projects will do the needed porting work away from
  libgnome (porting to gtk3 is probably needed) in time for Ubuntu 20.04
  LTS or Debian 10. Users who are hurt by these removals can keep using
  Ubuntu 18.04 LTS for a few years.
  
  This bug depends on these other removals:
  gnome-python LP: #1739800
  DONE: gnome-sharp2 LP: #1771025
  DONE: shutter LP: #1771030
- 
- The libgnome removal in turn blocks these other removals:
- gnome-vfs LP: #1771035
- libgnome-keyring LP: #1771036

** Also affects: libgnome-keyring (Ubuntu)
   Importance: Undecided
   Status: New

** Summary changed:

- Please remove libgnome from Ubuntu
+ Please remove libgnome and friends from Ubuntu

** Description changed:

  libgnome has been removed from Debian Testing and will not be included
  in the Debian 10 "Buster" release. We should do the same. If we do it
  now, maybe some projects will do the needed porting work away from
  libgnome (porting to gtk3 is probably needed) in time for Ubuntu 20.04
  LTS or Debian 10. Users who are hurt by these removals can keep using
  Ubuntu 18.04 LTS for a few years.
  
+ resapplet and winefish are unmaintained and aren't in Debian.
+ 
+ linsmith is in Debian and will be either ported to gtk3 or removed
+ eventually, but I don't think Ubuntu needs to wait for that.
+ 
  This bug depends on these other removals:
  gnome-python LP: #1739800
  DONE: gnome-sharp2 LP: #1771025
  DONE: shutter LP: #1771030

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

Title:
  Please remove libgnome and friends from Ubuntu

Status in gnome-vfs package in Ubuntu:
  New
Status in libbonobo package in Ubuntu:
  New
Status in libbonoboui package in Ubuntu:
  New
Status in libgnome package in Ubuntu:
  New
Status in libgnome-keyring package in Ubuntu:
  New
Status in libgnomeui package in Ubuntu:
  New
Status in linsmith package in Ubuntu:
  New
Status in orbit2 package in Ubuntu:
  New
Status in resapplet package in Ubuntu:
  New
Status in winefish package in Ubuntu:
  New

Bug description:
  libgnome has been removed from Debian Testing and will not be included
  in the Debian 10 "Buster" release. We should do the same. If we do it
  now, maybe some projects will do the needed porting work away from
  libgnome (porting to gtk3 is probably needed) in time for Ubuntu 20.04
  LTS or Debian 10. Users who are hurt by these removals can keep using
  Ubuntu 18.04 LTS for a few years.

  resapplet and winefish are unmaintained and aren't in Debian.

  linsmith is in Debian and will be either ported to gtk3 or removed
  eventually, but I don't think Ubuntu needs to wait for that.

  This bug depends on these other removals:
  gnome-python LP: #1739800
  DONE: gnome-sharp2 LP: #1771025
  DONE: shutter LP: #1771030

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

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


[Touch-packages] [Bug 1771036] Re: Please remove libgnome-keyring from Ubuntu

2019-01-07 Thread Jeremy Bicha
** Changed in: libgnome-keyring (Ubuntu)
   Status: New => Invalid

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

Title:
  Please remove libgnome-keyring from Ubuntu

Status in libgnome-keyring package in Ubuntu:
  Invalid
Status in mysql-workbench package in Ubuntu:
  Invalid

Bug description:
  libgnome-keyring has been removed from Debian Testing and will not be
  included in the Debian 10 "Buster" release. We should do the same.
  Users who are hurt by these removals can keep using Ubuntu 18.04 LTS
  for a few years.

  This bug depends on the libgnome removal LP: #1771031

  ukui-power-manager is a blocker LP: #1767165 (but mate-power-manager
  was done)

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

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


[Touch-packages] [Bug 1767302] Re: User is not added to kvm group when installing gnome-boxes

2019-01-07 Thread Jeremy Bicha
** Changed in: gnome-boxes (Ubuntu Bionic)
   Importance: Undecided => High

** Changed in: gnome-boxes (Ubuntu Bionic)
   Status: Confirmed => Triaged

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

Title:
  User is not added to kvm group when installing gnome-boxes

Status in gnome-boxes package in Ubuntu:
  Invalid
Status in qemu package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in gnome-boxes source package in Bionic:
  Triaged
Status in qemu source package in Bionic:
  Won't Fix
Status in systemd source package in Bionic:
  Invalid
Status in gnome-boxes source package in Cosmic:
  Invalid
Status in qemu source package in Cosmic:
  Invalid
Status in systemd source package in Cosmic:
  Fix Released
Status in gnome-boxes source package in Disco:
  Invalid
Status in qemu source package in Disco:
  Invalid
Status in systemd source package in Disco:
  Fix Released

Bug description:
  Installing gnome-boxes does not add the user to the needed kvm group.
  This leads to the problem that it is impossible to start any system within 
gnome-boxes.

  Gnome-Boxes throwes the error: CPU mode 'custom' for x86_64 kvm domain
  on x86_64 host is not supported by hypervisor

  adduser  kvm solves that problem but how should an average
  user know that. Gnome-Boxes is not usable as of now.

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

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


[Touch-packages] [Bug 1771036] Re: Please remove libgnome-keyring from Ubuntu

2018-12-23 Thread Jeremy Bicha
** Changed in: moonshot-ui (Ubuntu)
   Status: New => Fix Released

** No longer affects: moonshot-ui (Ubuntu)

** Changed in: mysql-workbench (Ubuntu)
   Status: New => Invalid

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

Title:
  Please remove libgnome-keyring from Ubuntu

Status in libgnome-keyring package in Ubuntu:
  New
Status in mysql-workbench package in Ubuntu:
  Invalid

Bug description:
  libgnome-keyring has been removed from Debian Testing and will not be
  included in the Debian 10 "Buster" release. We should do the same.
  Users who are hurt by these removals can keep using Ubuntu 18.04 LTS
  for a few years.

  This bug depends on the libgnome removal LP: #1771031

  ukui-power-manager is a blocker LP: #1767165 (but mate-power-manager
  was done)

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

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


[Touch-packages] [Bug 1808075] Re: Backport Unicode/Emoji 11 updates

2018-12-22 Thread Jeremy Bicha
I installed pango1.0 1.42.4-3ubuntu1 on Ubuntu 18.10 and verified that
the red-haired man now displays correctly in gedit.

I also opened the GNOME Characters app (.deb and snap versions) and
verified that emoji there still displayed ok.

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

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

Title:
  Backport Unicode/Emoji 11 updates

Status in pango1.0 package in Ubuntu:
  Fix Released
Status in pango1.0 source package in Cosmic:
  Fix Committed

Bug description:
  Impact
  ==
  Once a year, there is a new Unicode and Emoji release. 2018's release is 
Unicode 11.

  Ubuntu 18.04 LTS and 18.10 already include Google's color emoji font
  for Unicode 11 (LP: #1788256) but neither Ubuntu 18.10 nor 18.04 LTS
  are able to display the new combinations introduced in Unicode 11 such
  as red-haired people.

  Test Case
  =
  Copy and paste the red-hair man ‍聆 into gedit. It should show as a single 
character.

  Regression Potential
  
  Although the code was written several weeks ago, it was only released in 
pango 1.43 (a development release) today so it's not seen many users yet.

  On the other hand, pango does have a test suite run during the build
  and as autopkgtest and those tests still pass. I haven't seen any
  issues yet and we'll work to fix any issues that do develop.

  A significant portion of the change set comes from the Unicode data
  sets and from the Chromium Unicode/Emoji parser. Both of those parts
  have received wider testing and use over several months.

  Other Info
  ==
  This issue is easy to fix with Ubuntu 18.10 but it may not be practical to 
try to update Ubuntu 18.04 LTS for this feature.

  GTK's "Insert Emoji" feature will need to be updated to offer these
  new emoji.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1808075/+subscriptions

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


[Touch-packages] [Bug 1807719] Re: Some emoji in emoji chooser are black & white

2018-12-18 Thread Jeremy Bicha
** Description changed:

  Impact
  ==
  Some emoji in the emoji chooser show as black & white.
  
  This is because these emoji default to "text presentation" instead of
  "emoji presentation".
  
  More information and a screenshot can be found in the pango issue linked
  below.
  
  Test Case
  =
  In an app like gedit, right click in the text area and select Insert Emoji
  Browse through the emoji list. All should be in full color.
  
  Regression Potential
  
  This fix was included in the gtk 3.24.2 release. There is a standing 
microrelease exception for GNOME point releases.
  
  GTK 3.24 was a big enough release (with some bumped dependencies) that
  it's not very practical to push to Ubuntu 18.04 LTS so we selectively
  cherry-pick fixes there.
  
  https://wiki.ubuntu.com/StableReleaseUpdates#GNOME
  
  https://gitlab.gnome.org/GNOME/pango/issues/334
  https://gitlab.gnome.org/GNOME/gtk/commit/aac38198a3f5
  https://gitlab.gnome.org/GNOME/gtk/commit/b74e3209a5af0
  
  Other Info
  ==
  This adds an extra variation selector byte to each emoji added via the emoji 
chooser. (Many emoji are made up of multiple bytes.) This will not affect emoji 
added to GTK apps in other ways, such as copying and pasting from an app where 
the emoji doesn't have that variation selector added to it.
+ 
+ This bug is fixed in gtk 3.24.2. Its SRU for cosmic is being tracked in
+ LP: #1808233

** Changed in: gtk+3.0 (Ubuntu Cosmic)
   Status: In Progress => Triaged

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

Title:
  Some emoji in emoji chooser are black & white

Status in gtk+3.0 package in Ubuntu:
  Fix Committed
Status in gtk+3.0 source package in Bionic:
  In Progress
Status in gtk+3.0 source package in Cosmic:
  Triaged

Bug description:
  Impact
  ==
  Some emoji in the emoji chooser show as black & white.

  This is because these emoji default to "text presentation" instead of
  "emoji presentation".

  More information and a screenshot can be found in the pango issue
  linked below.

  Test Case
  =
  In an app like gedit, right click in the text area and select Insert Emoji
  Browse through the emoji list. All should be in full color.

  Regression Potential
  
  This fix was included in the gtk 3.24.2 release. There is a standing 
microrelease exception for GNOME point releases.

  GTK 3.24 was a big enough release (with some bumped dependencies) that
  it's not very practical to push to Ubuntu 18.04 LTS so we selectively
  cherry-pick fixes there.

  https://wiki.ubuntu.com/StableReleaseUpdates#GNOME

  https://gitlab.gnome.org/GNOME/pango/issues/334
  https://gitlab.gnome.org/GNOME/gtk/commit/aac38198a3f5
  https://gitlab.gnome.org/GNOME/gtk/commit/b74e3209a5af0

  Other Info
  ==
  This adds an extra variation selector byte to each emoji added via the emoji 
chooser. (Many emoji are made up of multiple bytes.) This will not affect emoji 
added to GTK apps in other ways, such as copying and pasting from an app where 
the emoji doesn't have that variation selector added to it.

  This bug is fixed in gtk 3.24.2. Its SRU for cosmic is being tracked
  in LP: #1808233

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1807719/+subscriptions

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


[Touch-packages] [Bug 1807721] Re: Fix variant selection in emoji chooser

2018-12-18 Thread Jeremy Bicha
Brian, I have now added a note to the bug description to explain that
the cosmic fix is being handled as part of the gtk 3.24.2 SRU. I did
upload this fix for cosmic but I got Steve to reject it for me since we
are doing to do the 3.24.2 SRU instead. I still haven't uploaded 3.24.2
to cosmic since I expect a 3.24.3 release "soon".

If you want to accept the bionic fix, I'll wait to verify the fix until
after this issue is also fixed is in cosmic-proopsed. Or we can just
wait a bit longer for bionic too.

** Description changed:

  Impact
  ==
  The variant selector in the emoji chooser was broken and will crash the app 
if used.
  
  Test Case
  =
  In an app like gedit, right click in the text area and select Insert Emoji
  Look for one of the "people" emoji.
  Right-click (or long-click) on the emoji and select one of the skin tones 
instead of the default yellow.
  The emoji with the skin tone you selected should be added to the text area.
  
  Regression Potential
  
  This fix was included in the gtk 3.24.2 release. There is a standing 
microrelease exception for GNOME point releases.
  
  GTK 3.24 was a big enough release (with some bumped dependencies) that
  it's not very practical to push to Ubuntu 18.04 LTS so we selectively
  cherry-pick fixes there.
  
  https://wiki.ubuntu.com/StableReleaseUpdates#GNOME
  
  https://gitlab.gnome.org/GNOME/gtk/commit/dbbc7b3859f4b
  https://gitlab.gnome.org/GNOME/gtk/issues/1398
+ 
+ Other Info
+ ==
+ This bug is fixed in gtk 3.24.2. Its SRU for cosmic is being tracked in LP: 
#1808233

** Changed in: gtk+3.0 (Ubuntu Cosmic)
   Status: In Progress => Triaged

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

Title:
  Fix variant selection in emoji chooser

Status in gtk+3.0 package in Ubuntu:
  Fix Committed
Status in gtk+3.0 source package in Bionic:
  In Progress
Status in gtk+3.0 source package in Cosmic:
  Triaged

Bug description:
  Impact
  ==
  The variant selector in the emoji chooser was broken and will crash the app 
if used.

  Test Case
  =
  In an app like gedit, right click in the text area and select Insert Emoji
  Look for one of the "people" emoji.
  Right-click (or long-click) on the emoji and select one of the skin tones 
instead of the default yellow.
  The emoji with the skin tone you selected should be added to the text area.

  Regression Potential
  
  This fix was included in the gtk 3.24.2 release. There is a standing 
microrelease exception for GNOME point releases.

  GTK 3.24 was a big enough release (with some bumped dependencies) that
  it's not very practical to push to Ubuntu 18.04 LTS so we selectively
  cherry-pick fixes there.

  https://wiki.ubuntu.com/StableReleaseUpdates#GNOME

  https://gitlab.gnome.org/GNOME/gtk/commit/dbbc7b3859f4b
  https://gitlab.gnome.org/GNOME/gtk/issues/1398

  Other Info
  ==
  This bug is fixed in gtk 3.24.2. Its SRU for cosmic is being tracked in LP: 
#1808233

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1807721/+subscriptions

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


[Touch-packages] [Bug 1808233] Re: Update gtk to 3.24.2

2018-12-15 Thread Jeremy Bicha
** Also affects: gtk+3.0 (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Changed in: gtk+3.0 (Ubuntu Cosmic)
 Assignee: (unassigned) => Jeremy Bicha (jbicha)

** Changed in: gtk+3.0 (Ubuntu Cosmic)
   Importance: Undecided => Medium

** Changed in: gtk+3.0 (Ubuntu Cosmic)
   Status: New => Triaged

** Changed in: gtk+3.0 (Ubuntu)
   Status: Triaged => Fix Committed

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

Title:
  Update gtk to 3.24.2

Status in gtk+3.0 package in Ubuntu:
  Fix Committed
Status in gtk+3.0 source package in Cosmic:
  Triaged

Bug description:
  Impact
  ==
  There is a new release in the stable 3.24 series.

  This also bundles the emoji fixes from LP: #1807719 and LP: #1807721
  and the Xfce flickering fix from LP: #1798861.

  https://gitlab.gnome.org/GNOME/gtk/blob/gtk-3-24/NEWS
  https://gitlab.gnome.org/GNOME/gtk/compare/3.24.1...3.24.2

  Test Case
  =
  Run several apps in the default Ubuntu install and make sure that there are 
no visible regressions.

  We will also be checking Xfce to validate the fix for LP: #1798861.

  Regression Potential
  
  There is a standing microrelease exception for GNOME point releases.

  I believe this is the second time in recent history that we've pushed
  a gtk point release as an SRU. The other example was 3.22.25 for
  Ubuntu 17.10 (LP: #1728421). We never ended up doing one for Ubuntu
  18.04 LTS since it already included 3.22.30, the final 3.22 release.
  It hasn't been practical to update 18.04's gtk to  the 3.24 series
  (bumped dependencies are one problem).

  https://wiki.ubuntu.com/StableReleaseUpdates#GNOME

  By the way, pre-release gtk3 is actually getting a bit more testing
  than a year ago since more developers and users are using development
  Flatpak releases of popular GNOME apps.

  Other Info
  ==
  One of the bigger changes in the git commit history were theming changes to 
the GNOME default themes (Adwaita and Adwaita Dark which are bundled inside 
gtk3. Ubuntu 18.10 uses the Yaru theme as default instead.). But those changes 
were reverted for this release to make it easier for distros like us to push 
the update to our stable release.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1808233/+subscriptions

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


[Touch-packages] [Bug 1808075] Re: Backport Unicode/Emoji 11 updates

2018-12-15 Thread Jeremy Bicha
** Changed in: pango1.0 (Ubuntu Cosmic)
   Status: Triaged => In Progress

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

Title:
  Backport Unicode/Emoji 11 updates

Status in pango1.0 package in Ubuntu:
  Fix Released
Status in pango1.0 source package in Cosmic:
  In Progress

Bug description:
  Impact
  ==
  Once a year, there is a new Unicode and Emoji release. 2018's release is 
Unicode 11.

  Ubuntu 18.04 LTS and 18.10 already include Google's color emoji font
  for Unicode 11 (LP: #1788256) but neither Ubuntu 18.10 nor 18.04 LTS
  are able to display the new combinations introduced in Unicode 11 such
  as red-haired people.

  Test Case
  =
  Copy and paste the red-hair man ‍聆 into gedit. It should show as a single 
character.

  Regression Potential
  
  Although the code was written several weeks ago, it was only released in 
pango 1.43 (a development release) today so it's not seen many users yet.

  On the other hand, pango does have a test suite run during the build
  and as autopkgtest and those tests still pass. I haven't seen any
  issues yet and we'll work to fix any issues that do develop.

  A significant portion of the change set comes from the Unicode data
  sets and from the Chromium Unicode/Emoji parser. Both of those parts
  have received wider testing and use over several months.

  Other Info
  ==
  This issue is easy to fix with Ubuntu 18.10 but it may not be practical to 
try to update Ubuntu 18.04 LTS for this feature.

  GTK's "Insert Emoji" feature will need to be updated to offer these
  new emoji.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1808075/+subscriptions

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


[Touch-packages] [Bug 1808233] Re: Update gtk to 3.24.2

2018-12-15 Thread Jeremy Bicha
There will be a 3.24.3 release "soon" so I think it's best to wait for
that before pushing to Ubuntu 18.10.

** Tags added: upgrade-software-version

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

Title:
  Update gtk to 3.24.2

Status in gtk+3.0 package in Ubuntu:
  Triaged

Bug description:
  Impact
  ==
  There is a new release in the stable 3.24 series.

  This also bundles the emoji fixes from LP: #1807719 and LP: #1807721
  and the Xfce flickering fix from LP: #1798861.

  https://gitlab.gnome.org/GNOME/gtk/blob/gtk-3-24/NEWS
  https://gitlab.gnome.org/GNOME/gtk/compare/3.24.1...3.24.2

  Test Case
  =
  Run several apps in the default Ubuntu install and make sure that there are 
no visible regressions.

  We will also be checking Xfce to validate the fix for LP: #1798861.

  Regression Potential
  
  There is a standing microrelease exception for GNOME point releases.

  I believe this is the second time in recent history that we've pushed
  a gtk point release as an SRU. The other example was 3.22.25 for
  Ubuntu 17.10 (LP: #1728421). We never ended up doing one for Ubuntu
  18.04 LTS since it already included 3.22.30, the final 3.22 release.
  It hasn't been practical to update 18.04's gtk to  the 3.24 series
  (bumped dependencies are one problem).

  https://wiki.ubuntu.com/StableReleaseUpdates#GNOME

  By the way, pre-release gtk3 is actually getting a bit more testing
  than a year ago since more developers and users are using development
  Flatpak releases of popular GNOME apps.

  Other Info
  ==
  One of the bigger changes in the git commit history were theming changes to 
the GNOME default themes (Adwaita and Adwaita Dark which are bundled inside 
gtk3. Ubuntu 18.10 uses the Yaru theme as default instead.). But those changes 
were reverted for this release to make it easier for distros like us to push 
the update to our stable release.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1808233/+subscriptions

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


[Touch-packages] [Bug 1439222] Re: Implement emoji in Ubuntu

2018-12-15 Thread Jeremy Bicha
Ubuntu 18.04 LTS includes color emoji support (with Google's Noto Color
Emoji font). Most GTK apps are supported.

The GNOME Characters app allow you to browse emoji and is installed by
default.

You can right-click in many text areas and choose Insert Emoji to get an
embedded emoji browser when you want it.

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

Title:
  Implement emoji in Ubuntu

Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-touch-meta package in Ubuntu:
  Invalid

Bug description:
  This bug is about implementing emoji display and insertion in Ubuntu,
  desktop and phone.

  I wrote a page about possible ways to implement emoji in Gnu/Linux systems:
  http://probablement.net/txt/emojilinux

  To sum it up:

  * The first thing to do is having the Symbola font (in ttf-ancient-
  fonts) as part of the default installation, so users can see
  monochrome emoji. If I understand, it’s what is being done in bug
  #1137630 (which is about not seeing emoji: Symbola certainly resolve
  it but isn’t a full implementation of emoji as we expect them).

  * The second thing is replacing Symbola with a proper colour emoji
  set, like Emoji One, Noto Color Emoji, or Twemoji. There’s different
  ways to implement this (layered colour font, SVG font, substitution
  with individual SVG files, …) but if I understand correctly comment #6
  in #1137630 FreeType is already compatible with colour fonts! (I will
  update my page)

  * An optional third step would be designing a custom Emoji set. That’s
  more or less bug #820034 even if I’m unsure about it being part of the
  Ubuntu Font Family, even if drawn in stylistically consistent way with
  it.

  * Lastly, we need a system wide UI to browse, pick and insert emoji. I
  added some existing examples on the page; basically, the choice is
  making it only for emoji or part of larger UI for inserting
  characters.

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

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


[Touch-packages] [Bug 1439222] Re: Implement emoji in Ubuntu

2018-12-15 Thread Jeremy Bicha
** Changed in: ubuntu-meta (Ubuntu)
   Status: Triaged => Fix Released

** Changed in: ubuntu-touch-meta (Ubuntu)
   Status: Triaged => Invalid

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

Title:
  Implement emoji in Ubuntu

Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-touch-meta package in Ubuntu:
  Invalid

Bug description:
  This bug is about implementing emoji display and insertion in Ubuntu,
  desktop and phone.

  I wrote a page about possible ways to implement emoji in Gnu/Linux systems:
  http://probablement.net/txt/emojilinux

  To sum it up:

  * The first thing to do is having the Symbola font (in ttf-ancient-
  fonts) as part of the default installation, so users can see
  monochrome emoji. If I understand, it’s what is being done in bug
  #1137630 (which is about not seeing emoji: Symbola certainly resolve
  it but isn’t a full implementation of emoji as we expect them).

  * The second thing is replacing Symbola with a proper colour emoji
  set, like Emoji One, Noto Color Emoji, or Twemoji. There’s different
  ways to implement this (layered colour font, SVG font, substitution
  with individual SVG files, …) but if I understand correctly comment #6
  in #1137630 FreeType is already compatible with colour fonts! (I will
  update my page)

  * An optional third step would be designing a custom Emoji set. That’s
  more or less bug #820034 even if I’m unsure about it being part of the
  Ubuntu Font Family, even if drawn in stylistically consistent way with
  it.

  * Lastly, we need a system wide UI to browse, pick and insert emoji. I
  added some existing examples on the page; basically, the choice is
  making it only for emoji or part of larger UI for inserting
  characters.

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

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


[Touch-packages] [Bug 1808233] [NEW] Update gtk to 3.24.2

2018-12-12 Thread Jeremy Bicha
Public bug reported:

Impact
==
There is a new release in the stable 3.24 series.

This also bundles the emoji fixes from LP: #1807719 and LP: #1807721 and
the Xfce flickering fix from LP: #1798861.

https://gitlab.gnome.org/GNOME/gtk/blob/gtk-3-24/NEWS
https://gitlab.gnome.org/GNOME/gtk/compare/3.24.1...3.24.2

Test Case
=
Run several apps in the default Ubuntu install and make sure that there are no 
visible regressions.

We will also be checking Xfce to validate the fix for LP: #1798861.

Regression Potential

There is a standing microrelease exception for GNOME point releases.

I believe this is the second time in recent history that we've pushed a
gtk point release as an SRU. The other example was 3.22.25 for Ubuntu
17.10 (LP: #1728421). We never ended up doing one for Ubuntu 18.04 LTS
since it already included 3.22.30, the final 3.22 release. It hasn't
been practical to update 18.04's gtk to  the 3.24 series (bumped
dependencies are one problem).

https://wiki.ubuntu.com/StableReleaseUpdates#GNOME

By the way, pre-release gtk3 is actually getting a bit more testing than
a year ago since more developers and users are using development Flatpak
releases of popular GNOME apps.

Other Info
==
One of the bigger changes in the git commit history were theming changes to the 
GNOME default themes (Adwaita and Adwaita Dark which are bundled inside gtk3. 
Ubuntu 18.10 uses the Yaru theme as default instead.). But those changes were 
reverted for this release to make it easier for distros like us to push the 
update to our stable release.

** Affects: gtk+3.0 (Ubuntu)
 Importance: Medium
 Status: Triaged


** Tags: cosmic

** Changed in: gtk+3.0 (Ubuntu)
   Status: Fix Committed => Triaged

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

Title:
  Update gtk to 3.24.2

Status in gtk+3.0 package in Ubuntu:
  Triaged

Bug description:
  Impact
  ==
  There is a new release in the stable 3.24 series.

  This also bundles the emoji fixes from LP: #1807719 and LP: #1807721
  and the Xfce flickering fix from LP: #1798861.

  https://gitlab.gnome.org/GNOME/gtk/blob/gtk-3-24/NEWS
  https://gitlab.gnome.org/GNOME/gtk/compare/3.24.1...3.24.2

  Test Case
  =
  Run several apps in the default Ubuntu install and make sure that there are 
no visible regressions.

  We will also be checking Xfce to validate the fix for LP: #1798861.

  Regression Potential
  
  There is a standing microrelease exception for GNOME point releases.

  I believe this is the second time in recent history that we've pushed
  a gtk point release as an SRU. The other example was 3.22.25 for
  Ubuntu 17.10 (LP: #1728421). We never ended up doing one for Ubuntu
  18.04 LTS since it already included 3.22.30, the final 3.22 release.
  It hasn't been practical to update 18.04's gtk to  the 3.24 series
  (bumped dependencies are one problem).

  https://wiki.ubuntu.com/StableReleaseUpdates#GNOME

  By the way, pre-release gtk3 is actually getting a bit more testing
  than a year ago since more developers and users are using development
  Flatpak releases of popular GNOME apps.

  Other Info
  ==
  One of the bigger changes in the git commit history were theming changes to 
the GNOME default themes (Adwaita and Adwaita Dark which are bundled inside 
gtk3. Ubuntu 18.10 uses the Yaru theme as default instead.). But those changes 
were reverted for this release to make it easier for distros like us to push 
the update to our stable release.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1808233/+subscriptions

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


[Touch-packages] [Bug 1807719] Re: Some emoji in emoji chooser are black & white

2018-12-12 Thread Jeremy Bicha
** Description changed:

  Impact
  ==
  Some emoji in the emoji chooser show as black & white.
  
  This is because these emoji default to "text presentation" instead of
  "emoji presentation".
  
  More information and a screenshot can be found in the pango issue linked
  below.
  
  Test Case
  =
  In an app like gedit, right click in the text area and select Insert Emoji
  Browse through the emoji list. All should be in full color.
  
  Regression Potential
  
- The fix for this was pushed to the stable gtk-3-24 branch.
+ This fix was included in the gtk 3.24.2 release. There is a standing 
microrelease exception for GNOME point releases.
+ 
+ GTK 3.24 was a big enough release (with some bumped dependencies) that
+ it's not very practical to push to Ubuntu 18.04 LTS so we selectively
+ cherry-pick fixes there.
+ 
+ https://wiki.ubuntu.com/StableReleaseUpdates#GNOME
  
  https://gitlab.gnome.org/GNOME/pango/issues/334
  https://gitlab.gnome.org/GNOME/gtk/commit/aac38198a3f5
  https://gitlab.gnome.org/GNOME/gtk/commit/b74e3209a5af0
  
  Other Info
  ==
  This adds an extra variation selector byte to each emoji added via the emoji 
chooser. (Many emoji are made up of multiple bytes.) This will not affect emoji 
added to GTK apps in other ways, such as copying and pasting from an app where 
the emoji doesn't have that variation selector added to it.

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

Title:
  Some emoji in emoji chooser are black & white

Status in gtk+3.0 package in Ubuntu:
  Fix Committed
Status in gtk+3.0 source package in Bionic:
  In Progress
Status in gtk+3.0 source package in Cosmic:
  In Progress

Bug description:
  Impact
  ==
  Some emoji in the emoji chooser show as black & white.

  This is because these emoji default to "text presentation" instead of
  "emoji presentation".

  More information and a screenshot can be found in the pango issue
  linked below.

  Test Case
  =
  In an app like gedit, right click in the text area and select Insert Emoji
  Browse through the emoji list. All should be in full color.

  Regression Potential
  
  This fix was included in the gtk 3.24.2 release. There is a standing 
microrelease exception for GNOME point releases.

  GTK 3.24 was a big enough release (with some bumped dependencies) that
  it's not very practical to push to Ubuntu 18.04 LTS so we selectively
  cherry-pick fixes there.

  https://wiki.ubuntu.com/StableReleaseUpdates#GNOME

  https://gitlab.gnome.org/GNOME/pango/issues/334
  https://gitlab.gnome.org/GNOME/gtk/commit/aac38198a3f5
  https://gitlab.gnome.org/GNOME/gtk/commit/b74e3209a5af0

  Other Info
  ==
  This adds an extra variation selector byte to each emoji added via the emoji 
chooser. (Many emoji are made up of multiple bytes.) This will not affect emoji 
added to GTK apps in other ways, such as copying and pasting from an app where 
the emoji doesn't have that variation selector added to it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1807719/+subscriptions

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


[Touch-packages] [Bug 1807721] Re: Fix variant selection in emoji chooser

2018-12-12 Thread Jeremy Bicha
** Description changed:

  Impact
  ==
  The variant selector in the emoji chooser was broken and will crash the app 
if used.
  
  Test Case
  =
  In an app like gedit, right click in the text area and select Insert Emoji
  Look for one of the "people" emoji.
  Right-click (or long-click) on the emoji and select one of the skin tones 
instead of the default yellow.
  The emoji with the skin tone you selected should be added to the text area.
  
  Regression Potential
  
- The fix for this was pushed to the stable gtk-3-24 branch.
+ This fix was included in the gtk 3.24.2 release. There is a standing 
microrelease exception for GNOME point releases.
+ 
+ GTK 3.24 was a big enough release (with some bumped dependencies) that
+ it's not very practical to push to Ubuntu 18.04 LTS so we selectively
+ cherry-pick fixes there.
  
  https://gitlab.gnome.org/GNOME/gtk/commit/dbbc7b3859f4b
  https://gitlab.gnome.org/GNOME/gtk/issues/1398

** Description changed:

  Impact
  ==
  The variant selector in the emoji chooser was broken and will crash the app 
if used.
  
  Test Case
  =
  In an app like gedit, right click in the text area and select Insert Emoji
  Look for one of the "people" emoji.
  Right-click (or long-click) on the emoji and select one of the skin tones 
instead of the default yellow.
  The emoji with the skin tone you selected should be added to the text area.
  
  Regression Potential
  
  This fix was included in the gtk 3.24.2 release. There is a standing 
microrelease exception for GNOME point releases.
  
  GTK 3.24 was a big enough release (with some bumped dependencies) that
  it's not very practical to push to Ubuntu 18.04 LTS so we selectively
- cherry-pick fixes there.
+ cherry-pick fixes
+ there.https://wiki.ubuntu.com/StableReleaseUpdates#GNOME
  
  https://gitlab.gnome.org/GNOME/gtk/commit/dbbc7b3859f4b
  https://gitlab.gnome.org/GNOME/gtk/issues/1398

** Description changed:

  Impact
  ==
  The variant selector in the emoji chooser was broken and will crash the app 
if used.
  
  Test Case
  =
  In an app like gedit, right click in the text area and select Insert Emoji
  Look for one of the "people" emoji.
  Right-click (or long-click) on the emoji and select one of the skin tones 
instead of the default yellow.
  The emoji with the skin tone you selected should be added to the text area.
  
  Regression Potential
  
  This fix was included in the gtk 3.24.2 release. There is a standing 
microrelease exception for GNOME point releases.
  
  GTK 3.24 was a big enough release (with some bumped dependencies) that
  it's not very practical to push to Ubuntu 18.04 LTS so we selectively
- cherry-pick fixes
- there.https://wiki.ubuntu.com/StableReleaseUpdates#GNOME
+ cherry-pick fixes there.
+ 
+ https://wiki.ubuntu.com/StableReleaseUpdates#GNOME
  
  https://gitlab.gnome.org/GNOME/gtk/commit/dbbc7b3859f4b
  https://gitlab.gnome.org/GNOME/gtk/issues/1398

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

Title:
  Fix variant selection in emoji chooser

Status in gtk+3.0 package in Ubuntu:
  Fix Committed
Status in gtk+3.0 source package in Bionic:
  In Progress
Status in gtk+3.0 source package in Cosmic:
  In Progress

Bug description:
  Impact
  ==
  The variant selector in the emoji chooser was broken and will crash the app 
if used.

  Test Case
  =
  In an app like gedit, right click in the text area and select Insert Emoji
  Look for one of the "people" emoji.
  Right-click (or long-click) on the emoji and select one of the skin tones 
instead of the default yellow.
  The emoji with the skin tone you selected should be added to the text area.

  Regression Potential
  
  This fix was included in the gtk 3.24.2 release. There is a standing 
microrelease exception for GNOME point releases.

  GTK 3.24 was a big enough release (with some bumped dependencies) that
  it's not very practical to push to Ubuntu 18.04 LTS so we selectively
  cherry-pick fixes there.

  https://wiki.ubuntu.com/StableReleaseUpdates#GNOME

  https://gitlab.gnome.org/GNOME/gtk/commit/dbbc7b3859f4b
  https://gitlab.gnome.org/GNOME/gtk/issues/1398

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1807721/+subscriptions

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


[Touch-packages] [Bug 1798861] Re: Tooltips flicker constantly in GTK3 applications

2018-12-12 Thread Jeremy Bicha
I discussed this issue briefly on #xubuntu-devel today. This issue does
not affect the default Xubuntu session which has set a cursor size for a
long time. It only affects Ubuntu 18.10 users using the plain Xfce
session. (In fact, I had to create a new user to see this bug for myself
in an Xubuntu 18.10 live ISO. Simply choosing "Xfce" after already
logging in with "Xubuntu" was not sufficient.)

This bug will be fixed for Ubuntu 19.04 and never affected Ubuntu 18.04
LTS.

** Changed in: gtk+3.0 (Ubuntu)
   Status: Confirmed => Fix Committed

** Tags added: rls-cc-notfixing

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

Title:
  Tooltips flicker constantly in GTK3 applications

Status in gtk+3.0 package in Ubuntu:
  Fix Committed
Status in gtk+3.0 package in Debian:
  Unknown

Bug description:
  Tooltips are flicker constantly (i.e. repeatedly shown and the hidden
  again) in GTK3 applications under XFCE.

  It is a regression in the recent GTK 3.24.

  This is the upstream report and fix:
  https://gitlab.gnome.org/GNOME/gtk/issues/1371
  
https://gitlab.gnome.org/GNOME/gtk/commit/9b7d886b723132eade2e76f3fd179cf81b7601f2

  A workaround for XFCE is as follows:

  Open Settings Editor.
  Set xsettings -> Gtk -> CursorThemeSize to 16.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libgtk-3-0 3.24.1-1ubuntu2
  Uname: Linux 4.19.0-041900rc8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  Date: Fri Oct 19 12:23:53 2018
  InstallationDate: Installed on 2017-02-01 (624 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gtk+3.0
  UpgradeStatus: Upgraded to cosmic on 2018-10-18 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1798861/+subscriptions

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


[Touch-packages] [Bug 1798861] Re: Tooltips flicker constantly in GTK3 applications

2018-12-12 Thread Jeremy Bicha
** Also affects: gtk+3.0 (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911148
   Importance: Unknown
   Status: Unknown

** Project changed: hash-it => acorn (Ubuntu)

** No longer affects: acorn (Ubuntu)

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

Title:
  Tooltips flicker constantly in GTK3 applications

Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Debian:
  Unknown

Bug description:
  Tooltips are flicker constantly (i.e. repeatedly shown and the hidden
  again) in GTK3 applications under XFCE.

  It is a regression in the recent GTK 3.24.

  This is the upstream report and fix:
  https://gitlab.gnome.org/GNOME/gtk/issues/1371
  
https://gitlab.gnome.org/GNOME/gtk/commit/9b7d886b723132eade2e76f3fd179cf81b7601f2

  A workaround for XFCE is as follows:

  Open Settings Editor.
  Set xsettings -> Gtk -> CursorThemeSize to 16.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libgtk-3-0 3.24.1-1ubuntu2
  Uname: Linux 4.19.0-041900rc8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  Date: Fri Oct 19 12:23:53 2018
  InstallationDate: Installed on 2017-02-01 (624 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gtk+3.0
  UpgradeStatus: Upgraded to cosmic on 2018-10-18 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1798861/+subscriptions

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


[Touch-packages] [Bug 1808075] Re: Backport Unicode/Emoji 11 updates

2018-12-11 Thread Jeremy Bicha
** Description changed:

  Impact
  ==
  Once a year, there is a new Unicode and Emoji release. 2018's release is 
Unicode 11.
  
  Ubuntu 18.04 LTS and 18.10 already include Google's color emoji font for
  Unicode 11 (LP: #1788256) but neither Ubuntu 18.10 nor 18.04 LTS are
  able to display the new combinations introduced in Unicode 11 such as
  red-haired people.
  
  Test Case
  =
  Copy and paste the red-hair man ‍聆 into gedit. It should show as a single 
character.
  
  Regression Potential
  
  Although the code was written several weeks ago, it was only released in 
pango 1.43 (a development release) today so it's not seen many users yet.
  
  On the other hand, pango does have a test suite run during the build and
  as autopkgtest and those tests still pass. I haven't seen any issues yet
  and we'll work to fix any issues that do develop.
  
  A significant portion of the change set comes from the Unicode data sets
  and from the Chromium Unicode/Emoji parser. Both of those parts have
  received wider testing and use over several months.
  
  Other Info
  ==
- GTK's "Insert Emoji" feature will need to be updated to offer these new emoji.
+ This issue is easy to fix with Ubuntu 18.10 but it may not be practical to 
try to update Ubuntu 18.04 LTS for this feature.
+ 
+ GTK's "Insert Emoji" feature will need to be updated to offer these new
+ emoji.

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

Title:
  Backport Unicode/Emoji 11 updates

Status in pango1.0 package in Ubuntu:
  Fix Committed
Status in pango1.0 source package in Cosmic:
  Triaged

Bug description:
  Impact
  ==
  Once a year, there is a new Unicode and Emoji release. 2018's release is 
Unicode 11.

  Ubuntu 18.04 LTS and 18.10 already include Google's color emoji font
  for Unicode 11 (LP: #1788256) but neither Ubuntu 18.10 nor 18.04 LTS
  are able to display the new combinations introduced in Unicode 11 such
  as red-haired people.

  Test Case
  =
  Copy and paste the red-hair man ‍聆 into gedit. It should show as a single 
character.

  Regression Potential
  
  Although the code was written several weeks ago, it was only released in 
pango 1.43 (a development release) today so it's not seen many users yet.

  On the other hand, pango does have a test suite run during the build
  and as autopkgtest and those tests still pass. I haven't seen any
  issues yet and we'll work to fix any issues that do develop.

  A significant portion of the change set comes from the Unicode data
  sets and from the Chromium Unicode/Emoji parser. Both of those parts
  have received wider testing and use over several months.

  Other Info
  ==
  This issue is easy to fix with Ubuntu 18.10 but it may not be practical to 
try to update Ubuntu 18.04 LTS for this feature.

  GTK's "Insert Emoji" feature will need to be updated to offer these
  new emoji.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1808075/+subscriptions

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


[Touch-packages] [Bug 1808075] [NEW] Backport Unicode/Emoji 11 updates

2018-12-11 Thread Jeremy Bicha
Public bug reported:

Impact
==
Once a year, there is a new Unicode and Emoji release. 2018's release is 
Unicode 11.

Ubuntu 18.04 LTS and 18.10 already include Google's color emoji font for
Unicode 11 (LP: #1788256) but neither Ubuntu 18.10 nor 18.04 LTS are
able to display the new combinations introduced in Unicode 11 such as
red-haired people.

Test Case
=
Copy and paste the red-hair man ‍聆 into gedit. It should show as a single 
character.

Regression Potential

Although the code was written several weeks ago, it was only released in pango 
1.43 (a development release) today so it's not seen many users yet.

On the other hand, pango does have a test suite run during the build and
as autopkgtest and those tests still pass. I haven't seen any issues yet
and we'll work to fix any issues that do develop.

A significant portion of the change set comes from the Unicode data sets
and from the Chromium Unicode/Emoji parser. Both of those parts have
received wider testing and use over several months.

Other Info
==
GTK's "Insert Emoji" feature will need to be updated to offer these new emoji.

** Affects: pango1.0 (Ubuntu)
 Importance: Low
 Status: Fix Committed

** Affects: pango1.0 (Ubuntu Cosmic)
 Importance: Low
 Assignee: Jeremy Bicha (jbicha)
 Status: Triaged


** Tags: bionic cosmic

** Also affects: pango1.0 (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Changed in: pango1.0 (Ubuntu Cosmic)
 Assignee: (unassigned) => Jeremy Bicha (jbicha)

** Changed in: pango1.0 (Ubuntu Cosmic)
   Importance: Undecided => Low

** Changed in: pango1.0 (Ubuntu Cosmic)
   Status: New => Triaged

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

Title:
  Backport Unicode/Emoji 11 updates

Status in pango1.0 package in Ubuntu:
  Fix Committed
Status in pango1.0 source package in Cosmic:
  Triaged

Bug description:
  Impact
  ==
  Once a year, there is a new Unicode and Emoji release. 2018's release is 
Unicode 11.

  Ubuntu 18.04 LTS and 18.10 already include Google's color emoji font
  for Unicode 11 (LP: #1788256) but neither Ubuntu 18.10 nor 18.04 LTS
  are able to display the new combinations introduced in Unicode 11 such
  as red-haired people.

  Test Case
  =
  Copy and paste the red-hair man ‍聆 into gedit. It should show as a single 
character.

  Regression Potential
  
  Although the code was written several weeks ago, it was only released in 
pango 1.43 (a development release) today so it's not seen many users yet.

  On the other hand, pango does have a test suite run during the build
  and as autopkgtest and those tests still pass. I haven't seen any
  issues yet and we'll work to fix any issues that do develop.

  A significant portion of the change set comes from the Unicode data
  sets and from the Chromium Unicode/Emoji parser. Both of those parts
  have received wider testing and use over several months.

  Other Info
  ==
  GTK's "Insert Emoji" feature will need to be updated to offer these new emoji.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1808075/+subscriptions

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


[Touch-packages] [Bug 1807719] Re: Some emoji in emoji chooser are black & white

2018-12-11 Thread Jeremy Bicha
** Changed in: gtk+3.0 (Ubuntu)
 Assignee: (unassigned) => Jeremy Bicha (jbicha)

** Changed in: gtk+3.0 (Ubuntu Bionic)
 Assignee: (unassigned) => Jeremy Bicha (jbicha)

** Changed in: gtk+3.0 (Ubuntu Cosmic)
 Assignee: (unassigned) => Jeremy Bicha (jbicha)

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

Title:
  Some emoji in emoji chooser are black & white

Status in gtk+3.0 package in Ubuntu:
  Fix Committed
Status in gtk+3.0 source package in Bionic:
  In Progress
Status in gtk+3.0 source package in Cosmic:
  In Progress

Bug description:
  Impact
  ==
  Some emoji in the emoji chooser show as black & white.

  This is because these emoji default to "text presentation" instead of
  "emoji presentation".

  More information and a screenshot can be found in the pango issue
  linked below.

  Test Case
  =
  In an app like gedit, right click in the text area and select Insert Emoji
  Browse through the emoji list. All should be in full color.

  Regression Potential
  
  The fix for this was pushed to the stable gtk-3-24 branch.

  https://gitlab.gnome.org/GNOME/pango/issues/334
  https://gitlab.gnome.org/GNOME/gtk/commit/aac38198a3f5
  https://gitlab.gnome.org/GNOME/gtk/commit/b74e3209a5af0

  Other Info
  ==
  This adds an extra variation selector byte to each emoji added via the emoji 
chooser. (Many emoji are made up of multiple bytes.) This will not affect emoji 
added to GTK apps in other ways, such as copying and pasting from an app where 
the emoji doesn't have that variation selector added to it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1807719/+subscriptions

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


[Touch-packages] [Bug 1807721] Re: Fix variant selection in emoji chooser

2018-12-10 Thread Jeremy Bicha
** Also affects: gtk+3.0 (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Also affects: gtk+3.0 (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: gtk+3.0 (Ubuntu Bionic)
   Importance: Undecided => Medium

** Changed in: gtk+3.0 (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: gtk+3.0 (Ubuntu Bionic)
 Assignee: (unassigned) => Jeremy Bicha (jbicha)

** Changed in: gtk+3.0 (Ubuntu Cosmic)
 Assignee: (unassigned) => Jeremy Bicha (jbicha)

** Changed in: gtk+3.0 (Ubuntu Cosmic)
   Importance: Undecided => Medium

** Changed in: gtk+3.0 (Ubuntu Cosmic)
   Status: New => In Progress

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

Title:
  Fix variant selection in emoji chooser

Status in gtk+3.0 package in Ubuntu:
  Fix Committed
Status in gtk+3.0 source package in Bionic:
  In Progress
Status in gtk+3.0 source package in Cosmic:
  In Progress

Bug description:
  Impact
  ==
  The variant selector in the emoji chooser was broken and will crash the app 
if used.

  Test Case
  =
  In an app like gedit, right click in the text area and select Insert Emoji
  Look for one of the "people" emoji.
  Right-click (or long-click) on the emoji and select one of the skin tones 
instead of the default yellow.
  The emoji with the skin tone you selected should be added to the text area.

  Regression Potential
  
  The fix for this was pushed to the stable gtk-3-24 branch.

  https://gitlab.gnome.org/GNOME/gtk/commit/dbbc7b3859f4b
  https://gitlab.gnome.org/GNOME/gtk/issues/1398

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1807721/+subscriptions

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


[Touch-packages] [Bug 1807719] Re: Some emoji in emoji chooser are black & white

2018-12-10 Thread Jeremy Bicha
** Also affects: gtk+3.0 (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Also affects: gtk+3.0 (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: gtk+3.0 (Ubuntu Bionic)
   Importance: Undecided => Low

** Changed in: gtk+3.0 (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: gtk+3.0 (Ubuntu Cosmic)
   Status: New => In Progress

** Changed in: gtk+3.0 (Ubuntu Cosmic)
   Importance: Undecided => Low

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

Title:
  Some emoji in emoji chooser are black & white

Status in gtk+3.0 package in Ubuntu:
  Fix Committed
Status in gtk+3.0 source package in Bionic:
  In Progress
Status in gtk+3.0 source package in Cosmic:
  In Progress

Bug description:
  Impact
  ==
  Some emoji in the emoji chooser show as black & white.

  This is because these emoji default to "text presentation" instead of
  "emoji presentation".

  More information and a screenshot can be found in the pango issue
  linked below.

  Test Case
  =
  In an app like gedit, right click in the text area and select Insert Emoji
  Browse through the emoji list. All should be in full color.

  Regression Potential
  
  The fix for this was pushed to the stable gtk-3-24 branch.

  https://gitlab.gnome.org/GNOME/pango/issues/334
  https://gitlab.gnome.org/GNOME/gtk/commit/aac38198a3f5
  https://gitlab.gnome.org/GNOME/gtk/commit/b74e3209a5af0

  Other Info
  ==
  This adds an extra variation selector byte to each emoji added via the emoji 
chooser. (Many emoji are made up of multiple bytes.) This will not affect emoji 
added to GTK apps in other ways, such as copying and pasting from an app where 
the emoji doesn't have that variation selector added to it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1807719/+subscriptions

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


[Touch-packages] [Bug 1807721] Re: Fix variant selection in emoji chooser

2018-12-10 Thread Jeremy Bicha
** Description changed:

  Impact
  ==
  The variant selector in the emoji chooser was broken and will crash the app 
if used.
  
  Test Case
  =
  In an app like gedit, right click in the text area and select Insert Emoji
  Look for one of the "people" emoji.
- Right-click on the emoji and select one of the skin tones instead of the 
default yellow.
+ Right-click (or long-click) on the emoji and select one of the skin tones 
instead of the default yellow.
  The emoji with the skin tone you selected should be added to the text area.
  
  Regression Potential
  
  The fix for this was pushed to the stable gtk-3-24 branch.
  
  https://gitlab.gnome.org/GNOME/gtk/commit/dbbc7b3859f4b
  https://gitlab.gnome.org/GNOME/gtk/issues/1398

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

Title:
  Fix variant selection in emoji chooser

Status in gtk+3.0 package in Ubuntu:
  Fix Committed

Bug description:
  Impact
  ==
  The variant selector in the emoji chooser was broken and will crash the app 
if used.

  Test Case
  =
  In an app like gedit, right click in the text area and select Insert Emoji
  Look for one of the "people" emoji.
  Right-click (or long-click) on the emoji and select one of the skin tones 
instead of the default yellow.
  The emoji with the skin tone you selected should be added to the text area.

  Regression Potential
  
  The fix for this was pushed to the stable gtk-3-24 branch.

  https://gitlab.gnome.org/GNOME/gtk/commit/dbbc7b3859f4b
  https://gitlab.gnome.org/GNOME/gtk/issues/1398

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1807721/+subscriptions

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


[Touch-packages] [Bug 1807721] [NEW] Fix variant selection in emoji chooser

2018-12-10 Thread Jeremy Bicha
Public bug reported:

Impact
==
The variant selector in the emoji chooser was broken and will crash the app if 
used.

Test Case
=
In an app like gedit, right click in the text area and select Insert Emoji
Look for one of the "people" emoji.
Right-click on the emoji and select one of the skin tones instead of the 
default yellow.
The emoji with the skin tone you selected should be added to the text area.

Regression Potential

The fix for this was pushed to the stable gtk-3-24 branch.

https://gitlab.gnome.org/GNOME/gtk/commit/dbbc7b3859f4b
https://gitlab.gnome.org/GNOME/gtk/issues/1398

** Affects: gtk+3.0 (Ubuntu)
 Importance: Medium
 Status: Fix Committed


** Tags: bionic cosmic

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

Title:
  Fix variant selection in emoji chooser

Status in gtk+3.0 package in Ubuntu:
  Fix Committed

Bug description:
  Impact
  ==
  The variant selector in the emoji chooser was broken and will crash the app 
if used.

  Test Case
  =
  In an app like gedit, right click in the text area and select Insert Emoji
  Look for one of the "people" emoji.
  Right-click on the emoji and select one of the skin tones instead of the 
default yellow.
  The emoji with the skin tone you selected should be added to the text area.

  Regression Potential
  
  The fix for this was pushed to the stable gtk-3-24 branch.

  https://gitlab.gnome.org/GNOME/gtk/commit/dbbc7b3859f4b
  https://gitlab.gnome.org/GNOME/gtk/issues/1398

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1807721/+subscriptions

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


[Touch-packages] [Bug 1807719] [NEW] Some emoji in emoji chooser are black & white

2018-12-10 Thread Jeremy Bicha
Public bug reported:

Impact
==
Some emoji in the emoji chooser show as black & white.

This is because these emoji default to "text presentation" instead of
"emoji presentation".

More information and a screenshot can be found in the pango issue linked
below.

Test Case
=
In an app like gedit, right click in the text area and select Insert Emoji
Browse through the emoji list. All should be in full color.

Regression Potential

The fix for this was pushed to the stable gtk-3-24 branch.

https://gitlab.gnome.org/GNOME/pango/issues/334
https://gitlab.gnome.org/GNOME/gtk/commit/aac38198a3f5
https://gitlab.gnome.org/GNOME/gtk/commit/b74e3209a5af0

Other Info
==
This adds an extra variation selector byte to each emoji added via the emoji 
chooser. (Many emoji are made up of multiple bytes.) This will not affect emoji 
added to GTK apps in other ways, such as copying and pasting from an app where 
the emoji doesn't have that variation selector added to it.

** Affects: gtk+3.0 (Ubuntu)
 Importance: Low
 Status: Fix Committed


** Tags: bionic cosmic

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

Title:
  Some emoji in emoji chooser are black & white

Status in gtk+3.0 package in Ubuntu:
  Fix Committed

Bug description:
  Impact
  ==
  Some emoji in the emoji chooser show as black & white.

  This is because these emoji default to "text presentation" instead of
  "emoji presentation".

  More information and a screenshot can be found in the pango issue
  linked below.

  Test Case
  =
  In an app like gedit, right click in the text area and select Insert Emoji
  Browse through the emoji list. All should be in full color.

  Regression Potential
  
  The fix for this was pushed to the stable gtk-3-24 branch.

  https://gitlab.gnome.org/GNOME/pango/issues/334
  https://gitlab.gnome.org/GNOME/gtk/commit/aac38198a3f5
  https://gitlab.gnome.org/GNOME/gtk/commit/b74e3209a5af0

  Other Info
  ==
  This adds an extra variation selector byte to each emoji added via the emoji 
chooser. (Many emoji are made up of multiple bytes.) This will not affect emoji 
added to GTK apps in other ways, such as copying and pasting from an app where 
the emoji doesn't have that variation selector added to it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1807719/+subscriptions

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


  1   2   3   4   5   6   7   8   9   10   >