[Touch-packages] [Bug 1934936] Re: package libwind0-heimdal 7.7.0+dfsg-2build1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libwind0-heimdal/changelog.Debian.gz', which is dif

2021-07-16 Thread Iain Lane
It's probably a bug in pkgstripfiles, will confirm

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

Title:
  package libwind0-heimdal 7.7.0+dfsg-2build1 failed to install/upgrade:
  trying to overwrite shared
  '/usr/share/doc/libwind0-heimdal/changelog.Debian.gz', which is
  different from other instances of package libwind0-heimdal:i386

Status in heimdal package in Ubuntu:
  Confirmed

Bug description:
  fresh 21.10 install and 1 reboot later it said there was additional
  updates and while doing so the error popped up

  ProblemType: Package
  DistroRelease: Ubuntu 21.10
  Package: libwind0-heimdal 7.7.0+dfsg-2build1
  ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21
  Uname: Linux 5.11.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu67
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Thu Jul  8 01:45:16 2021
  DuplicateSignature:
   package:libwind0-heimdal:7.7.0+dfsg-2build1
   Unpacking libwind0-heimdal:i386 (7.7.0+dfsg-2build1) over (7.7.0+dfsg-2) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-8FDC3J/53-libwind0-heimdal_7.7.0+dfsg-2build1_i386.deb 
(--unpack):
trying to overwrite shared 
'/usr/share/doc/libwind0-heimdal/changelog.Debian.gz', which is different from 
other instances of package libwind0-heimdal:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libwind0-heimdal/changelog.Debian.gz', which is different from 
other instances of package libwind0-heimdal:i386
  InstallationDate: Installed on 2021-06-05 (32 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  Python3Details: /usr/bin/python3.9, Python 3.9.6, python3-minimal, 3.9.4-1
  PythonDetails: N/A
  RebootRequiredPkgs:
   libc6
   libc6
  RelatedPackageVersions:
   dpkg 1.20.9ubuntu2
   apt  2.3.6
  SourcePackage: heimdal
  Title: package libwind0-heimdal 7.7.0+dfsg-2build1 failed to install/upgrade: 
trying to overwrite shared 
'/usr/share/doc/libwind0-heimdal/changelog.Debian.gz', which is different from 
other instances of package libwind0-heimdal:i386
  UpgradeStatus: Upgraded to impish on 2021-07-07 (0 days ago)

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


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


[Touch-packages] [Bug 1934936] Re: package libwind0-heimdal 7.7.0+dfsg-2build1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libwind0-heimdal/changelog.Debian.gz', which is dif

2021-07-16 Thread Iain Lane
** Changed in: heimdal (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  package libwind0-heimdal 7.7.0+dfsg-2build1 failed to install/upgrade:
  trying to overwrite shared
  '/usr/share/doc/libwind0-heimdal/changelog.Debian.gz', which is
  different from other instances of package libwind0-heimdal:i386

Status in heimdal package in Ubuntu:
  Confirmed

Bug description:
  fresh 21.10 install and 1 reboot later it said there was additional
  updates and while doing so the error popped up

  ProblemType: Package
  DistroRelease: Ubuntu 21.10
  Package: libwind0-heimdal 7.7.0+dfsg-2build1
  ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21
  Uname: Linux 5.11.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu67
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Thu Jul  8 01:45:16 2021
  DuplicateSignature:
   package:libwind0-heimdal:7.7.0+dfsg-2build1
   Unpacking libwind0-heimdal:i386 (7.7.0+dfsg-2build1) over (7.7.0+dfsg-2) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-8FDC3J/53-libwind0-heimdal_7.7.0+dfsg-2build1_i386.deb 
(--unpack):
trying to overwrite shared 
'/usr/share/doc/libwind0-heimdal/changelog.Debian.gz', which is different from 
other instances of package libwind0-heimdal:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libwind0-heimdal/changelog.Debian.gz', which is different from 
other instances of package libwind0-heimdal:i386
  InstallationDate: Installed on 2021-06-05 (32 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  Python3Details: /usr/bin/python3.9, Python 3.9.6, python3-minimal, 3.9.4-1
  PythonDetails: N/A
  RebootRequiredPkgs:
   libc6
   libc6
  RelatedPackageVersions:
   dpkg 1.20.9ubuntu2
   apt  2.3.6
  SourcePackage: heimdal
  Title: package libwind0-heimdal 7.7.0+dfsg-2build1 failed to install/upgrade: 
trying to overwrite shared 
'/usr/share/doc/libwind0-heimdal/changelog.Debian.gz', which is different from 
other instances of package libwind0-heimdal:i386
  UpgradeStatus: Upgraded to impish on 2021-07-07 (0 days ago)

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


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


[Touch-packages] [Bug 1934936] Re: package libwind0-heimdal 7.7.0+dfsg-2build1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libwind0-heimdal/changelog.Debian.gz', which is dif

2021-07-16 Thread Iain Lane
Yeah I'm getting this too on dist-upgrade, now that heimdal migrated to
impish.

laney@raleigh> diff -u <(xxd changelog.Debian.gz-amd64) <(xxd 
changelog.Debian.gz-i386)
--- /proc/self/fd/112021-07-16 11:20:29.165989264 +0100
+++ /proc/self/fd/202021-07-16 11:20:29.169989204 +0100
@@ -97,5 +97,5 @@
 0600: 8a9e 51d4 4f3c 479b 631a d7fa aea8 3049  ..Q.Ohttps://bugs.launchpad.net/bugs/1934936

Title:
  package libwind0-heimdal 7.7.0+dfsg-2build1 failed to install/upgrade:
  trying to overwrite shared
  '/usr/share/doc/libwind0-heimdal/changelog.Debian.gz', which is
  different from other instances of package libwind0-heimdal:i386

Status in heimdal package in Ubuntu:
  Confirmed

Bug description:
  fresh 21.10 install and 1 reboot later it said there was additional
  updates and while doing so the error popped up

  ProblemType: Package
  DistroRelease: Ubuntu 21.10
  Package: libwind0-heimdal 7.7.0+dfsg-2build1
  ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21
  Uname: Linux 5.11.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu67
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Thu Jul  8 01:45:16 2021
  DuplicateSignature:
   package:libwind0-heimdal:7.7.0+dfsg-2build1
   Unpacking libwind0-heimdal:i386 (7.7.0+dfsg-2build1) over (7.7.0+dfsg-2) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-8FDC3J/53-libwind0-heimdal_7.7.0+dfsg-2build1_i386.deb 
(--unpack):
trying to overwrite shared 
'/usr/share/doc/libwind0-heimdal/changelog.Debian.gz', which is different from 
other instances of package libwind0-heimdal:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libwind0-heimdal/changelog.Debian.gz', which is different from 
other instances of package libwind0-heimdal:i386
  InstallationDate: Installed on 2021-06-05 (32 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  Python3Details: /usr/bin/python3.9, Python 3.9.6, python3-minimal, 3.9.4-1
  PythonDetails: N/A
  RebootRequiredPkgs:
   libc6
   libc6
  RelatedPackageVersions:
   dpkg 1.20.9ubuntu2
   apt  2.3.6
  SourcePackage: heimdal
  Title: package libwind0-heimdal 7.7.0+dfsg-2build1 failed to install/upgrade: 
trying to overwrite shared 
'/usr/share/doc/libwind0-heimdal/changelog.Debian.gz', which is different from 
other instances of package libwind0-heimdal:i386
  UpgradeStatus: Upgraded to impish on 2021-07-07 (0 days ago)

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


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


[Touch-packages] [Bug 1934936] Re: package libwind0-heimdal 7.7.0+dfsg-2build1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libwind0-heimdal/changelog.Debian.gz', which is dif

2021-07-16 Thread Iain Lane
welp, this is more sensible as a thing to look at:

laney@raleigh> diff -u <(zcat changelog.Debian.gz-amd64) <(zcat 
changelog.Debian.gz-i386)
--- /proc/self/fd/112021-07-16 11:22:45.935902600 +0100
+++ /proc/self/fd/202021-07-16 11:22:45.939902539 +0100
@@ -95,4 +95,4 @@
 
  -- Brian May   Wed, 26 Apr 2017 19:38:20 +1000
 
-# For older changelog entries, run 'apt-get changelog libwind0-heimdal'
+# For older changelog entries, run 'apt-get changelog libheimbase1-heimdal'

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

Title:
  package libwind0-heimdal 7.7.0+dfsg-2build1 failed to install/upgrade:
  trying to overwrite shared
  '/usr/share/doc/libwind0-heimdal/changelog.Debian.gz', which is
  different from other instances of package libwind0-heimdal:i386

Status in heimdal package in Ubuntu:
  Confirmed

Bug description:
  fresh 21.10 install and 1 reboot later it said there was additional
  updates and while doing so the error popped up

  ProblemType: Package
  DistroRelease: Ubuntu 21.10
  Package: libwind0-heimdal 7.7.0+dfsg-2build1
  ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21
  Uname: Linux 5.11.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu67
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Thu Jul  8 01:45:16 2021
  DuplicateSignature:
   package:libwind0-heimdal:7.7.0+dfsg-2build1
   Unpacking libwind0-heimdal:i386 (7.7.0+dfsg-2build1) over (7.7.0+dfsg-2) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-8FDC3J/53-libwind0-heimdal_7.7.0+dfsg-2build1_i386.deb 
(--unpack):
trying to overwrite shared 
'/usr/share/doc/libwind0-heimdal/changelog.Debian.gz', which is different from 
other instances of package libwind0-heimdal:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libwind0-heimdal/changelog.Debian.gz', which is different from 
other instances of package libwind0-heimdal:i386
  InstallationDate: Installed on 2021-06-05 (32 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  Python3Details: /usr/bin/python3.9, Python 3.9.6, python3-minimal, 3.9.4-1
  PythonDetails: N/A
  RebootRequiredPkgs:
   libc6
   libc6
  RelatedPackageVersions:
   dpkg 1.20.9ubuntu2
   apt  2.3.6
  SourcePackage: heimdal
  Title: package libwind0-heimdal 7.7.0+dfsg-2build1 failed to install/upgrade: 
trying to overwrite shared 
'/usr/share/doc/libwind0-heimdal/changelog.Debian.gz', which is different from 
other instances of package libwind0-heimdal:i386
  UpgradeStatus: Upgraded to impish on 2021-07-07 (0 days ago)

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


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


[Touch-packages] [Bug 1930359] Re: glib2.0: Uninitialised memory is written to gschema.compiled, failure to parse this file leads to gdm, gnome-shell failing to start

2021-07-12 Thread Iain Lane
> Looks like both of us sponsored it for the queue. I'd appreciate
rejecting either one of them.

I pushed to the VCS[0] at the same time as sponsoring, so I'll reject
the other one which doesn't quite match up with it.

[0] https://salsa.debian.org/gnome-
team/glib/-/commits/ubuntu/2.64.6-1_ubuntu20.04.4/

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

Title:
  glib2.0: Uninitialised memory is written to gschema.compiled, failure
  to parse this file leads to gdm, gnome-shell failing to start

Status in GLib:
  Unknown
Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Focal:
  In Progress

Bug description:
  [Impact]

  A recent SRU of mutter 3.36.9-0ubuntu0.20.04.1 caused an outage for a
  user with 300 VDIs running Focal, where GNOME applications would fail
  to start, and if you reboot, gdm and gnome-shell both fail to start,
  and you are left with a black screen and a blinking cursor.

  After much investigation, mutter was not at fault. Instead, mutter-
  common calls the libglib2.0-0 hook on upgrade:

  Processing triggers for libglib2.0-0:amd64 (2.64.6-1~ubuntu20.04.3)
  ...

  This in turn calls glib-compile-schemas to recompile the gsettings
  gschema cache, from the files in /usr/share/glib-2.0/schemas/. The
  result is a binary gschemas.compiled file, which is loaded by
  libglib2.0 on every invocation of a GNOME application, or gdm or
  gnome-shell to fetch application default settings.

  Now, glib2.0 2.64.6-1~ubuntu20.04.3 in Focal has some non-
  deterministic behaviour when calling glib-compile-schemas, causing
  generated gschemas.compiled files to have differing contents on each
  run:

  # glib-compile-schemas /usr/share/glib-2.0/schemas
  # cmp -l /home/ubuntu/schemas/gschemas.compiled 
/usr/share/glib-2.0/schemas/gschemas.compiled | gawk '{printf "%08X %02X 
%02X\n", $1, strtonum(0$2), strtonum(0$3)}'
  376F E3 D0
  3771 A4 DB

  # glib-compile-schemas /usr/share/glib-2.0/schemas
  # cmp -l /home/ubuntu/schemas/gschemas.compiled 
/usr/share/glib-2.0/schemas/gschemas.compiled | gawk '{printf "%08X %02X 
%02X\n", $1, strtonum(0$2), strtonum(0$3)}'
  376F E3 C3
  3771 A4 98

  # glib-compile-schemas /usr/share/glib-2.0/schemas
  # cmp -l /home/ubuntu/schemas/gschemas.compiled 
/usr/share/glib-2.0/schemas/gschemas.compiled | gawk '{printf "%08X %02X 
%02X\n", $1, strtonum(0$2), strtonum(0$3)}'
  376F E3 68
  3771 A4 30
  3772 55 56

  The bytes on the left are from a corrupted gschemas.compiled provided
  by an affected user. The changing bytes on the right are non-
  deterministic.

  I ran valgrind over glib-compile-schemas, and found that we are
  writing to uninitialised memory.

  https://paste.ubuntu.com/p/hvZccwdzxz/

  What is happening is that a submodule of glib, gvdb, contains the
  logic for serialising the gschema data structures, and when it
  allocates a buffer to store the eventual gschemas.compiled file, it
  does not initialise it.

  When we populate the fields in the buffer, some bytes are never
  overwritten, and these junk bytes find themselves written to
  gschemas.compiled.

  On boot, when gdm and gnome-shell attempt to parse and load this
  corrupted gschemas.compiled file, it can't parse the junk bytes, and
  raises and error, which propagates up to a breakpoint in glib logging,
  but no debugger is present, so the kernel traps the breakpoint, and
  terminates the library, and the calling application, e.g. gdm.

  The result is that the user is left starting at a black screen with a
  blinking pointer.

  [Testcase]

  On a Focal system, simply run valgrind over glib-compile-schemas:

  # valgrind glib-compile-schemas /usr/share/glib-2.0/schemas

  You will get output like this, with the warning "Syscall param
  write(buf) points to uninitialised byte(s)":

  https://paste.ubuntu.com/p/hvZccwdzxz/

  If you happen to have a large amount of gschema overrides present on
  your system, like my affected user does, you can save a copy of a
  generated gschema.compiled to your home directory and bindiff it
  against recompiles:

  # glib-compile-schemas /usr/share/glib-2.0/schemas
  # cp /usr/share/glib-2.0/schemas/gschema.compiled 
/home/ubuntu/schemas/gschemas.compiled
  # glib-compile-schemas /usr/share/glib-2.0/schemas
  # cmp -l /home/ubuntu/schemas/gschemas.compiled 
/usr/share/glib-2.0/schemas/gschemas.compiled | gawk '{printf "%08X %02X 
%02X\n", $1, strtonum(0$2), strtonum(0$3)}'
  376F E3 C3
  3771 A4 98

  If you install the test package from the following ppa:

  https://launchpad.net/~mruffell/+archive/ubuntu/sf311791-test

  When you run valgrind, it will report a clean run with no writing to
  uninitialised buffers, and all invocations of glib-compile-schemas
  will be deterministic, and generate the file same with the same sha256
  hash every 

[Touch-packages] [Bug 1930359] Re: glib2.0: Uninitialised memory is written to gschema.compiled, failure to parse this file leads to gdm, gnome-shell failing to start

2021-07-12 Thread Iain Lane
Thanks, sponsored to the queue

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

Title:
  glib2.0: Uninitialised memory is written to gschema.compiled, failure
  to parse this file leads to gdm, gnome-shell failing to start

Status in GLib:
  Unknown
Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Focal:
  In Progress

Bug description:
  [Impact]

  A recent SRU of mutter 3.36.9-0ubuntu0.20.04.1 caused an outage for a
  user with 300 VDIs running Focal, where GNOME applications would fail
  to start, and if you reboot, gdm and gnome-shell both fail to start,
  and you are left with a black screen and a blinking cursor.

  After much investigation, mutter was not at fault. Instead, mutter-
  common calls the libglib2.0-0 hook on upgrade:

  Processing triggers for libglib2.0-0:amd64 (2.64.6-1~ubuntu20.04.3)
  ...

  This in turn calls glib-compile-schemas to recompile the gsettings
  gschema cache, from the files in /usr/share/glib-2.0/schemas/. The
  result is a binary gschemas.compiled file, which is loaded by
  libglib2.0 on every invocation of a GNOME application, or gdm or
  gnome-shell to fetch application default settings.

  Now, glib2.0 2.64.6-1~ubuntu20.04.3 in Focal has some non-
  deterministic behaviour when calling glib-compile-schemas, causing
  generated gschemas.compiled files to have differing contents on each
  run:

  # glib-compile-schemas /usr/share/glib-2.0/schemas
  # cmp -l /home/ubuntu/schemas/gschemas.compiled 
/usr/share/glib-2.0/schemas/gschemas.compiled | gawk '{printf "%08X %02X 
%02X\n", $1, strtonum(0$2), strtonum(0$3)}'
  376F E3 D0
  3771 A4 DB

  # glib-compile-schemas /usr/share/glib-2.0/schemas
  # cmp -l /home/ubuntu/schemas/gschemas.compiled 
/usr/share/glib-2.0/schemas/gschemas.compiled | gawk '{printf "%08X %02X 
%02X\n", $1, strtonum(0$2), strtonum(0$3)}'
  376F E3 C3
  3771 A4 98

  # glib-compile-schemas /usr/share/glib-2.0/schemas
  # cmp -l /home/ubuntu/schemas/gschemas.compiled 
/usr/share/glib-2.0/schemas/gschemas.compiled | gawk '{printf "%08X %02X 
%02X\n", $1, strtonum(0$2), strtonum(0$3)}'
  376F E3 68
  3771 A4 30
  3772 55 56

  The bytes on the left are from a corrupted gschemas.compiled provided
  by an affected user. The changing bytes on the right are non-
  deterministic.

  I ran valgrind over glib-compile-schemas, and found that we are
  writing to uninitialised memory.

  https://paste.ubuntu.com/p/hvZccwdzxz/

  What is happening is that a submodule of glib, gvdb, contains the
  logic for serialising the gschema data structures, and when it
  allocates a buffer to store the eventual gschemas.compiled file, it
  does not initialise it.

  When we populate the fields in the buffer, some bytes are never
  overwritten, and these junk bytes find themselves written to
  gschemas.compiled.

  On boot, when gdm and gnome-shell attempt to parse and load this
  corrupted gschemas.compiled file, it can't parse the junk bytes, and
  raises and error, which propagates up to a breakpoint in glib logging,
  but no debugger is present, so the kernel traps the breakpoint, and
  terminates the library, and the calling application, e.g. gdm.

  The result is that the user is left starting at a black screen with a
  blinking pointer.

  [Testcase]

  On a Focal system, simply run valgrind over glib-compile-schemas:

  # valgrind glib-compile-schemas /usr/share/glib-2.0/schemas

  You will get output like this, with the warning "Syscall param
  write(buf) points to uninitialised byte(s)":

  https://paste.ubuntu.com/p/hvZccwdzxz/

  If you happen to have a large amount of gschema overrides present on
  your system, like my affected user does, you can save a copy of a
  generated gschema.compiled to your home directory and bindiff it
  against recompiles:

  # glib-compile-schemas /usr/share/glib-2.0/schemas
  # cp /usr/share/glib-2.0/schemas/gschema.compiled 
/home/ubuntu/schemas/gschemas.compiled
  # glib-compile-schemas /usr/share/glib-2.0/schemas
  # cmp -l /home/ubuntu/schemas/gschemas.compiled 
/usr/share/glib-2.0/schemas/gschemas.compiled | gawk '{printf "%08X %02X 
%02X\n", $1, strtonum(0$2), strtonum(0$3)}'
  376F E3 C3
  3771 A4 98

  If you install the test package from the following ppa:

  https://launchpad.net/~mruffell/+archive/ubuntu/sf311791-test

  When you run valgrind, it will report a clean run with no writing to
  uninitialised buffers, and all invocations of glib-compile-schemas
  will be deterministic, and generate the file same with the same sha256
  hash every time. The unwritten bytes if you do a bindiff from before
  and after will be all set to zero.

  [Where problems can occur]

  I am doubtful that any programs are relying on buggy non-deterministic
  behaviour from random bytes found in uninitialised memory, so this
  should be a 

Re: [Touch-packages] [Bug 1934505] Re: gdb 11 doesn't work on impish/s390x: internal-error: displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*, thread_info*, CORE_ADDR&): Assertion `g

2021-07-07 Thread Iain Lane
On Wed, Jul 07, 2021 at 08:30:32AM -, Matthias Klose wrote:
> fixed in 11.0.90.20210705-0ubuntu2

yep, thanks for reproducing and forwarding!

-- 
Iain Lane  [ i...@orangesquash.org.uk ]
Debian Developer   [ la...@debian.org ]
Ubuntu Developer   [ la...@ubuntu.com ]

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

Title:
  gdb 11 doesn't work on impish/s390x: internal-error:
  displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*,
  thread_info*, CORE_ADDR&): Assertion
  `gdbarch_data->num_disp_step_buffers > 0' failed.

Status in gdb:
  Confirmed
Status in gdb package in Ubuntu:
  Fix Released

Bug description:
  gdb doesn't work on impish/s390x at the minute. Even if you say 'no'
  to both questions you still can't debug:

  ubuntu@laney-bos01-s390x-2:~/glib-networking-2.66.0/build$ gdb ls
  GNU gdb (Ubuntu 11.0.50.20210630-0ubuntu1) 11.0.50.20210630-git
  Copyright (C) 2021 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.
  Type "show copying" and "show warranty" for details.
  This GDB was configured as "s390x-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  <https://www.gnu.org/software/gdb/bugs/>.
  Find the GDB manual and other documentation resources online at:
  <http://www.gnu.org/software/gdb/documentation/>.

  For help, type "help".
  Type "apropos word" to search for commands related to "word"...
  Reading symbols from ls...
  (No debugging symbols found in ls)
  (gdb) run
  Starting program: /usr/bin/ls
  /build/gdb-Ti35un/gdb-11.0.50.20210630/gdb/linux-tdep.c:2550: internal-error: 
displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*, 
thread_info*, CORE_ADDR&): Assertion `gdbarch_data->num_disp_step_buffers > 0' 
failed.
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.
  Quit this debugging session? (y or n) n

  This is a bug, please report it.  For instructions, see:
  <https://www.gnu.org/software/gdb/bugs/>.

  /build/gdb-Ti35un/gdb-11.0.50.20210630/gdb/linux-tdep.c:2550: internal-error: 
displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*, 
thread_info*, CORE_ADDR&): Assertion `gdbarch_data->num_disp_step_buffers > 0' 
failed.
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.
  Create a core file of GDB? (y or n) n
  Command aborted.
  (gdb)

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

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


[Touch-packages] [Bug 1934505] Re: gdb 11 doesn't work on impish/s390x: internal-error: displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*, thread_info*, CORE_ADDR&): Assertion `gdbar

2021-07-05 Thread Iain Lane
** Summary changed:

- gdb 11 doesn't work on impish: internal-error: displaced_step_prepare_status 
linux_displaced_step_prepare(gdbarch*, thread_info*, CORE_ADDR&): Assertion 
`gdbarch_data->num_disp_step_buffers > 0' failed.
+ gdb 11 doesn't work on impish/s390x: internal-error: 
displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*, 
thread_info*, CORE_ADDR&): Assertion `gdbarch_data->num_disp_step_buffers > 0' 
failed.

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

Title:
  gdb 11 doesn't work on impish/s390x: internal-error:
  displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*,
  thread_info*, CORE_ADDR&): Assertion
  `gdbarch_data->num_disp_step_buffers > 0' failed.

Status in gdb:
  Confirmed
Status in gdb package in Ubuntu:
  Confirmed

Bug description:
  gdb doesn't work on impish/s390x at the minute. Even if you say 'no'
  to both questions you still can't debug:

  ubuntu@laney-bos01-s390x-2:~/glib-networking-2.66.0/build$ gdb ls
  GNU gdb (Ubuntu 11.0.50.20210630-0ubuntu1) 11.0.50.20210630-git
  Copyright (C) 2021 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.
  Type "show copying" and "show warranty" for details.
  This GDB was configured as "s390x-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .

  For help, type "help".
  Type "apropos word" to search for commands related to "word"...
  Reading symbols from ls...
  (No debugging symbols found in ls)
  (gdb) run
  Starting program: /usr/bin/ls
  /build/gdb-Ti35un/gdb-11.0.50.20210630/gdb/linux-tdep.c:2550: internal-error: 
displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*, 
thread_info*, CORE_ADDR&): Assertion `gdbarch_data->num_disp_step_buffers > 0' 
failed.
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.
  Quit this debugging session? (y or n) n

  This is a bug, please report it.  For instructions, see:
  .

  /build/gdb-Ti35un/gdb-11.0.50.20210630/gdb/linux-tdep.c:2550: internal-error: 
displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*, 
thread_info*, CORE_ADDR&): Assertion `gdbarch_data->num_disp_step_buffers > 0' 
failed.
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.
  Create a core file of GDB? (y or n) n
  Command aborted.
  (gdb)

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

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


[Touch-packages] [Bug 1934505] [NEW] gdb 11 doesn't work on impish: internal-error: displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*, thread_info*, CORE_ADDR&): Assertion `gdbarch_d

2021-07-02 Thread Iain Lane
Public bug reported:

gdb doesn't work on impish/s390x at the minute. Even if you say 'no' to
both questions you still can't debug:

ubuntu@laney-bos01-s390x-2:~/glib-networking-2.66.0/build$ gdb ls
GNU gdb (Ubuntu 11.0.50.20210630-0ubuntu1) 11.0.50.20210630-git
Copyright (C) 2021 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "s390x-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from ls...
(No debugging symbols found in ls)
(gdb) run
Starting program: /usr/bin/ls
/build/gdb-Ti35un/gdb-11.0.50.20210630/gdb/linux-tdep.c:2550: internal-error: 
displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*, 
thread_info*, CORE_ADDR&): Assertion `gdbarch_data->num_disp_step_buffers > 0' 
failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) n

This is a bug, please report it.  For instructions, see:
.

/build/gdb-Ti35un/gdb-11.0.50.20210630/gdb/linux-tdep.c:2550: internal-error: 
displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*, 
thread_info*, CORE_ADDR&): Assertion `gdbarch_data->num_disp_step_buffers > 0' 
failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Create a core file of GDB? (y or n) n
Command aborted.
(gdb)

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

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

Title:
  gdb 11 doesn't work on impish: internal-error:
  displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*,
  thread_info*, CORE_ADDR&): Assertion
  `gdbarch_data->num_disp_step_buffers > 0' failed.

Status in gdb package in Ubuntu:
  New

Bug description:
  gdb doesn't work on impish/s390x at the minute. Even if you say 'no'
  to both questions you still can't debug:

  ubuntu@laney-bos01-s390x-2:~/glib-networking-2.66.0/build$ gdb ls
  GNU gdb (Ubuntu 11.0.50.20210630-0ubuntu1) 11.0.50.20210630-git
  Copyright (C) 2021 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.
  Type "show copying" and "show warranty" for details.
  This GDB was configured as "s390x-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .

  For help, type "help".
  Type "apropos word" to search for commands related to "word"...
  Reading symbols from ls...
  (No debugging symbols found in ls)
  (gdb) run
  Starting program: /usr/bin/ls
  /build/gdb-Ti35un/gdb-11.0.50.20210630/gdb/linux-tdep.c:2550: internal-error: 
displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*, 
thread_info*, CORE_ADDR&): Assertion `gdbarch_data->num_disp_step_buffers > 0' 
failed.
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.
  Quit this debugging session? (y or n) n

  This is a bug, please report it.  For instructions, see:
  .

  /build/gdb-Ti35un/gdb-11.0.50.20210630/gdb/linux-tdep.c:2550: internal-error: 
displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*, 
thread_info*, CORE_ADDR&): Assertion `gdbarch_data->num_disp_step_buffers > 0' 
failed.
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.
  Create a core file of GDB? (y or n) n
  Command aborted.
  (gdb)

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

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


[Touch-packages] [Bug 1928931] Re: German strings in deja-dup.mo for en_GB

2021-06-24 Thread Iain Lane
Hmm no, it needs removing first, my upload got rejected.

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

Title:
  German strings in deja-dup.mo for en_GB

Status in language-pack-gnome-en package in Ubuntu:
  In Progress
Status in language-pack-gnome-en source package in Hirsute:
  Fix Committed

Bug description:
  [ Description ]

  Some German strings were accidentally translated under en_GB. They
  affect the default Ubuntu install - some of them are strings which are
  displayed as a notification some time after first logging in, so it's
  quite visible. See the attached screenshot.

  [ Fix ]

  Revert the German and go back to the proper English text. The way to
  fix langpacks is to upload the language-pack-gnome-XX package which
  replaces files in language-pack-gnome-XX-base.

  [ Devel release ]

  I'd like to propose to binary copy forward, and let the normal
  langpack release schedule take care of eventually dominating these
  away in impish.

  [ QA ]

  To verify the diff, compare deja-dup.po from language-pack-gnome-en-
  base to the one in this upload. You'll have to do that manually.

    0. Be in en_GB.
    1. Install the SRU
    2. In an Ubuntu Desktop session, open a terminal and run `deja-dup 
--prompt`.
    3. Note the buttons in the notification that shows up. They should be in 
English.

  [ What could go wrong ]

  1. There could be other instances of this in different packages we haven't 
noticed yet
  2. If I break the .po file, it could either break the build or the 
translations at runtime (but this is English, so if we fall back to C it's not 
too bad)
  3. If my diff is wrong then I might have dropped some en_GB translations or 
made them wrong

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-pack-gnome-en/+bug/1928931/+subscriptions

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


[Touch-packages] [Bug 1928931] Re: German strings in deja-dup.mo for en_GB

2021-06-24 Thread Iain Lane
Okay, done. I think: remove this, let the removal publish, accept the
new one.

Hopefully the ageing period can be waived on that.

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

Title:
  German strings in deja-dup.mo for en_GB

Status in language-pack-gnome-en package in Ubuntu:
  In Progress
Status in language-pack-gnome-en source package in Hirsute:
  Fix Committed

Bug description:
  [ Description ]

  Some German strings were accidentally translated under en_GB. They
  affect the default Ubuntu install - some of them are strings which are
  displayed as a notification some time after first logging in, so it's
  quite visible. See the attached screenshot.

  [ Fix ]

  Revert the German and go back to the proper English text. The way to
  fix langpacks is to upload the language-pack-gnome-XX package which
  replaces files in language-pack-gnome-XX-base.

  [ Devel release ]

  I'd like to propose to binary copy forward, and let the normal
  langpack release schedule take care of eventually dominating these
  away in impish.

  [ QA ]

  To verify the diff, compare deja-dup.po from language-pack-gnome-en-
  base to the one in this upload. You'll have to do that manually.

    0. Be in en_GB.
    1. Install the SRU
    2. In an Ubuntu Desktop session, open a terminal and run `deja-dup 
--prompt`.
    3. Note the buttons in the notification that shows up. They should be in 
English.

  [ What could go wrong ]

  1. There could be other instances of this in different packages we haven't 
noticed yet
  2. If I break the .po file, it could either break the build or the 
translations at runtime (but this is English, so if we fall back to C it's not 
too bad)
  3. If my diff is wrong then I might have dropped some en_GB translations or 
made them wrong

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-pack-gnome-en/+bug/1928931/+subscriptions

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


[Touch-packages] [Bug 1928931] Re: German strings in deja-dup.mo for en_GB

2021-06-24 Thread Iain Lane
Wait, isn't the version wrong? 1:21.10+20210415ubuntu1.

I'm going to re-upload to the queue with 1:21.04.

Also, can we just run a langpack export for impish to fix this there
please? The version is greater than hirsute's now so I can't just copy
up.

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

Title:
  German strings in deja-dup.mo for en_GB

Status in language-pack-gnome-en package in Ubuntu:
  In Progress
Status in language-pack-gnome-en source package in Hirsute:
  Fix Committed

Bug description:
  [ Description ]

  Some German strings were accidentally translated under en_GB. They
  affect the default Ubuntu install - some of them are strings which are
  displayed as a notification some time after first logging in, so it's
  quite visible. See the attached screenshot.

  [ Fix ]

  Revert the German and go back to the proper English text. The way to
  fix langpacks is to upload the language-pack-gnome-XX package which
  replaces files in language-pack-gnome-XX-base.

  [ Devel release ]

  I'd like to propose to binary copy forward, and let the normal
  langpack release schedule take care of eventually dominating these
  away in impish.

  [ QA ]

  To verify the diff, compare deja-dup.po from language-pack-gnome-en-
  base to the one in this upload. You'll have to do that manually.

    0. Be in en_GB.
    1. Install the SRU
    2. In an Ubuntu Desktop session, open a terminal and run `deja-dup 
--prompt`.
    3. Note the buttons in the notification that shows up. They should be in 
English.

  [ What could go wrong ]

  1. There could be other instances of this in different packages we haven't 
noticed yet
  2. If I break the .po file, it could either break the build or the 
translations at runtime (but this is English, so if we fall back to C it's not 
too bad)
  3. If my diff is wrong then I might have dropped some en_GB translations or 
made them wrong

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-pack-gnome-en/+bug/1928931/+subscriptions

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


[Touch-packages] [Bug 1918044] Re: (Update libgweather to 3.36.2) Weather forecast and info is not available anymore

2021-06-22 Thread Iain Lane
** Also affects: libgweather (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: gnome-weather (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Changed in: gnome-weather (Ubuntu)
   Status: Confirmed => Fix Released

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

** Changed in: gnome-weather (Ubuntu Focal)
 Assignee: (unassigned) => Iain Lane (laney)

** Changed in: libgweather (Ubuntu Focal)
 Assignee: (unassigned) => Iain Lane (laney)

** Tags removed: rls-ff-incoming

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

Title:
  (Update libgweather to 3.36.2) Weather forecast and info is not
  available anymore

Status in libgweather:
  Unknown
Status in gnome-weather package in Ubuntu:
  Fix Released
Status in libgweather package in Ubuntu:
  Fix Released
Status in gnome-weather source package in Focal:
  New
Status in libgweather source package in Focal:
  New
Status in gnome-weather package in Fedora:
  New

Bug description:
  [Impact]

  The weather forecast is not available since one week now. Also, the
  weather info is gone from gnome-shell.

  The weather service provider retired their old API.
  
https://developer.yr.no/news/important-changes-to-locationforecast-and-nowcast/

  https://gitlab.gnome.org/GNOME/libgweather/-/blob/gnome-3-36/NEWS

  ==
  Version 3.36.2
  ==

  This version switches the yr.no backend to use met.no instead. Please note
  that this backport is only meant as a compatibility layer. Where at all
  possible, the newer libgweather 40 should be used as applications cannot
  fully comply with the met.no ToS otherwise.

  
  [Test case]

  - gnome-weather shows the weather forecast
  - gnome-shell shows the weather forecast in the calendar menu

  
  [Regression potential]

  - Weather forecast is totally broken now and can't be more broken.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libgweather-3-16 3.36.1-1~ubuntu20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar  7 09:54:52 2021
  InstallationDate: Installed on 2020-04-26 (314 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: libgweather
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1925742] Re: Recent iCloud versions trigger an issue in IMAP x

2021-06-22 Thread Iain Lane
** Changed in: evolution-data-server (Ubuntu Hirsute)
 Assignee: (unassigned) => Sebastien Bacher (seb128)

** Tags removed: rls-hh-incoming

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

Title:
  Recent iCloud versions trigger an issue in IMAP x

Status in evolution-data-server package in Ubuntu:
  Fix Released
Status in evolution-data-server source package in Focal:
  Fix Released
Status in evolution-data-server source package in Hirsute:
  Triaged

Bug description:
  * Impact

  The Icloud service introduced changes that are confusing evolution-
  data-server which means evolution is now failing to connect to the
  email server

  * Test case

  Set up an iCloud account and try to use it for emails in evolution

  * Regression potential

  The change is in the imapx connection code, it could create problems
  with other type of servers so we should try to test on different
  providers.

  
  -


  The bug has been fixed yesterday by Evolution's developer:
  https://gitlab.gnome.org/GNOME/evolution/-/issues/1468

  However, the package in Ubuntu (at least in Focal Fosa) still needs to
  be updated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1925742/+subscriptions

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


[Touch-packages] [Bug 1918855] Re: Xorg xserver got signal 6 to abort

2021-06-22 Thread Iain Lane
** Changed in: mesa (Ubuntu Focal)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

** Changed in: mesa (Ubuntu Hirsute)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

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

Title:
  Xorg xserver got signal 6 to abort

Status in Mesa:
  Unknown
Status in OEM Priority Project:
  In Progress
Status in Provider for Plainbox - Checkbox:
  New
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Focal:
  New
Status in mesa source package in Hirsute:
  New

Bug description:
  == SRU Justification ==
  [Impact]
  When the system is under memory pressure, the entire desktop session may 
crash.

  [Fix]
  Commit f9d8d9acbb6a620684fb4dac4affe25816587d92 ("iris: Avoid abort() if 
kernel can't allocate memory")

  [Test]
  Run memory stress and the session crashed in less than 5 minutes.
  With the fix applied, run memory stress for 24 hours and the desktop session 
is still alive.

  [Where problems could occur]
  Doing a reset might make the system even more sluggish when under memory 
pressure.

  
  == Original bug report ==
  I run checkbox job com.canonical.certification::memory/memory_stress_ng on 
focal, and the xserver stops unexpectedly with the following stacktrace:

  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg 
(OsLookupColor+0x13c) [0x5619f3a4d59c]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 1: 
/lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 
(gsignal+0xcb) [0x7fae476a418b]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 
(abort+0x12b) [0x7fae47683859]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind 
info found [-10]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 4: 
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 5: 
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec) 
[0x7fae46529c9c]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 6: 
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so 
(__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 7: 
/usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150) 
[0x7fae47007480]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind 
info found [-10]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 8: 
/usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg 
(BlockHandler+0xa5) [0x5619f38f0995]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg 
(WaitForSomething+0x122) [0x5619f3a46c12]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg 
(SendErrorToClient+0x117) [0x5619f38ebcf7]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg 
(InitFonts+0x3b4) [0x5619f38effc4]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf3) [0x7fae476850b3]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e) 
[0x5619f38d9a2e]

  More info:
  I searched the Internet and got a bug with the same stacktrace:
  https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468
  https://gitlab.freedesktop.org/mesa/mesa/-/issues/2859

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

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


[Touch-packages] [Bug 1932311] Re: migrate to llvm 12

2021-06-22 Thread Iain Lane
** Changed in: mesa (Ubuntu Focal)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

** Changed in: mesa (Ubuntu Hirsute)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

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

Title:
  migrate to llvm 12

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Focal:
  New
Status in mesa source package in Hirsute:
  New

Bug description:
  (split off from bug 1917763)

  [Impact]

  Mesa should migrate to llvm 12 for new AMDGPU features and HW support.
  Normally this would be done during the devel series, but this version
  was delayed too much to migrate before hirsute was out.

  [Fix]
  Build-depend on the new packages, including libclc which is now built from 
llvm sources.

  [Test case]

  Test AMD graphics and/or qemu desktop (llvmpipe) after installing
  migrated packages.

  [Regression potential]

  This has been in Impish for a month now without issues.

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

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


[Touch-packages] [Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm

2021-06-22 Thread Iain Lane
** Changed in: accountsservice (Ubuntu Groovy)
   Status: New => Invalid

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

** Changed in: gnome-shell (Ubuntu Groovy)
   Status: New => Invalid

** Changed in: gnome-shell (Ubuntu Hirsute)
   Status: New => Invalid

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

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

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

Title:
  dbus timeout-ed during an upgrade, taking services down including gdm

Status in D-Bus:
  Unknown
Status in systemd:
  New
Status in accountsservice package in Ubuntu:
  Invalid
Status in dbus package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Invalid
Status in accountsservice source package in Focal:
  Invalid
Status in dbus source package in Focal:
  Incomplete
Status in gnome-shell source package in Focal:
  Invalid
Status in accountsservice source package in Groovy:
  Invalid
Status in dbus source package in Groovy:
  Incomplete
Status in gnome-shell source package in Groovy:
  Invalid
Status in accountsservice source package in Hirsute:
  Invalid
Status in dbus source package in Hirsute:
  Incomplete
Status in gnome-shell source package in Hirsute:
  Invalid
Status in accountsservice source package in Impish:
  Invalid
Status in dbus source package in Impish:
  Incomplete
Status in gnome-shell source package in Impish:
  Invalid

Bug description:
  This morning I found my computer on the login screen.
  But not the one of the screen log, no a new one - so something must have 
crashed.

  Logging in again confirmed that all apps were gone and the gnome shell
  was brought down what seems like triggered by a background update o
  accountsservice.

  As always things are not perfectly clear :-/
  The following goes *back* in time through my logs one by one.

  Multiple apps crashed at 06:09, but we will find later that this is a follow 
on issue of the underlying gnome/X/... recycling.
  -rw-r-  1 paelzer  whoopsie 52962868 Apr  8 06:09 
_usr_bin_konversation.1000.crash
  -rw-r-  1 paelzer  whoopsie   986433 Apr  8 06:09 
_usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash

  
  rdkit was failing fast and giving up (that will be a different bug, it just 
seems broken on my system):
  Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling 
Policy Service.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully called 
chroot.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully dropped 
privileges.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully limited 
resources.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: pthread_create failed: 
Resource temporarily unavailable
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Canary thread running.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Exiting canary thread.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoting known real-time 
threads.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoted 0 threads.
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Main process 
exited, code=exited, status=1/FAILURE
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with 
result 'exit-code'.
  Apr 08 06:10:13 Keschdeichel dbus-daemon[1208]: [system] Activating via 
systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.1176' (uid=121 pid=>
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Start request 
repeated too quickly.
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with 
result 'exit-code'.
  Apr 08 06:10:13 Keschdeichel systemd[1]: Failed to start RealtimeKit 
Scheduling Policy Service.
  Apr 08 06:10:13 Keschdeichel bluetoothd[1729331]: Bluetooth daemon 5.53

  
  But that already was only triggered by a gnome restart that kicked of earlier:

  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Started GNOME Shell on Wayland.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Shell on 
Wayland.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session 
is initialized.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Wayland 
Session.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session 
(session: gnome-login).

  
  X was recycleing before:
  Apr 08 06:09:19 Keschdeichel systemd[10683]: Stopping GNOME Shell on X11...
  ...
  Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (EE) 
systemd-logind: ReleaseControl failed: Unknown object 
'/org/freedesktop/login1/session/_32'.
  Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (II) Server 
terminated successfully (0). Closing log 

[Touch-packages] [Bug 1928931] Re: German strings in deja-dup.mo for en_GB

2021-06-22 Thread Iain Lane
> hm, do we actually know *why* this happened?

Yes, someone mis-translated the strings on Launchpad. I reverted them
all now, but I don't think we have any way of dealing with that
happening again, do we?

I've just verified the SRU. I installed language-pack-gnome-en
1:21.10+20210415ubuntu1 and ran deja-dup --prompt. With the SRU the
buttons are in English again!

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

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

Title:
  German strings in deja-dup.mo for en_GB

Status in language-pack-gnome-en package in Ubuntu:
  In Progress
Status in language-pack-gnome-en source package in Hirsute:
  Fix Committed

Bug description:
  [ Description ]

  Some German strings were accidentally translated under en_GB. They
  affect the default Ubuntu install - some of them are strings which are
  displayed as a notification some time after first logging in, so it's
  quite visible. See the attached screenshot.

  [ Fix ]

  Revert the German and go back to the proper English text. The way to
  fix langpacks is to upload the language-pack-gnome-XX package which
  replaces files in language-pack-gnome-XX-base.

  [ Devel release ]

  I'd like to propose to binary copy forward, and let the normal
  langpack release schedule take care of eventually dominating these
  away in impish.

  [ QA ]

  To verify the diff, compare deja-dup.po from language-pack-gnome-en-
  base to the one in this upload. You'll have to do that manually.

    0. Be in en_GB.
    1. Install the SRU
    2. In an Ubuntu Desktop session, open a terminal and run `deja-dup 
--prompt`.
    3. Note the buttons in the notification that shows up. They should be in 
English.

  [ What could go wrong ]

  1. There could be other instances of this in different packages we haven't 
noticed yet
  2. If I break the .po file, it could either break the build or the 
translations at runtime (but this is English, so if we fall back to C it's not 
too bad)
  3. If my diff is wrong then I might have dropped some en_GB translations or 
made them wrong

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-pack-gnome-en/+bug/1928931/+subscriptions

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


Re: [Touch-packages] [Bug 1894619] Re: [2.82 regression] router announcements have 'forever' lifetime by default

2021-06-21 Thread Iain Lane
On Mon, Jun 21, 2021 at 05:53:41AM -, Christian Ehrhardt  wrote:
> We finally got an answer to our questions/pings (thanks Simon)
> => 
> https://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2021q2/015134.html
> 
> TL;DR: this might be wanted new behavior :/ ?!
> 
> @Laney - You initially started this when we have faced this bug
> I wonder now if we should indeed drop our delta and resolve the fallout in 
> other places like the formerly breaking tests.
> You have back then thought deeper into this, while I only carried this delta 
> a few times.
> Therefore I'd appreciate if you could let me know what you think of that 
> reply.
> 
> P.S. Because if we drop it then I guess we better do that now than e.g.
> late in 22.04 :-)

I don't know to be honest. What do you think, does that argument make 
sense? I don't really understand why it should be different whether 
you're using DHCPv6 or SLAAC, but maybe it's just me not getting 
something right now.

If it's fine, then feel free to drop the patch and upload a NM with 
adjusted regexes (preferrably committing to the VCS too).

Cheers,

-- 
Iain Lane  [ i...@orangesquash.org.uk ]
Debian Developer   [ la...@debian.org ]
Ubuntu Developer   [ la...@ubuntu.com ]

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

Title:
  [2.82 regression] router announcements have 'forever' lifetime by
  default

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

Bug description:
  The default lifetime was changed to 1 day in 2.82 in the change
  corresponding to this changelog entry:

  Change default lease time for DHCPv6 to one day.

  Fine, but the same commit also did this:

Alter calculation of preferred and valid times in router
advertisements, so that these do not have a floor applied
of the lease time in the dhcp-range if this is not explicitly
specified and is merely the default.

  And that change is buggy and causes advertisements to have infinite
  lifetime, when you are using the default.

  See this thread

http://lists.thekelleys.org.uk/pipermail/dnsmasq-
  discuss/2020q3/014341.html

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

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


[Touch-packages] [Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm

2021-06-17 Thread Iain Lane
I filed an upstream bug with D-Bus:
https://gitlab.freedesktop.org/dbus/dbus/-/issues/337

Hopefully a maintainer there will be able to give a better opinion as to
what's going on here

** Bug watch added: gitlab.freedesktop.org/dbus/dbus/-/issues #337
   https://gitlab.freedesktop.org/dbus/dbus/-/issues/337

** Also affects: dbus via
   https://gitlab.freedesktop.org/dbus/dbus/-/issues/337
   Importance: Unknown
   Status: Unknown

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

Title:
  dbus timeout-ed during an upgrade, taking services down including gdm

Status in D-Bus:
  Unknown
Status in systemd:
  New
Status in accountsservice package in Ubuntu:
  Invalid
Status in dbus package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Invalid
Status in accountsservice source package in Focal:
  Invalid
Status in dbus source package in Focal:
  Incomplete
Status in gnome-shell source package in Focal:
  Invalid
Status in accountsservice source package in Groovy:
  New
Status in dbus source package in Groovy:
  New
Status in gnome-shell source package in Groovy:
  New
Status in accountsservice source package in Hirsute:
  New
Status in dbus source package in Hirsute:
  New
Status in gnome-shell source package in Hirsute:
  New
Status in accountsservice source package in Impish:
  Invalid
Status in dbus source package in Impish:
  Incomplete
Status in gnome-shell source package in Impish:
  Invalid

Bug description:
  This morning I found my computer on the login screen.
  But not the one of the screen log, no a new one - so something must have 
crashed.

  Logging in again confirmed that all apps were gone and the gnome shell
  was brought down what seems like triggered by a background update o
  accountsservice.

  As always things are not perfectly clear :-/
  The following goes *back* in time through my logs one by one.

  Multiple apps crashed at 06:09, but we will find later that this is a follow 
on issue of the underlying gnome/X/... recycling.
  -rw-r-  1 paelzer  whoopsie 52962868 Apr  8 06:09 
_usr_bin_konversation.1000.crash
  -rw-r-  1 paelzer  whoopsie   986433 Apr  8 06:09 
_usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash

  
  rdkit was failing fast and giving up (that will be a different bug, it just 
seems broken on my system):
  Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling 
Policy Service.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully called 
chroot.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully dropped 
privileges.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully limited 
resources.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: pthread_create failed: 
Resource temporarily unavailable
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Canary thread running.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Exiting canary thread.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoting known real-time 
threads.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoted 0 threads.
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Main process 
exited, code=exited, status=1/FAILURE
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with 
result 'exit-code'.
  Apr 08 06:10:13 Keschdeichel dbus-daemon[1208]: [system] Activating via 
systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.1176' (uid=121 pid=>
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Start request 
repeated too quickly.
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with 
result 'exit-code'.
  Apr 08 06:10:13 Keschdeichel systemd[1]: Failed to start RealtimeKit 
Scheduling Policy Service.
  Apr 08 06:10:13 Keschdeichel bluetoothd[1729331]: Bluetooth daemon 5.53

  
  But that already was only triggered by a gnome restart that kicked of earlier:

  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Started GNOME Shell on Wayland.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Shell on 
Wayland.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session 
is initialized.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Wayland 
Session.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session 
(session: gnome-login).

  
  X was recycleing before:
  Apr 08 06:09:19 Keschdeichel systemd[10683]: Stopping GNOME Shell on X11...
  ...
  Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (EE) 
systemd-logind: ReleaseControl failed: Unknown object 
'/org/freedesktop/login1/session/_32'.
  Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (II) Server 
terminated successfully (0). Closing log file.

  
  It seems like some 

[Touch-packages] [Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm

2021-06-16 Thread Iain Lane
Thanks! Here's where I think the problem starts:

Ok, let's authenticate to dbus:

Jun 16 08:54:54 alan-hirsute-base-aiamcicscciaelhaktpo systemd[1]: Bus 
bus-api-system: changing state AUTHENTICATING → HELLO
...
Jun 16 08:54:54 alan-hirsute-base-aiamcicscciaelhaktpo systemd[1]: Bus 
bus-api-system: changing state HELLO → RUNNING

Right, systemd thinks it's done it at least. You can see a whole bunch
of messages being returned, the connection is working.

After a while (note this first timestamp jump; is that significant?
looks to be waiting for udev to settle I think so maybe not; could be
snapd related) we decide to do something with a Type=dbus unit:

Jun 16 08:55:25 alan-hirsute-base-aiamcicscciaelhaktpo systemd[1]: Sent message 
type=method_call sender=n/a destination=org.freedesktop.DBus 
path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=AddMatch 
cookie=1511 reply_cookie=0 signature=s error-name=n/a error-message=n/a
Jun 16 08:55:25 alan-hirsute-base-aiamcicscciaelhaktpo systemd[1]: Sent message 
type=method_call sender=n/a destination=org.freedesktop.DBus 
path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=GetNameOwner 
cookie=1512 reply_cookie=0 signature=s error-name=n/a error-message=n/a

And another timestamp jump, waiting for this timeout:

Jun 16 08:55:45 alan-hirsute-base-aiamcicscciaelhaktpo dbus-daemon[711]: 
[system] Connection has not authenticated soon enough, closing it 
(auth_timeout=3ms, elapsed: 45129ms)
Jun 16 08:55:45 alan-hirsute-base-aiamcicscciaelhaktpo systemd[1]: Got message 
type=method_return sender=org.freedesktop.DBus destination=:1.4 path=n/a 
interface=n/a member=n/a cookie=42 reply_cookie=1512 signature=s error-name=n/a 
error-message=n/a

The dbus-daemon didn't think that the connection was authenticated.

The last message AFAICS received on the bus connection was:

Jun 16 08:55:00 alan-hirsute-base-aiamcicscciaelhaktpo systemd[1]: Got message 
type=method_call sender=n/a destination=org.freedesktop.systemd1 
path=/org/freedesktop/systemd1 interface=org.freedesktop.systemd1.Manager 
member=Reload cookie=1 reply_cookie=0 signature=n/a error-name=n/a 
error-message=n/a
Jun 16 08:55:00 alan-hirsute-base-aiamcicscciaelhaktpo systemd[1]: Reloading.

No smoking gun yet, at least not to me. But interesting that the last
thing which happened successfully was reloading. Can we have another go
please, with these changes vs. an upstream clean image?

  - LogLevel=debug in /etc/systemd/system.conf
  - Using the dbus 1.12.20-2ubuntu1+ppa1 from ppa:ci-train-ppa-service/4587. 
This dbus is just the one from impish backported to hirsute with verbose 
debugging turned on.
  
And then attach the full `journalctl -b ` which will 
probably be quite large. :-)

Maybe we'll get some information out of the dbus side to say what it
thinks goes wrong with the connection.

** Please note ** The "connection has not authenticated" string does not
appear in the earlier logs from Christian or Steve. It could be that
there are two bugs here, with similar symptoms that systemd loses its
connection to the system bus.

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

Title:
  dbus timeout-ed during an upgrade, taking services down including gdm

Status in systemd:
  New
Status in accountsservice package in Ubuntu:
  Invalid
Status in dbus package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Invalid
Status in accountsservice source package in Focal:
  Invalid
Status in dbus source package in Focal:
  Incomplete
Status in gnome-shell source package in Focal:
  Invalid
Status in accountsservice source package in Groovy:
  New
Status in dbus source package in Groovy:
  New
Status in gnome-shell source package in Groovy:
  New
Status in accountsservice source package in Hirsute:
  New
Status in dbus source package in Hirsute:
  New
Status in gnome-shell source package in Hirsute:
  New
Status in accountsservice source package in Impish:
  Invalid
Status in dbus source package in Impish:
  Incomplete
Status in gnome-shell source package in Impish:
  Invalid

Bug description:
  This morning I found my computer on the login screen.
  But not the one of the screen log, no a new one - so something must have 
crashed.

  Logging in again confirmed that all apps were gone and the gnome shell
  was brought down what seems like triggered by a background update o
  accountsservice.

  As always things are not perfectly clear :-/
  The following goes *back* in time through my logs one by one.

  Multiple apps crashed at 06:09, but we will find later that this is a follow 
on issue of the underlying gnome/X/... recycling.
  -rw-r-  1 paelzer  whoopsie 52962868 Apr  8 06:09 
_usr_bin_konversation.1000.crash
  -rw-r-  1 paelzer  whoopsie   986433 Apr  8 06:09 
_usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash

  
 

[Touch-packages] [Bug 1931088] Re: boot-and-services tests fails in impish on armhf (248.3)

2021-06-15 Thread Iain Lane
I have added a badtest hint for this version, so that the many packages
blocked by this can become unblocked. But could somebody please take a
look? The hint is only for this version so the issue will come back with
the next systemd upload unless fixed.

(I'll reset systemd to  "New" so that it appears on the rls-incoming
page)

** Tags added: rls-ii-incoming

** Changed in: auto-package-testing
   Status: New => Incomplete

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

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

Title:
  boot-and-services tests fails in impish on armhf (248.3)

Status in Auto Package Testing:
  Incomplete
Status in dnsmasq package in Ubuntu:
  Incomplete
Status in gdm3 package in Ubuntu:
  Incomplete
Status in glibc package in Ubuntu:
  Incomplete
Status in isc-dhcp package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  New

Bug description:
  Systemd 248.3-1ubuntu1 is rather new, but had 5 successful tests on armhf
  before now slipping into a bad mode.

  Now it seems all tests failed in boot-and-services by hanging until killed by
  VirtSubproc.Timeout of autokgtest.

  The last [1] test log has a bit more, it shows a python stack overflow
  ```
 VirtSubproc.Timeout
 Fatal Python error: Cannot recover from stack overflow.
 Python runtime state: initialized

 Current thread 0x7f108e840740 (most recent call first):
   File "/home/ubuntu/autopkgtest/lib/adtlog.py", line 36 in log
   File "/home/ubuntu/autopkgtest/lib/adtlog.py", line 86 in debug
   File "/home/ubuntu/autopkgtest/lib/adt_testbed.py", line 472 in send
   File "/home/ubuntu/autopkgtest/lib/adt_testbed.py", line 521 in command
  ```

  I have seen a bunch of packages including even gdm3 and glibc being blocked by
  that so I wanted to at least track down the issue until we can put it on
  someones task list to resolve.
  No one replied to my pings yet, but maybe that means someone is already
  debugging this and had enabled some debugging?

  By running the same in armhf container on arm64 VM on canonistack I've seen
  no issues. The test worked fine and had no hang/issues.

  root@systemd-test-fail:~/systemd-248.3# ./debian/tests/boot-and-services
  lxc
  1
  test_profile (__main__.AppArmorTest)
  AppArmor confined unit ... skipped 'fails on armhf testbeds, see LP: #1842352'
  test_help (__main__.CLITest)
  --help works and succeeds ... ok
  test_invalid_option (__main__.CLITest)
  Calling with invalid option fails ... ok
  test_version (__main__.CLITest)
  --version works and succeeds ... ok
  test_cpushares (__main__.CgroupsTest)
  service with CPUShares ... ok
  test_simple (__main__.CgroupsTest)
  simple service ... ok
  test_bash_crash (__main__.CoredumpTest) ... skipped 'systemd-coredump does 
not work in containers'
  test_log_for_service (__main__.JournalTest) ... ok
  test_no_options (__main__.JournalTest) ... ok
  test_boot (__main__.NspawnTest) ... skipped 'nspawn does not work in most 
containers'
  test_service (__main__.NspawnTest) ... skipped 'nspawn does not work in most 
containers'
  test_failing (__main__.SeccompTest) ... ok
  test_0_init (__main__.ServicesTest)
  Verify that init is systemd ... ok
  test_cron (__main__.ServicesTest) ... ok
  test_dbus (__main__.ServicesTest) ... ok
  test_gdm3 (__main__.ServicesTest) ... skipped 'gdm3 not found'
  test_logind (__main__.ServicesTest) ... ok
  test_network_manager (__main__.ServicesTest) ... ok
  test_no_failed (__main__.ServicesTest)
  No failed units ... ok
  test_rsyslog (__main__.ServicesTest) ... ok
  test_tmp_cleanup (__main__.ServicesTest) ... ok
  test_tmp_mount (__main__.ServicesTest) ... ok
  test_udev (__main__.ServicesTest) ... skipped 'udev does not work in 
containers'
  --
  Ran 23 tests in 5.589s
  OK (skipped=6)

  So I can not reproduce this on canonistack, but it blocks autopkgtests of
  various packages pretty reproducibly :-/

  [1]: https://autopkgtest.ubuntu.com/results/autopkgtest-
  impish/impish/armhf/s/systemd/20210604_081326_d4319@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/auto-package-testing/+bug/1931088/+subscriptions

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


[Touch-packages] [Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm

2021-06-15 Thread Iain Lane
That's interesting actually. I thought this was an interaction between
reloading dbus-daemon and daemon-reloading systems at the same time. But
in this cloud case, I don't think dbus is being reloaded, is it?

It's going to be next to impossible for me to look into this in detail
without being able to reproduce it or getting a bit more debug
information.

Maybe you could crank up the system log level and try to reproduce this?

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

Title:
  dbus timeout-ed during an upgrade, taking services down including gdm

Status in systemd:
  New
Status in accountsservice package in Ubuntu:
  Invalid
Status in dbus package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Invalid
Status in accountsservice source package in Focal:
  Invalid
Status in dbus source package in Focal:
  Incomplete
Status in gnome-shell source package in Focal:
  Invalid

Bug description:
  This morning I found my computer on the login screen.
  But not the one of the screen log, no a new one - so something must have 
crashed.

  Logging in again confirmed that all apps were gone and the gnome shell
  was brought down what seems like triggered by a background update o
  accountsservice.

  As always things are not perfectly clear :-/
  The following goes *back* in time through my logs one by one.

  Multiple apps crashed at 06:09, but we will find later that this is a follow 
on issue of the underlying gnome/X/... recycling.
  -rw-r-  1 paelzer  whoopsie 52962868 Apr  8 06:09 
_usr_bin_konversation.1000.crash
  -rw-r-  1 paelzer  whoopsie   986433 Apr  8 06:09 
_usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash

  
  rdkit was failing fast and giving up (that will be a different bug, it just 
seems broken on my system):
  Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling 
Policy Service.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully called 
chroot.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully dropped 
privileges.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully limited 
resources.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: pthread_create failed: 
Resource temporarily unavailable
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Canary thread running.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Exiting canary thread.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoting known real-time 
threads.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoted 0 threads.
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Main process 
exited, code=exited, status=1/FAILURE
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with 
result 'exit-code'.
  Apr 08 06:10:13 Keschdeichel dbus-daemon[1208]: [system] Activating via 
systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.1176' (uid=121 pid=>
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Start request 
repeated too quickly.
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with 
result 'exit-code'.
  Apr 08 06:10:13 Keschdeichel systemd[1]: Failed to start RealtimeKit 
Scheduling Policy Service.
  Apr 08 06:10:13 Keschdeichel bluetoothd[1729331]: Bluetooth daemon 5.53

  
  But that already was only triggered by a gnome restart that kicked of earlier:

  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Started GNOME Shell on Wayland.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Shell on 
Wayland.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session 
is initialized.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Wayland 
Session.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session 
(session: gnome-login).

  
  X was recycleing before:
  Apr 08 06:09:19 Keschdeichel systemd[10683]: Stopping GNOME Shell on X11...
  ...
  Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (EE) 
systemd-logind: ReleaseControl failed: Unknown object 
'/org/freedesktop/login1/session/_32'.
  Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (II) Server 
terminated successfully (0). Closing log file.

  
  It seems like some internal service broke and everything that followed was a 
secondary issue to that:
  Apr 08 06:09:19 Keschdeichel systemd[1]: NetworkManager.service: Unexpected 
error response from GetNameOwner(): Connection terminated
  Apr 08 06:09:19 Keschdeichel systemd[1]: wpa_supplicant.service: Unexpected 
error response from GetNameOwner(): Connection terminated
  Apr 08 06:09:19 Keschdeichel systemd[1]: thermald.service: Unexpected error 
response from GetNameOwner(): Connection terminated
  Apr 08 06:09:19 Keschdeichel thermald[1256]: 

[Touch-packages] [Bug 1931088] Re: boot-and-services tests fails in impish on armhf (248.3)

2021-06-10 Thread Iain Lane
Just to put the information on the bug, I reproduced this failure on a
Raspberry Pi, not a piece of the Scalingstack infrastructure in sight
;-)

As far as I can tell it looked as if it's timing out waiting for
network-online.target to become active. It seems as if installing
network-manager makes the target take way longer to activate, so long
that it is over autopkgtest's timeout. I suppose this isn't expected, so
maybe the next step is to look into why that happens?

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

Title:
  boot-and-services tests fails in impish on armhf (248.3)

Status in Auto Package Testing:
  New
Status in dnsmasq package in Ubuntu:
  Incomplete
Status in gdm3 package in Ubuntu:
  Incomplete
Status in glibc package in Ubuntu:
  Incomplete
Status in isc-dhcp package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Systemd 248.3-1ubuntu1 is rather new, but had 5 successful tests on armhf
  before now slipping into a bad mode.

  Now it seems all tests failed in boot-and-services by hanging until killed by
  VirtSubproc.Timeout of autokgtest.

  The last [1] test log has a bit more, it shows a python stack overflow
  ```
 VirtSubproc.Timeout
 Fatal Python error: Cannot recover from stack overflow.
 Python runtime state: initialized

 Current thread 0x7f108e840740 (most recent call first):
   File "/home/ubuntu/autopkgtest/lib/adtlog.py", line 36 in log
   File "/home/ubuntu/autopkgtest/lib/adtlog.py", line 86 in debug
   File "/home/ubuntu/autopkgtest/lib/adt_testbed.py", line 472 in send
   File "/home/ubuntu/autopkgtest/lib/adt_testbed.py", line 521 in command
  ```

  I have seen a bunch of packages including even gdm3 and glibc being blocked by
  that so I wanted to at least track down the issue until we can put it on
  someones task list to resolve.
  No one replied to my pings yet, but maybe that means someone is already
  debugging this and had enabled some debugging?

  By running the same in armhf container on arm64 VM on canonistack I've seen
  no issues. The test worked fine and had no hang/issues.

  root@systemd-test-fail:~/systemd-248.3# ./debian/tests/boot-and-services
  lxc
  1
  test_profile (__main__.AppArmorTest)
  AppArmor confined unit ... skipped 'fails on armhf testbeds, see LP: #1842352'
  test_help (__main__.CLITest)
  --help works and succeeds ... ok
  test_invalid_option (__main__.CLITest)
  Calling with invalid option fails ... ok
  test_version (__main__.CLITest)
  --version works and succeeds ... ok
  test_cpushares (__main__.CgroupsTest)
  service with CPUShares ... ok
  test_simple (__main__.CgroupsTest)
  simple service ... ok
  test_bash_crash (__main__.CoredumpTest) ... skipped 'systemd-coredump does 
not work in containers'
  test_log_for_service (__main__.JournalTest) ... ok
  test_no_options (__main__.JournalTest) ... ok
  test_boot (__main__.NspawnTest) ... skipped 'nspawn does not work in most 
containers'
  test_service (__main__.NspawnTest) ... skipped 'nspawn does not work in most 
containers'
  test_failing (__main__.SeccompTest) ... ok
  test_0_init (__main__.ServicesTest)
  Verify that init is systemd ... ok
  test_cron (__main__.ServicesTest) ... ok
  test_dbus (__main__.ServicesTest) ... ok
  test_gdm3 (__main__.ServicesTest) ... skipped 'gdm3 not found'
  test_logind (__main__.ServicesTest) ... ok
  test_network_manager (__main__.ServicesTest) ... ok
  test_no_failed (__main__.ServicesTest)
  No failed units ... ok
  test_rsyslog (__main__.ServicesTest) ... ok
  test_tmp_cleanup (__main__.ServicesTest) ... ok
  test_tmp_mount (__main__.ServicesTest) ... ok
  test_udev (__main__.ServicesTest) ... skipped 'udev does not work in 
containers'
  --
  Ran 23 tests in 5.589s
  OK (skipped=6)

  So I can not reproduce this on canonistack, but it blocks autopkgtests of
  various packages pretty reproducibly :-/

  [1]: https://autopkgtest.ubuntu.com/results/autopkgtest-
  impish/impish/armhf/s/systemd/20210604_081326_d4319@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/auto-package-testing/+bug/1931088/+subscriptions

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


[Touch-packages] [Bug 1928001] Re: [SRU] New stable release 2.68.1

2021-05-19 Thread Iain Lane
I ran the applications listed in the description against
2.68.1-1~ubuntu21.04.1. I also generally exercised the desktop for a
while and didn't notice anything odd.

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

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

Title:
  [SRU] New stable release 2.68.1

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Hirsute:
  Fix Committed

Bug description:
  [ Description ]

  Take this new upstream stable release.

  * Fix a crash in `GKeyFile` when parsing a file which contains translations
using a `GKeyFile` instance which has loaded another file previously (#2361)

  * Pin GIO DLL in memory on Windows (!2016)

  * Bugs fixed:
   - #2361 g_key_file_load_from_file segfaults on "Key[*]="like lines
   - !1997 Backport !1996 “Include glibconfig.h to get the G_OS_UNIX token” to 
glib-2-68
   - !2016 GIO W32: Pin gio DLL
   - !2021 Backport MR !2016 (GIO W32: Pin gio DLL) into glib-2-68
   - !2022 Few fixes and notes for building on Visual Studio 2012 and earlier
   - !2034 Backport MR !2032 (gkeyfile: Drop a redundant check) into glib-2-68
   - !2035 Backport !2026 “Split g_test_log() messages that contain multiple 
lines” to glib-2-68

  [ QA ]

  Upstream release, so QA already performed by maintainers

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

  This upload will trigger many autopkgtests that we expect to not be
  regressed by this upload.

  [ What could go wrong ]

  This update contains fixes in multiple places so multiple apps could
  be affected. The consequences of a broken GLib can range from some
  functions returning bad results sometimes, which have minimal runtime
  implications, up to the system simply crashing all the time.

  Pretty much all parts of GNOME use GLib, so test anything in the
  desktop that you can. If you reboot the machine and can get to the
  desktop, that's already tested GLib extensively. But also run
  applications like GNOME terminal, Files and Epiphany.

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

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


[Touch-packages] [Bug 1928931] [NEW] German strings in deja-dup.mo for en_GB

2021-05-19 Thread Iain Lane
Public bug reported:

[ Description ]

Some German strings were accidentally translated under en_GB. They
affect the default Ubuntu install - some of them are strings which are
displayed as a notification some time after first logging in, so it's
quite visible. See the attached screenshot.

[ Fix ]

Revert the German and go back to the proper English text. The way to fix
langpacks is to upload the language-pack-gnome-XX package which replaces
files in language-pack-gnome-XX-base.

[ Devel release ]

I'd like to propose to binary copy forward, and let the normal langpack
release schedule take care of eventually dominating these away in
impish.

[ QA ]

To verify the diff, compare deja-dup.po from language-pack-gnome-en-base
to the one in this upload. You'll have to do that manually.

  0. Be in en_GB.
  1. Install the SRU
  2. In an Ubuntu Desktop session, open a terminal and run `deja-dup --prompt`.
  3. Note the buttons in the notification that shows up. They should be in 
English.

[ What could go wrong ]

1. There could be other instances of this in different packages we haven't 
noticed yet
2. If I break the .po file, it could either break the build or the translations 
at runtime (but this is English, so if we fall back to C it's not too bad)
3. If my diff is wrong then I might have dropped some en_GB translations or 
made them wrong

** Affects: language-pack-gnome-en (Ubuntu)
 Importance: Undecided
 Status: In Progress

** Affects: language-pack-gnome-en (Ubuntu Hirsute)
 Importance: Undecided
 Assignee: Iain Lane (laney)
 Status: In Progress

** Attachment added: "Screenshot from 2021-05-19 09-51-59.png"
   
https://bugs.launchpad.net/bugs/1928931/+attachment/5498717/+files/Screenshot%20from%202021-05-19%2009-51-59.png

** Also affects: language-pack-gnome-en-base (Ubuntu Hirsute)
   Importance: Undecided
   Status: New

** Changed in: language-pack-gnome-en-base (Ubuntu Hirsute)
   Status: New => In Progress

** Changed in: language-pack-gnome-en-base (Ubuntu Hirsute)
 Assignee: (unassigned) => Iain Lane (laney)

** Changed in: language-pack-gnome-en-base (Ubuntu)
 Assignee: (unassigned) => Iain Lane (laney)

** Changed in: language-pack-gnome-en-base (Ubuntu)
   Status: New => In Progress

** Description changed:

  [ Description ]
  
  Some German strings were accidentally translated under en_GB. They
  affect the default Ubuntu install - some of them are strings which are
  displayed as a notification some time after first logging in, so it's
  quite visible. See the attached screenshot.
  
  [ Fix ]
  
  Revert the German and go back to the proper English text. The way to fix
  langpacks is to upload the language-pack-gnome-XX package which replaces
  files in language-pack-gnome-XX-base.
  
  [ Devel release ]
  
  I'd like to propose to binary copy forward, and let the normal langpack
  release schedule take care of eventually dominating these away in
  impish.
  
  [ QA ]
  
  To verify the diff, compare deja-dup.po from language-pack-gnome-en-base
  to the one in this upload. You'll have to do that manually.
  
-   0. Be in en_GB.
-   1. Install the SRU
-   2. In an Ubuntu Desktop session, open a terminal and run `deja-dup 
--prompt`.
-   3. Note the buttons in the notification that shows up. They should be in 
English.
+   0. Be in en_GB.
+   1. Install the SRU
+   2. In an Ubuntu Desktop session, open a terminal and run `deja-dup 
--prompt`.
+   3. Note the buttons in the notification that shows up. They should be in 
English.
  
  [ What could go wrong ]
  
- 1. I could have missed some strings, and so there might still be some Deutsch 
around
- 2. There could be other instances of this in different packages we haven't 
noticed yet
- 3. If I break the .po file, it could either break the build or the 
translations at runtime (but this is English, so if we fall back to C it's not 
too bad)
+ 1. There could be other instances of this in different packages we haven't 
noticed yet
+ 2. If I break the .po file, it could either break the build or the 
translations at runtime (but this is English, so if we fall back to C it's not 
too bad)

** Description changed:

  [ Description ]
  
  Some German strings were accidentally translated under en_GB. They
  affect the default Ubuntu install - some of them are strings which are
  displayed as a notification some time after first logging in, so it's
  quite visible. See the attached screenshot.
  
  [ Fix ]
  
  Revert the German and go back to the proper English text. The way to fix
  langpacks is to upload the language-pack-gnome-XX package which replaces
  files in language-pack-gnome-XX-base.
  
  [ Devel release ]
  
  I'd like to propose to binary copy forward, and let the normal langpack
  release schedule take care of eventually dominating these away in
  impish.
  
  [ QA ]
  
  To verify the diff, compare deja-dup.po from language-pack-gnome-en-base
  to the one in th

[Touch-packages] [Bug 1928001] Re: [SRU] New stable release 2.68.1

2021-05-18 Thread Iain Lane
automake-1.16> same started happening in impish too - you could cherry-
pick 2b8b44ffc37047231757780952f6290398fb73e2 to the hints maybe?

netplan.io> slyon told me this is known bad and is skipped in other
releases already (upstream) and will be included in the next SRU to
hirsute, if any. could be hinted too?

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

Title:
  [SRU] New stable release 2.68.1

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Hirsute:
  Fix Committed

Bug description:
  [ Description ]

  Take this new upstream stable release.

  * Fix a crash in `GKeyFile` when parsing a file which contains translations
using a `GKeyFile` instance which has loaded another file previously (#2361)

  * Pin GIO DLL in memory on Windows (!2016)

  * Bugs fixed:
   - #2361 g_key_file_load_from_file segfaults on "Key[*]="like lines
   - !1997 Backport !1996 “Include glibconfig.h to get the G_OS_UNIX token” to 
glib-2-68
   - !2016 GIO W32: Pin gio DLL
   - !2021 Backport MR !2016 (GIO W32: Pin gio DLL) into glib-2-68
   - !2022 Few fixes and notes for building on Visual Studio 2012 and earlier
   - !2034 Backport MR !2032 (gkeyfile: Drop a redundant check) into glib-2-68
   - !2035 Backport !2026 “Split g_test_log() messages that contain multiple 
lines” to glib-2-68

  [ QA ]

  Upstream release, so QA already performed by maintainers

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

  This upload will trigger many autopkgtests that we expect to not be
  regressed by this upload.

  [ What could go wrong ]

  This update contains fixes in multiple places so multiple apps could
  be affected. The consequences of a broken GLib can range from some
  functions returning bad results sometimes, which have minimal runtime
  implications, up to the system simply crashing all the time.

  Pretty much all parts of GNOME use GLib, so test anything in the
  desktop that you can. If you reboot the machine and can get to the
  desktop, that's already tested GLib extensively. But also run
  applications like GNOME terminal, Files and Epiphany.

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

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


[Touch-packages] [Bug 1926843] Re: online accounts integration with fb isn't working

2021-05-12 Thread Iain Lane
I retried libgdata and it works now

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

Title:
  online accounts integration with fb isn't working

Status in gnome-online-accounts package in Ubuntu:
  Fix Released
Status in gnome-online-accounts source package in Hirsute:
  Fix Committed

Bug description:
  * Impact

  The online accounts setting are proposing a facebook item which isn't
  working

  * Test case

  Go to settings -> online account, browse the accounts option proposed,
  facebook shouldn't be in the list since it doesn't work.

  * Regression potential

  The change is to disable the facebook provider using the upstream
  provided build option. Check that facebook isn't listed anymore but
  that the other providers still are. Since it's a build option change
  it could fail to build so check for that as well on launchpad.

  Since the facebook service currently doesn't consider gnome-online-
  accounts as a valid client there should be no user with that provider
  configured. Even if there were since the service isn't working they
  would see a functional regression.

  ---

  Hi i tryed to use gnome-control-center online-accounts to make easy
  like windows 10 to login to email or add other login so its more easy
  with ID to use pincode or other ID fingerprint and other.

  But its look its much issue compared with windows 10 with thunderbird,
  firefox, and other program.

  Worst is facebook only little windows with issue with login?

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-online-accounts 3.38.1-1ubuntu1
  Uname: Linux 5.12.0-051200-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  1 19:38:03 2021
  InstallationDate: Installed on 2019-05-07 (725 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: gnome-online-accounts
  UpgradeStatus: Upgraded to hirsute on 2021-04-06 (24 days ago)

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

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


[Touch-packages] [Bug 1928001] [NEW] [SRU] New stable release 2.68.1

2021-05-10 Thread Iain Lane
Public bug reported:

[ Description ]

Take this new upstream stable release.

* Fix a crash in `GKeyFile` when parsing a file which contains translations
  using a `GKeyFile` instance which has loaded another file previously (#2361)

* Pin GIO DLL in memory on Windows (!2016)

* Bugs fixed:
 - #2361 g_key_file_load_from_file segfaults on "Key[*]="like lines
 - !1997 Backport !1996 “Include glibconfig.h to get the G_OS_UNIX token” to 
glib-2-68
 - !2016 GIO W32: Pin gio DLL
 - !2021 Backport MR !2016 (GIO W32: Pin gio DLL) into glib-2-68
 - !2022 Few fixes and notes for building on Visual Studio 2012 and earlier
 - !2034 Backport MR !2032 (gkeyfile: Drop a redundant check) into glib-2-68
 - !2035 Backport !2026 “Split g_test_log() messages that contain multiple 
lines” to glib-2-68

[ QA ]

Upstream release, so QA already performed by maintainers

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

This upload will trigger many autopkgtests that we expect to not be
regressed by this upload.

[ What could go wrong ]

This update contains fixes in multiple places so multiple apps could be
affected. The consequences of a broken GLib can range from some
functions returning bad results sometimes, which have minimal runtime
implications, up to the system simply crashing all the time.

Pretty much all parts of GNOME use GLib, so test anything in the desktop
that you can. If you reboot the machine and can get to the desktop,
that's already tested GLib extensively. But also run applications like
GNOME terminal, Files and Epiphany.

** Affects: glib2.0 (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: glib2.0 (Ubuntu Hirsute)
 Importance: Undecided
 Assignee: Iain Lane (laney)
 Status: In Progress

** Also affects: glib2.0 (Ubuntu Hirsute)
   Importance: Undecided
   Status: New

** Changed in: glib2.0 (Ubuntu)
   Status: New => Fix Released

** Changed in: glib2.0 (Ubuntu Hirsute)
   Status: New => In Progress

** Changed in: glib2.0 (Ubuntu Hirsute)
 Assignee: (unassigned) => Iain Lane (laney)

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

Title:
  [SRU] New stable release 2.68.1

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Hirsute:
  In Progress

Bug description:
  [ Description ]

  Take this new upstream stable release.

  * Fix a crash in `GKeyFile` when parsing a file which contains translations
using a `GKeyFile` instance which has loaded another file previously (#2361)

  * Pin GIO DLL in memory on Windows (!2016)

  * Bugs fixed:
   - #2361 g_key_file_load_from_file segfaults on "Key[*]="like lines
   - !1997 Backport !1996 “Include glibconfig.h to get the G_OS_UNIX token” to 
glib-2-68
   - !2016 GIO W32: Pin gio DLL
   - !2021 Backport MR !2016 (GIO W32: Pin gio DLL) into glib-2-68
   - !2022 Few fixes and notes for building on Visual Studio 2012 and earlier
   - !2034 Backport MR !2032 (gkeyfile: Drop a redundant check) into glib-2-68
   - !2035 Backport !2026 “Split g_test_log() messages that contain multiple 
lines” to glib-2-68

  [ QA ]

  Upstream release, so QA already performed by maintainers

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

  This upload will trigger many autopkgtests that we expect to not be
  regressed by this upload.

  [ What could go wrong ]

  This update contains fixes in multiple places so multiple apps could
  be affected. The consequences of a broken GLib can range from some
  functions returning bad results sometimes, which have minimal runtime
  implications, up to the system simply crashing all the time.

  Pretty much all parts of GNOME use GLib, so test anything in the
  desktop that you can. If you reboot the machine and can get to the
  desktop, that's already tested GLib extensively. But also run
  applications like GNOME terminal, Files and Epiphany.

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

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


[Touch-packages] [Bug 1821415] Re: pkexec fails in a non-graphical environment

2021-04-06 Thread Iain Lane
(but I asked for some input there from an apport maintainer, it could be
better than I did it)

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

Title:
  pkexec fails in a non-graphical environment

Status in PolicyKit:
  New
Status in apport package in Ubuntu:
  Triaged
Status in policykit-1 package in Ubuntu:
  Won't Fix

Bug description:
  The plymouth apport source package hooks wants to gather log files as
  the root user and apport provides a policy kit policy for collecting
  that information. This works fine in a graphical environment but not
  in a non-graphical one.

  N.B. you first need to create a /var/log/plymouth-debug.log file for
  the plymouth apport package hook to actually trigger this.

  ubuntu@disco:~$ ubuntu-bug plymouth

  *** Collecting problem information

  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.
  .. AUTHENTICATING FOR com.ubuntu.apport.root-info ===
  Authentication is required to collect system information for this problem 
report
  Authenticating as: Ubuntu (ubuntu)
  Password: 
  polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   AUTHENTICATION FAILED ===
  Error executing command as another user: Not authorized

  This incident has been reported.

  Subsequently, bug reports from servers will contain less information.

To manage notifications about this bug go to:
https://bugs.launchpad.net/policykit-1/+bug/1821415/+subscriptions

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


[Touch-packages] [Bug 1821415] Re: pkexec fails in a non-graphical environment

2021-04-06 Thread Iain Lane
See the attached branch, it's a fix for this in apport.

** Branch linked: lp:~laney/apport/pkttyagent

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

Title:
  pkexec fails in a non-graphical environment

Status in PolicyKit:
  New
Status in apport package in Ubuntu:
  Triaged
Status in policykit-1 package in Ubuntu:
  Won't Fix

Bug description:
  The plymouth apport source package hooks wants to gather log files as
  the root user and apport provides a policy kit policy for collecting
  that information. This works fine in a graphical environment but not
  in a non-graphical one.

  N.B. you first need to create a /var/log/plymouth-debug.log file for
  the plymouth apport package hook to actually trigger this.

  ubuntu@disco:~$ ubuntu-bug plymouth

  *** Collecting problem information

  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.
  .. AUTHENTICATING FOR com.ubuntu.apport.root-info ===
  Authentication is required to collect system information for this problem 
report
  Authenticating as: Ubuntu (ubuntu)
  Password: 
  polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   AUTHENTICATION FAILED ===
  Error executing command as another user: Not authorized

  This incident has been reported.

  Subsequently, bug reports from servers will contain less information.

To manage notifications about this bug go to:
https://bugs.launchpad.net/policykit-1/+bug/1821415/+subscriptions

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


[Touch-packages] [Bug 1821415] Re: pkexec fails in a non-graphical environment

2021-04-06 Thread Iain Lane
I don't think we would want to carry the proposed patch as a distro
patch. So as long as polkit doesn't have direct support for this, apport
should do as systemd does, and spawn pkttyagent (--fallback) itself.

I'll try quickly now to work on an initial patch for this.

** Changed in: policykit-1 (Ubuntu)
   Status: Triaged => Won't Fix

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

Title:
  pkexec fails in a non-graphical environment

Status in PolicyKit:
  New
Status in apport package in Ubuntu:
  Triaged
Status in policykit-1 package in Ubuntu:
  Won't Fix

Bug description:
  The plymouth apport source package hooks wants to gather log files as
  the root user and apport provides a policy kit policy for collecting
  that information. This works fine in a graphical environment but not
  in a non-graphical one.

  N.B. you first need to create a /var/log/plymouth-debug.log file for
  the plymouth apport package hook to actually trigger this.

  ubuntu@disco:~$ ubuntu-bug plymouth

  *** Collecting problem information

  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.
  .. AUTHENTICATING FOR com.ubuntu.apport.root-info ===
  Authentication is required to collect system information for this problem 
report
  Authenticating as: Ubuntu (ubuntu)
  Password: 
  polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   AUTHENTICATION FAILED ===
  Error executing command as another user: Not authorized

  This incident has been reported.

  Subsequently, bug reports from servers will contain less information.

To manage notifications about this bug go to:
https://bugs.launchpad.net/policykit-1/+bug/1821415/+subscriptions

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


[Touch-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"

2021-04-06 Thread Iain Lane
assigning to timo for better tracking

** Changed in: mesa (Ubuntu Hirsute)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

** Changed in: ubiquity (Ubuntu Hirsute)
   Status: Confirmed => Incomplete

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

Title:
  Ubiquity KDE crash on try/install and from live session with
  "malloc(): unaligned tcache chunk detected"

Status in mesa package in Ubuntu:
  Confirmed
Status in ubiquity package in Ubuntu:
  Incomplete
Status in mesa source package in Hirsute:
  Confirmed
Status in ubiquity source package in Hirsute:
  Incomplete

Bug description:
  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: ubiquity 21.04.11
  ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0
  Uname: Linux 5.11.0-11-generic x86_64
  ApportVersion: 2.20.11-0ubuntu60
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.460
  CurrentDesktop: KDE
  Date: Sun Mar 21 11:53:44 2021
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed 
maybe-ubiquity quiet splash ---
  LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321)
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

  Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try
  install screen) and from the live session is crashing on launch or
  shortly after.

  Cases where the crash can be triggered:

  - Using a Virtualbox VM, where graphics acceleration is handled by mesa with 
LLVMPIPE
  - Start the ISO on real hardware in 'safe graphics mode'

  Cases where the crash is not encountered:
  - Start the ISO on real intel (HD graphics) hardware with full acceleration.

  NOTE: The crash can be avoided by downgrading MESA 21.0.x packages to
  the previous 20.3.4 in hirsute.

  Try/Install crash:

  Screen fails to start, or starts then crashes on any user action. The
  user is presented with:

  "Installation failed - The installer encountered an unrecoverable error.
  A desktop session will now be run so that you may investigate the problem or 
try installing again"

  Live session crash:

  The installer does not start from the desktop icon. Starting ubiquity
  from the terminal results in an "Aborted (core dumped)" message and
  nothing else.

  The crash is most commonly "malloc(): unaligned tcache chunk
  detected", but inevitably from this sort of memory issue can be
  something like "realloc(): invalid next size"

  An example /var/log/installer/debug log from a session where both
  crashes were triggered is below.

   /var/log/installer/debug 

  Ubiquity 21.04.11
  TEXT If more than one person will use this computer, you can set up 
multiple accounts after installation.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT The name it uses when it talks to other computers.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT If more than one person will use this computer, you can set up 
multiple accounts after installation.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT The name it uses when it talks to other computers.
  QSocketNotifier: Invalid socket 17 and type 'Read', disabling...
  QSocketNotifier: Invalid socket 17 and type 'Write', disabling...
  QSocketNotifier: Invalid socket 17 and type 'Exception', disabling...
  Your console font configuration will be updated the next time your system
  boots. If you want to update it now, run 'setupcon' from a virtual console.
  update-initramfs is disabled since running on read-only media
  debconf: DbDriver "passwords" warning: could not open 
/var/cache/debconf/passwords.dat: Permission denied
  munmap_chunk(): invalid pointer
  Ubiquity 21.04.11
  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu'
  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu'
  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu'
  TEXT If more than one person will use this computer, you can set up 
multiple accounts after installation.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT The name it uses when it talks to other computers.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  malloc(): unaligned tcache chunk detected

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

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


[Touch-packages] [Bug 1873895] Re: Regression: block staircase display with side-by-side monitors of different pixel widths

2021-04-06 Thread Iain Lane
This came up on our tracking report for the desktop team, but we're not
clear what is required in libxcb/amdgpu vs. a fix in the WMs themselves.
Can someone clarify please?

** Changed in: libxcb (Ubuntu)
   Status: Confirmed => Incomplete

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

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

** Changed in: xserver-xorg-video-amdgpu (Ubuntu)
   Status: Confirmed => Incomplete

** Changed in: xserver-xorg-video-amdgpu (Ubuntu Focal)
   Status: New => Incomplete

** Changed in: xserver-xorg-video-amdgpu (Ubuntu Groovy)
   Status: New => Incomplete

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

Title:
  Regression: block staircase display with side-by-side monitors of
  different pixel widths

Status in Linux:
  Unknown
Status in libxcb package in Ubuntu:
  Incomplete
Status in xfwm4 package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Incomplete
Status in libxcb source package in Focal:
  Incomplete
Status in xfwm4 source package in Focal:
  In Progress
Status in xserver-xorg-video-amdgpu source package in Focal:
  Incomplete
Status in libxcb source package in Groovy:
  Incomplete
Status in xfwm4 source package in Groovy:
  Fix Released
Status in xserver-xorg-video-amdgpu source package in Groovy:
  Incomplete

Bug description:
  [Impact]

   * This issue affects AMD graphics on Xfwm4 4.14.1.

   * Windows are displayed staggered with a multi-window layout

  [Test Plan]

   * Use AMD graphics drivers

   * Connect a second display at a different resolution

   * Open multiple windows

   * While the issue is present, the windows and desktop will appeared
  staggered

   * Once fixed, they display normally.

  [Where problems could occur]

   * Regression potential should be relatively low, as the release
  between 4.14.1 and 4.14.5 are bug releases.

   * With window managers, some changes could lead to different behavior
  and other broken displays. Non-AMD graphics users should also test for
  regressions.

  [Other Info]
   
   * Please see the Xfwm4 release notes for changes between 4.14.1 and 4.14.5: 
https://gitlab.xfce.org/xfce/xfwm4/-/blob/xfce-4.14/NEWS#L7-44

  [Original Report]

  Update based on further research.

  This only happens when the secondary external display is operating at
  a different pixel width to the internal. In this case eDP is 1920x1080
  whereas the external HDMI-A-0 is natively 1680x1050.

  It is caused by xfwm4's recent switch from using glx to xpresent for
  AMD GPUs.

  The underlying bug is in the AMD driver.

  I was able to reproduce on an external 1920x1200 display only when it
  was set to a non-native 1680x1050 resolution.

  ---
  Two identical Lenovo E495 laptops with 20.04 installed. The problem occurred 
initially on the laptop that is having package upgrades applied regularly.

  With dual monitors and the external monitor placed left or right the
  display has a blocked staircase effect shown in the attached
  photograph, and seems related to

  https://gitlab.freedesktop.org/xorg/driver/xf86-video-
  amdgpu/-/issues/10

  More detailed investigation suggests it only happens when the X
  coordinate of the two monitors is different. The symptom looks like an
  off-by-one error because it appears as if the display is divided into,
  say, 10 rows and 15 columns but the first row has 16 'columns' worth
  of blocks on it and so wraps to the beginning of the 2nd row, and so
  on.

  On the laptop without package upgrades being applied this didn't
  happen. So I upgraded it (314 packages) and restarted and it too sees
  the same problem.

  I suspected libxcomposite1 and downgraded it to 1:0.4.5-0ubuntu1 but
  that didn't solve it.

  I now suspect libxcb but so far haven't been able to prove it.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 
00 [VGA controller])
     Subsystem: Lenovo ThinkPad E595 [17aa:5124]
  InstallationDate: Installed on 2020-04-08 (11 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200408)
  MachineType: LENOVO 20NECTO1WW
  Package: xserver-xorg-video-amdgpu 19.1.0-1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic 
root=/dev/mapper/ELLOE000-rootfs ro acpi_osi=! "acpi_osi=Windows 2016" quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Tags:  focal ubuntu ubuntu
  Uname: Linux 

[Touch-packages] [Bug 1922681] [NEW] manpages are wrong about PATH inheriting from the environment now

2021-04-06 Thread Iain Lane
Public bug reported:

I posted this on bug #1779767 but since that got closed it's probably
going to be lost there.

tl;dr the manpage(s) needs to be fixed for this change as well:

Julian, thanks for the fix. In crontab(5) in cron 3.0pl1-136ubuntu2 the
manpage is now wrong. It says:

> Several environment variables are set up automatically by the cron(8)
daemon. […] PATH is set to "/usr/bin:/bin". HOME, SHELL, and PATH may be
overridden by settings in the crontab […]

and also

> On the Debian GNU/Linux system, cron supports the pam_env module, and
loads the environment specified by /etc/environment and
/etc/security/pam_env.conf. It also reads locale information from
/etc/default/locale. However, the PAM settings do NOT override the
settings described above nor any settings in the crontab file itself.
Note in particular that if you want a PATH other than  "/usr/bin:/bin",
you will need to set it in the crontab file.

These should be fixed I think. There might be other spots that I didn't
notice yet too.

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


** Tags: rls-hh-incoming

** Description changed:

  I posted this on bug #1779767 but since that got closed it's probably
  going to be lost there.
  
  tl;dr the manpage(s) needs to be fixed for this change as well:
  
- Julian, thanks for the fix. In crontab(5) in cron 3.0pl1-136ubuntu2 the 
manpage
- is now wrong. It says:
+ Julian, thanks for the fix. In crontab(5) in cron 3.0pl1-136ubuntu2 the
+ manpage is now wrong. It says:
  
  > Several environment variables are set up automatically by the cron(8)
  daemon. […] PATH is set to "/usr/bin:/bin". HOME, SHELL, and PATH may be
  overridden by settings in the crontab […]
  
  and also
  
  > On the Debian GNU/Linux system, cron supports the pam_env module, and
  loads the environment specified by /etc/environment and
  /etc/security/pam_env.conf. It also reads locale information from
  /etc/default/locale. However, the PAM settings do NOT override the
  settings described above nor any settings in the crontab file itself.
  Note in particular that if you want a PATH other than  "/usr/bin:/bin",
  you will need to set it in the crontab file.
  
  These should be fixed I think. There might be other spots that I didn't
  notice yet too.

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

Title:
  manpages are wrong about PATH inheriting from the environment now

Status in cron package in Ubuntu:
  New

Bug description:
  I posted this on bug #1779767 but since that got closed it's probably
  going to be lost there.

  tl;dr the manpage(s) needs to be fixed for this change as well:

  Julian, thanks for the fix. In crontab(5) in cron 3.0pl1-136ubuntu2
  the manpage is now wrong. It says:

  > Several environment variables are set up automatically by the
  cron(8) daemon. […] PATH is set to "/usr/bin:/bin". HOME, SHELL, and
  PATH may be overridden by settings in the crontab […]

  and also

  > On the Debian GNU/Linux system, cron supports the pam_env module,
  and loads the environment specified by /etc/environment and
  /etc/security/pam_env.conf. It also reads locale information from
  /etc/default/locale. However, the PAM settings do NOT override the
  settings described above nor any settings in the crontab file itself.
  Note in particular that if you want a PATH other than
  "/usr/bin:/bin", you will need to set it in the crontab file.

  These should be fixed I think. There might be other spots that I
  didn't notice yet too.

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

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


[Touch-packages] [Bug 1920601] Re: Frequent test failures caused by networking issues on armhf runners

2021-03-24 Thread Iain Lane
Neat, can someone prepare a merge proposal for that?

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

Title:
  Frequent test failures caused by networking issues on armhf runners

Status in Auto Package Testing:
  Triaged
Status in apt package in Ubuntu:
  New

Bug description:
  Armhf runners have been known to have networking issues for years.

  A test of Focal's glibc SRU in Bileto shows that those issues did not
  go away. The glibc package itself is not expected to cause regression,
  this was just a run to confirm that.

  The test resuts are shown here:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_39a8dbb93caf4ec889f8a1b7f69885db/bileto-4017-excuses/2021-03-20_09:25:01/4017_focal_excuses.html

  Out of the 114 failed tests 58 containst the 'Connection timed out'
  string and only test logs from armhf contain that string:

  $ zgrep -l 'Connection timed out' ~/.cache/ubuntu-archive-tools/focal_*.gz 
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_atk1.0_20210318_182825_daefa.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_axe-demultiplexer_20210318_183430_6b008.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_bacula_20210318_190411_e3ad7.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_dialign-t_20210318_204503_b4d94.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_elisa-player_20210318_211129_9537d.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_fyba_20210318_181755_7731e.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_gcc-7_20210318_02_4d95c.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_gcc-8_20210318_221659_0e69f.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_golang-github-mailru-easyjson_20210318_231917_67888.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_gphoto2_20210318_200015_eb767.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_gtk+3.0_20210318_235412_db3e5.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_ipmitool_20210319_003215_d03da.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_kbibtex_20210319_004639_0ac1a.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_kcptun_20210318_193309_6dcd9.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libcache-memcached-getparserxs-perl_20210319_024051_33029.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libclass-load-xs-perl_20210319_025846_01419.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libconvert-uulib-perl_20210319_034852_21cd1.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libhat-trie_20210319_060826_fd334.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libhtml-tidy5-perl_20210319_070723_05fa8.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libimager-perl_20210319_063314_b19a2.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libipc-sharelite-perl_20210319_072246_0217e.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_liblexical-var-perl_20210319_070235_4c450.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libmarpa-r2-perl_20210319_073731_f7554.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libmemcached-libmemcached-perl_20210319_011004_dbca1.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libnet-ldns-perl_20210319_081224_49912.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libnet-pcap-perl_20210319_081606_4d772.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libparams-util-perl_20210319_084831_74d13.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libperlio-eol-perl_20210319_085645_97c6c.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libperlio-layers-perl_20210319_085937_8bd70.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libsass_20210319_092518_4db37.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libsdl-perl_20210319_095502_00c8c.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libtext-bibtex-perl_20210319_105027_abf4a.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libtext-hunspell-perl_20210319_103326_4a603.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libunix-syslog-perl_20210319_111403_f4374.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libwx-scintilla-perl_20210319_114818_a6aab.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libzstd_20210319_114737_0c4d9.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_mod-gearman_20210319_132205_d41ca.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_mrbayes_20210319_133633_10adb.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_octave-interval_20210319_151509_8348f.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_open-isns_20210319_161741_dffad.gz
  

[Touch-packages] [Bug 1920601] Re: Frequent test failures caused by networking issues on armhf runners

2021-03-24 Thread Iain Lane
I think both things would be fine. It's better to not surface these
problems to end users if we can, which we have a mechanism to do.

If and when apt gets a fix which works, then these retries will
automatically stop happening and we can remove the workarounds.

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

Title:
  Frequent test failures caused by networking issues on armhf runners

Status in Auto Package Testing:
  Triaged
Status in apt package in Ubuntu:
  New

Bug description:
  Armhf runners have been known to have networking issues for years.

  A test of Focal's glibc SRU in Bileto shows that those issues did not
  go away. The glibc package itself is not expected to cause regression,
  this was just a run to confirm that.

  The test resuts are shown here:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_39a8dbb93caf4ec889f8a1b7f69885db/bileto-4017-excuses/2021-03-20_09:25:01/4017_focal_excuses.html

  Out of the 114 failed tests 58 containst the 'Connection timed out'
  string and only test logs from armhf contain that string:

  $ zgrep -l 'Connection timed out' ~/.cache/ubuntu-archive-tools/focal_*.gz 
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_atk1.0_20210318_182825_daefa.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_axe-demultiplexer_20210318_183430_6b008.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_bacula_20210318_190411_e3ad7.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_dialign-t_20210318_204503_b4d94.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_elisa-player_20210318_211129_9537d.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_fyba_20210318_181755_7731e.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_gcc-7_20210318_02_4d95c.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_gcc-8_20210318_221659_0e69f.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_golang-github-mailru-easyjson_20210318_231917_67888.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_gphoto2_20210318_200015_eb767.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_gtk+3.0_20210318_235412_db3e5.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_ipmitool_20210319_003215_d03da.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_kbibtex_20210319_004639_0ac1a.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_kcptun_20210318_193309_6dcd9.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libcache-memcached-getparserxs-perl_20210319_024051_33029.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libclass-load-xs-perl_20210319_025846_01419.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libconvert-uulib-perl_20210319_034852_21cd1.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libhat-trie_20210319_060826_fd334.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libhtml-tidy5-perl_20210319_070723_05fa8.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libimager-perl_20210319_063314_b19a2.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libipc-sharelite-perl_20210319_072246_0217e.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_liblexical-var-perl_20210319_070235_4c450.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libmarpa-r2-perl_20210319_073731_f7554.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libmemcached-libmemcached-perl_20210319_011004_dbca1.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libnet-ldns-perl_20210319_081224_49912.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libnet-pcap-perl_20210319_081606_4d772.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libparams-util-perl_20210319_084831_74d13.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libperlio-eol-perl_20210319_085645_97c6c.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libperlio-layers-perl_20210319_085937_8bd70.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libsass_20210319_092518_4db37.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libsdl-perl_20210319_095502_00c8c.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libtext-bibtex-perl_20210319_105027_abf4a.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libtext-hunspell-perl_20210319_103326_4a603.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libunix-syslog-perl_20210319_111403_f4374.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libwx-scintilla-perl_20210319_114818_a6aab.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libzstd_20210319_114737_0c4d9.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_mod-gearman_20210319_132205_d41ca.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_mrbayes_20210319_133633_10adb.gz
  

[Touch-packages] [Bug 1779767] Re: Default cron PATH does not include /snap/bin

2021-03-16 Thread Iain Lane
Julian, thanks for the fix. In crontab(5) in cron 3.0pl1-136ubuntu2 the manpage
is now wrong. It says:

> Several environment variables are set up automatically by the cron(8) daemon.
> […] PATH is set to "/usr/bin:/bin". HOME, SHELL, and PATH may be overridden
> by settings in the crontab […]

and also

> On the Debian GNU/Linux system, cron supports the pam_env module, and loads
> the environment specified by /etc/environment and /etc/security/pam_env.conf.
> It also reads locale information from /etc/default/locale.  However, the PAM
> settings do NOT override the settings described above nor any settings in the
> crontab file itself.  Note in particular that if you want a PATH other than
> "/usr/bin:/bin", you will need to set it in the crontab file.

These should be fixed I think. There might be other spots that I didn't notice
yet too.

Secondly, as there are now tasks for stable releases, I think the SRU team
needs to be made aware of the implications of SRUing this change. It means that
the default PATH (if not overridden) will be different after applying the
update.  There's a chance that users will then have different copies of
programs found resulting in their cron scripts potentially experiencing
behaviour changes. The benefits of consistency may outweigh the
risks/drawbacks of this behaviour change, but I think it should be considered
carefully when SRUing.

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

Title:
  Default cron PATH does not include /snap/bin

Status in anacron package in Ubuntu:
  Fix Committed
Status in cron package in Ubuntu:
  Fix Committed
Status in anacron source package in Bionic:
  Confirmed
Status in cron source package in Bionic:
  Confirmed
Status in anacron source package in Focal:
  Confirmed
Status in cron source package in Focal:
  Confirmed
Status in anacron source package in Groovy:
  Confirmed
Status in cron source package in Groovy:
  Confirmed
Status in anacron source package in Hirsute:
  Fix Committed
Status in cron source package in Hirsute:
  Fix Committed

Bug description:
  I recently changed from a .deb install of LXD to a snap, and was
  surprised that one of my crontab scripts stopped working.

  I see that $PATH in a cron script only contains "/usr/bin:/bin",
  whereas my default shell also includes "/snap/bin".

  It seems to me that for the best user experience with snaps,
  "/snap/bin" should be part of the default $PATH in cron.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cron 3.0pl1-128.1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_20_21_generic_40 
kpatch_livepatch_Ubuntu_4_15_0_20_21_generic_39 
livepatch_livepatch_Ubuntu_4_15_0_20_21_generic_ zfs zunicode zavl icp zcommon 
znvpair
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul  2 14:30:06 2018
  InstallationDate: Installed on 2017-12-20 (194 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171219)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: cron
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1917763] Re: FFE: new upstream release 21.0 and migrate to llvm 12

2021-03-12 Thread Iain Lane
ACK, go for it (with 11 for now, I agree that switching to an RC
compiler feels dodgy)

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

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

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

Title:
  FFE: new upstream release 21.0 and migrate to llvm 12

Status in mesa package in Ubuntu:
  Triaged

Bug description:
  Mesa 21.0.0 will be released soon, and we still want it in 21.04. It's
  been in Debian experimental since rc1. The packaging also migrates it
  to use llvm 12.

  The risks involve graphical issues or even crashes when running more
  intense OpenGL/Vulkan apps like games. Running a desktop is a simple
  use-case and should work fine across the board. Upstream gitlab has a
  fairly extensive CI for various drivers, while Intel tests on their
  own CI. This means that any showstoppers should be shaken out already.

  We will be able to pull maybe two point-releases before hirsute is
  frozen, and then push more as an SRU.

  I've tested 21.0.0-rc's on Intel and AMD (RX 5700) and the latter too
  with some games, all good.

  packages for hirsute are available on ppa:canonical-x/x-staging

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

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


[Touch-packages] [Bug 1916705] Re: glib2.0 >=2.67.3 breaks include from an extern C context

2021-03-08 Thread Iain Lane
> Also open-vm-tools is also FTBFS by this, so I need to add a task and
work on that as well.

You want this kind of thing minimally to get over the FTBFS:

--- open-vm-tools-11.2.5.orig/open-vm-tools/configure.ac
+++ open-vm-tools-11.2.5/open-vm-tools/configure.ac
@@ -503,6 +503,9 @@ AC_CHECK_PROG([have_genmarshal],
   [yes],
   [no])
 
+AC_DEFINE(GLIB_VERSION_MIN_REQUIRED, GLIB_VERSION_2_34, [Ignore post 2.34 
deprecations])
+AC_DEFINE(GLIB_VERSION_MAX_ALLOWED, GLIB_VERSION_2_34, [Prevent post 2.34 
APIs])
+
 if test "$have_genmarshal" != "yes"; then
AC_MSG_ERROR([glib-genmarshal is required; make sure it is available in 
your path.])
 fi

But I would recommend also at least asking upstream to do the full fix
and move glib's headers out of 'extern "C"' too as outlined in comment
#2 here.

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

Title:
  glib2.0 >=2.67.3 breaks include from an extern C context

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in open-vm-tools package in Ubuntu:
  New
Status in qemu package in Ubuntu:
  Fix Released
Status in ukui-control-center package in Ubuntu:
  Triaged

Bug description:
  qemu now breaks in Hirsute (it didn't 23h ago)
  Broken:
  
https://launchpadlibrarian.net/524654684/buildlog_ubuntu-hirsute-amd64.qemu_1%3A5.2+dfsg-6ubuntu1_BUILDING.txt.gz

  Good before:
  https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4471/+packages

  Error:

  ../../disas/arm-a64.cc
  In file included from /usr/include/glib-2.0/glib/gmacros.h:241,
   from 
/usr/lib/x86_64-linux-gnu/glib-2.0/include/glibconfig.h:9,
   from /usr/include/glib-2.0/glib/gtypes.h:32,
   from /usr/include/glib-2.0/glib/galloca.h:32,
   from /usr/include/glib-2.0/glib.h:30,
   from /<>/qemu-5.2+dfsg/include/glib-compat.h:32,
   from /<>/qemu-5.2+dfsg/include/qemu/osdep.h:126,
   from ../../disas/arm-a64.cc:21:
  /usr/include/c++/10/type_traits:56:3: error: template with C linkage
     56 |   template
    |   ^~~~
  ../../disas/arm-a64.cc:20:1: note: ‘extern "C"’ linkage started here
     20 | extern "C" {
    | ^~

  Also in disas/nanomips.cpp, ...

  And indeed disas/arm-a64.cc has:
   20 extern "C" {
   21 #include "qemu/osdep.h"
   22 #include "disas/dis-asm.h"
   23 }

  Through the chain of headers as reported above this gets to the templates
  in /usr/include/c++/10/type_traits which fails due to that.

  So C++ constructs within a C scope which is this bug.

  Upstream qemu has not recently changed yet for this.
  The code is the same since 2016 via commit e78490c44: "disas/arm-a64.cc:
  Include osdep.h first" by Peter Maydell.

  But what was different before to break it now?
  To find that I was comparing Hirsute vs Hirsute-proposed ...

  It is indeed failing in -proposed but working in hirsute-release.

  10.2.1-20ubuntu1 : bad

  repro in broken build:
  $ cd /root/qemu-5.2+dfsg/b/qemu
  $ c++ -Ilibcommon.fa.p -I. -I../.. -Iqapi -Itrace -Iui -Iui/shader 
-I/usr/include/pixman-1 -I/usr/include/virgl -I/usr/include/libpng16 
-I/usr/include/spice-server -I/usr/include/spice-1 -I/usr/include/libusb-1.0 
-I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/gio-unix-2.0 
-I/usr/include/cacard -I/usr/include/nss -I/usr/include/nspr 
-I/usr/include/PCSC -I/usr/include/slirp -fdiagnostics-color=auto -pipe -Wall 
-Winvalid-pch -Wnon-virtual-dtor -std=gnu++11 -O2 -g -D__STDC_LIMIT_MACROS 
-D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -U_FORTIFY_SOURCE -m64 -mcx16 
-D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wundef 
-Wwrite-strings -fno-strict-aliasing -fno-common -fwrapv -g -O2 
-ffile-prefix-map=/root/qemu-5.2+dfsg=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wtype-limits 
-Wformat-security -Wformat-y2k -Winit-self -Wignored-qualifiers -Wempty-body 
-Wendif-labels -Wexpansion-to-defined -Wno-missing-include-dirs 
-Wno-shift-negative-value -Wno-psabi -fstack-protector-strong -isystem 
/root/qemu-5.2+dfsg/linux-headers -isystem linux-headers -iquote 
/root/qemu-5.2+dfsg/tcg/i386 -iquote . -iquote /root/qemu-5.2+dfsg -iquote 
/root/qemu-5.2+dfsg/accel/tcg -iquote /root/qemu-5.2+dfsg/include -iquote 
/root/qemu-5.2+dfsg/disas/libvixl -pthread -fPIE -DSTRUCT_IOVEC_DEFINED 
-D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600 -DNCURSES_WIDECHAR -MD -MQ 
libcommon.fa.p/disas_nanomips.cpp.o -MF libcommon.fa.p/disas_nanomips.cpp.o.d 
-o libcommon.fa.p/disas_nanomips.cpp.o -c ../../disas/nanomips.cpp

  With that I have a test env...

  Doko asked me to test
  
https://launchpad.net/ubuntu/+source/gcc-10/10.2.1-19ubuntu1/+build/20995220/+files/g++-10_10.2.1-19ubuntu1_amd64.deb
  That 

[Touch-packages] [Bug 1916701] Re: [glib2.0 2.67.4-1] Black screen on boot, login screen missing/delayed, eventually comes up without Wayland support (only Xorg sessions offered)

2021-03-01 Thread Iain Lane
** Changed in: glib2.0 (Ubuntu)
 Assignee: Marco Trevisan (Treviño) (3v1n0) => Iain Lane (laney)

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

Title:
  [glib2.0 2.67.4-1] Black screen on boot, login screen missing/delayed,
  eventually comes up without Wayland support (only Xorg sessions
  offered)

Status in GLib:
  Unknown
Status in glib2.0 package in Ubuntu:
  Fix Committed

Bug description:
  When I installed the glib2.0 2.67.4-1 packages I consistently
  encountered a black screen on boot. The login screen was
  missing/delayed but eventually comes up without Wayland support (only
  Xorg sessions offered).

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

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


[Touch-packages] [Bug 1916705] Re: glib2.0 >=2.67.3 breaks include from an extern C context

2021-03-01 Thread Iain Lane
I'm going to close this bug in the 2.67.5-1 upload which I'm just making
to experimental. There will still be "some" projects still affected, but
it's as fixed as it's going to get from glib2.0's side - we made the API
break opt in for packages that have followed glib's longstanding advice
and defined the MAX_ALLOWED/MIN_REQUIRED macros.

Affected projects can do either (but should do both) of these.

  - Define GLIB_VERSION_MAX_ALLOWED to something below GLIB_VERISON_2_66 to opt 
out or _2_68 to opt in to this new typesafe behaviour.
  - Not include glib's headers in an 'extern "C"' context. GLib has 
G_{BEGIN,END}_DECLS that might help with this.

** Changed in: glib2.0 (Ubuntu)
   Status: New => In Progress

** Changed in: glib2.0 (Ubuntu)
 Assignee: (unassigned) => Iain Lane (laney)

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

Title:
  glib2.0 >=2.67.3 breaks include from an extern C context

Status in glib2.0 package in Ubuntu:
  In Progress
Status in qemu package in Ubuntu:
  Triaged
Status in ukui-control-center package in Ubuntu:
  New

Bug description:
  qemu now breaks in Hirsute (it didn't 23h ago)
  Broken:
  
https://launchpadlibrarian.net/524654684/buildlog_ubuntu-hirsute-amd64.qemu_1%3A5.2+dfsg-6ubuntu1_BUILDING.txt.gz

  Good before:
  https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4471/+packages

  Error:

  ../../disas/arm-a64.cc
  In file included from /usr/include/glib-2.0/glib/gmacros.h:241,
   from 
/usr/lib/x86_64-linux-gnu/glib-2.0/include/glibconfig.h:9,
   from /usr/include/glib-2.0/glib/gtypes.h:32,
   from /usr/include/glib-2.0/glib/galloca.h:32,
   from /usr/include/glib-2.0/glib.h:30,
   from /<>/qemu-5.2+dfsg/include/glib-compat.h:32,
   from /<>/qemu-5.2+dfsg/include/qemu/osdep.h:126,
   from ../../disas/arm-a64.cc:21:
  /usr/include/c++/10/type_traits:56:3: error: template with C linkage
     56 |   template
    |   ^~~~
  ../../disas/arm-a64.cc:20:1: note: ‘extern "C"’ linkage started here
     20 | extern "C" {
    | ^~

  Also in disas/nanomips.cpp, ...

  And indeed disas/arm-a64.cc has:
   20 extern "C" {
   21 #include "qemu/osdep.h"
   22 #include "disas/dis-asm.h"
   23 }

  Through the chain of headers as reported above this gets to the templates
  in /usr/include/c++/10/type_traits which fails due to that.

  So C++ constructs within a C scope which is this bug.

  Upstream qemu has not recently changed yet for this.
  The code is the same since 2016 via commit e78490c44: "disas/arm-a64.cc:
  Include osdep.h first" by Peter Maydell.

  But what was different before to break it now?
  To find that I was comparing Hirsute vs Hirsute-proposed ...

  It is indeed failing in -proposed but working in hirsute-release.

  10.2.1-20ubuntu1 : bad

  repro in broken build:
  $ cd /root/qemu-5.2+dfsg/b/qemu
  $ c++ -Ilibcommon.fa.p -I. -I../.. -Iqapi -Itrace -Iui -Iui/shader 
-I/usr/include/pixman-1 -I/usr/include/virgl -I/usr/include/libpng16 
-I/usr/include/spice-server -I/usr/include/spice-1 -I/usr/include/libusb-1.0 
-I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/gio-unix-2.0 
-I/usr/include/cacard -I/usr/include/nss -I/usr/include/nspr 
-I/usr/include/PCSC -I/usr/include/slirp -fdiagnostics-color=auto -pipe -Wall 
-Winvalid-pch -Wnon-virtual-dtor -std=gnu++11 -O2 -g -D__STDC_LIMIT_MACROS 
-D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -U_FORTIFY_SOURCE -m64 -mcx16 
-D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wundef 
-Wwrite-strings -fno-strict-aliasing -fno-common -fwrapv -g -O2 
-ffile-prefix-map=/root/qemu-5.2+dfsg=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wtype-limits 
-Wformat-security -Wformat-y2k -Winit-self -Wignored-qualifiers -Wempty-body 
-Wendif-labels -Wexpansion-to-defined -Wno-missing-include-dirs 
-Wno-shift-negative-value -Wno-psabi -fstack-protector-strong -isystem 
/root/qemu-5.2+dfsg/linux-headers -isystem linux-headers -iquote 
/root/qemu-5.2+dfsg/tcg/i386 -iquote . -iquote /root/qemu-5.2+dfsg -iquote 
/root/qemu-5.2+dfsg/accel/tcg -iquote /root/qemu-5.2+dfsg/include -iquote 
/root/qemu-5.2+dfsg/disas/libvixl -pthread -fPIE -DSTRUCT_IOVEC_DEFINED 
-D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600 -DNCURSES_WIDECHAR -MD -MQ 
libcommon.fa.p/disas_nanomips.cpp.o -MF libcommon.fa.p/disas_nanomips.cpp.o.d 
-o libcommon.fa.p/disas_nanomips.cpp.o -c ../../disas/nanomips.cpp

  With that I have a test env...

  Doko asked me to test
  
https://launchpad.net/ubuntu/+source/gcc-10/10.2.1-19ubuntu1/+build/20995220/+files/g++-10_10.2.1

[Touch-packages] [Bug 1915126] Re: autopkgtest times out (or fails before that) in hirsute on test infra, passes locally

2021-02-24 Thread Iain Lane
Sorry for not replying to comment #11, although we chatted on IRC.

The main difference is the passing of the test name I think, but the
full autopkgtest command that I used is at the top of the log. I hope
using this exact command and adding --shell-fail is enough for anyone to
reproduce.

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

Title:
  autopkgtest times out (or fails before that) in hirsute on test infra,
  passes locally

Status in Auto Package Testing:
  Incomplete
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Hi,
  I've asked yesterday on IRC but so far got no answer. I think it is right to 
file a bug about the current state of systemd autopkgtest to unite the efforts 
in regard to it.

  I was looking at the systemd tests for a no-change rebuild that really
  had no reason to now make it fail. While checking I found that as of
  this month (first bad test on 1st of February) most of the systemd
  test runs on amd64 will not pass/fail but instead in most cases time
  out.

  I've seen various people retry the case as it shows the typical
  symptoms of a "not the fault of the package, let us retry this" case.
  But it seems that won't help as the test history is rather clear.

  
  * Watch this in monospace to make more sense of it *

  $ check-autopkgtest-stats.sh -c 50 -p systemd -r "hirsute" -a "amd64"
  Check last 50 test results for src:systemd on releases 'hirsute' on 
architectures 'amd64'
  Of the 50 last tests, we had these subtest failing per release/arch:

  hirsute
amd64
  tests-in-lxd   (F  2% f  0% S  0% B 12% => P 52%/) 
.BTTTBTT.BTBTTTBBTTT..F..
  hostnamed  (F  0% f  0% S  0% B 12% => P 54%/) 
.BTTTBTT.BTBTTTBBTTT.
  build-login(F  0% f  0% S  0% B 12% => P 54%/) 
.BTTTBTT.BTBTTTBBTTT.
  unit-config(F  0% f  0% S  0% B 12% => P 54%/) 
.BTTTBTT.BTBTTTBBTTT.
  networkd-testpy(F  0% f  0% S  0% B 12% => P 54%/) 
.BTTTBTT.BTBTTTBBTTT.
  localed-locale (F  0% f  0% S  0% B 12% => P 54%/) 
.BTTTBTT.BTBTTTBBTTT.
  boot-and-services  (F  4% f  0% S  0% B 12% => P 50%/) 
.BTTTBTT.BTBTTTBBTTT...F.F...
  timedated  (F  0% f  0% S  0% B 12% => P 54%/) 
.BTTTBTT.BTBTTTBBTTT.
  boot-smoke (F  0% f  0% S  0% B 12% => P 54%/) 
.BTTTBTT.BTBTTTBBTTT.
  logind (F  0% f  0% S  0% B 12% => P 54%/) 
.BTTTBTT.BTBTTTBBTTT.
  storage(F  0% f  0% S  0% B 12% => P 54%/) 
.BTTTBTT.BTBTTTBBTTT.
  upstream   (F 12% f  0% S  0% B 12% => P 42%/) 
.BTTTBTT.BTBTTTBBTTTF.F.F..FF..F.
  udev   (F  0% f  0% S  0% B 12% => P 54%/) 
.BTTTBTT.BTBTTTBBTTT.
  systemd-fsckd  (F  8% f  0% S  0% B 12% => P 46%/) 
FBTTTBTTFBTBTTTBBTTT.F..F
  root-unittests (F  0% f  0% S  0% B 12% => P 54%/) 
.BTTTBTT.BTBTTTBBTTT.
  localed-x11-keymap (F  0% f  0% S  0% B 12% => P 54%/) 
.BTTTBTT.BTBTTTBBTTT.

  We see that formerly we had the known to be somewhat flaky, but
  otherwise working test (time goes from right to left). So we had the
  usual suspects of tests like upstream/systemd-fsck that failed a few
  times, but also working runs in between.

  But since February 22/24 runs failed very bad.
  6 (=B) of those cases are aborting mid execution
autopkgtest [22:08:58]: ERROR: testbed failure: testbed auxverb failed with 
exit code 255
  And 16 of them timed out
: failure: Timed out on waiting for ssh connection

  Sadly the 2/24 that didn't hard fail by that where broken by the known
  flaky systemd-fsckd test.

  Something drives this test crazy that we have to find and resolve, at
  the current rate nothing depending on it is likely to migrate.

To manage notifications about this bug go to:
https://bugs.launchpad.net/auto-package-testing/+bug/1915126/+subscriptions

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


[Touch-packages] [Bug 1915784] Re: Permissions of executables pointing to "buildd"

2021-02-16 Thread Iain Lane
*** This bug is a duplicate of bug 1915250 ***
https://bugs.launchpad.net/bugs/1915250

hi, thanks, the team are already tracking this in bug #1915250 and said
they are working on fixing everything

** This bug has been marked a duplicate of bug 1915250
   buildd file owner/group for shared libraries

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

Title:
  Permissions of executables pointing to "buildd"

Status in apport package in Ubuntu:
  New
Status in ccache package in Ubuntu:
  New
Status in fuse3 package in Ubuntu:
  New
Status in lzma package in Ubuntu:
  New
Status in netstat-nat package in Ubuntu:
  New
Status in openssh package in Ubuntu:
  New
Status in pipewire package in Ubuntu:
  New
Status in psensor package in Ubuntu:
  New
Status in screen package in Ubuntu:
  New
Status in snap package in Ubuntu:
  New
Status in sudo package in Ubuntu:
  New
Status in wireshark package in Ubuntu:
  New
Status in xz-utils package in Ubuntu:
  New

Bug description:
  I've noticed this issue already with other applications, which have been 
updated recently, too.
  This morning I've updated the sudo package and it broke, too.

  The common issue is that fakeroot gets omitted or faulty in your build
  environment somehow.

  After looking into the current sudo package I've noticed that all
  files are owned by "buildd:buildd", which doesn't exist on my computer
  and thus the 2001:2501 on my local machine.

  I'll try to collect some other packages, too, which have the same
  problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: sudo 1.9.5p2-2ubuntu1
  ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
  Uname: Linux 5.10.0-14-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu58
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Tue Feb 16 08:33:27 2021
  InstallationDate: Installed on 2020-01-27 (385 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: sudo
  UpgradeStatus: No upgrade log present (probably fresh install)
  VisudoCheck:
   /etc/sudoers: parsed OK
   /etc/sudoers.d/README: parsed OK

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

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


[Touch-packages] [Bug 1915126] Re: autopkgtest times out (or fails before that) in hirsute on test infra, passes locally

2021-02-12 Thread Iain Lane
Ok, here you go. I reproduced the (or a) failure in Canonistack. This
was the first run FWIW, so it wasn't too hard to get it to fail:

autopkgtest [14:05:12]: test systemd-fsckd: [---
test_fsck_failure (__main__.FsckdTest)
Ensure that a failing fsck doesn't prevent fsckd to stop ... bash: line 1:  
1250 Killed  
/tmp/autopkgtest.5SlVJo/build.mmt/src/debian/tests/systemd-fsckd 2> >(tee -a 
/tmp/autopkgtest.5SlVJo/systemd-fsckd-stderr >&2) > >(tee -a 
/tmp/autopkgtest.5SlVJo/systemd-fsckd-stdout)
autopkgtest [14:05:16]: test process requested reboot with marker 
test_fsck_failure
autopkgtest-virt-ssh: WARNING: ssh connection failed. Retrying in 3 seconds...
test_fsck_failure (__main__.FsckdTest)
Ensure that a failing fsck doesn't prevent fsckd to stop ... FAIL

==
FAIL: test_fsck_failure (__main__.FsckdTest)
Ensure that a failing fsck doesn't prevent fsckd to stop
--
Traceback (most recent call last):
  File "/tmp/autopkgtest.5SlVJo/build.mmt/src/debian/tests/systemd-fsckd", line 
190, in test_fsck_failure
self.check_plymouth_start()
  File "/tmp/autopkgtest.5SlVJo/build.mmt/src/debian/tests/systemd-fsckd", line 
158, in check_plymouth_start
self.assertUnitStarted(unit)
  File "/tmp/autopkgtest.5SlVJo/build.mmt/src/debian/tests/systemd-fsckd", line 
228, in assertUnitStarted
self.assertTrue(has_unit_started(unit))
AssertionError: False is not true

--
Ran 1 test in 11.289s

FAILED (failures=1)
autopkgtest [14:06:11]: test systemd-fsckd: ---]
autopkgtest [14:06:12]: test systemd-fsckd:  - - - - - - - - - - results - - - 
- - - - - - -
systemd-fsckdFAIL non-zero exit status 1
autopkgtest [14:06:13]:  summary
timedatedPASS
hostnamedPASS
localed-locale   PASS
localed-x11-keymap   PASS
logind   PASS
unit-config  PASS
storage  PASS
networkd-test.py PASS
build-login  PASS
boot-and-servicesPASS
udev PASS
root-unittests   PASS
tests-in-lxd PASS
upstream PASS
boot-smoke   PASS
systemd-fsckdFAIL non-zero exit status 1

Full logs attached. The commandline is at the top of the log - is that
enough for you to be able to have a go, Balint? I suggest adding
--shell-fail of course so you can break in once it happens.

** Attachment added: "systemd-canonistack-cpu4-ram8-disk50.tar.xz"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1915126/+attachment/5463223/+files/systemd-canonistack-cpu4-ram8-disk50.tar.xz

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

Title:
  autopkgtest times out (or fails before that) in hirsute on test infra,
  passes locally

Status in Auto Package Testing:
  Incomplete
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Hi,
  I've asked yesterday on IRC but so far got no answer. I think it is right to 
file a bug about the current state of systemd autopkgtest to unite the efforts 
in regard to it.

  I was looking at the systemd tests for a no-change rebuild that really
  had no reason to now make it fail. While checking I found that as of
  this month (first bad test on 1st of February) most of the systemd
  test runs on amd64 will not pass/fail but instead in most cases time
  out.

  I've seen various people retry the case as it shows the typical
  symptoms of a "not the fault of the package, let us retry this" case.
  But it seems that won't help as the test history is rather clear.

  
  * Watch this in monospace to make more sense of it *

  $ check-autopkgtest-stats.sh -c 50 -p systemd -r "hirsute" -a "amd64"
  Check last 50 test results for src:systemd on releases 'hirsute' on 
architectures 'amd64'
  Of the 50 last tests, we had these subtest failing per release/arch:

  hirsute
amd64
  tests-in-lxd   (F  2% f  0% S  0% B 12% => P 52%/) 
.BTTTBTT.BTBTTTBBTTT..F..
  hostnamed  (F  0% f  0% S  0% B 12% => P 54%/) 
.BTTTBTT.BTBTTTBBTTT.
  build-login(F  0% f  0% S  0% B 12% => P 54%/) 
.BTTTBTT.BTBTTTBBTTT.
  unit-config(F  0% f  0% S  0% B 12% => P 54%/) 
.BTTTBTT.BTBTTTBBTTT.
  networkd-testpy(F  0% f  0% S  0% B 12% => P 54%/) 
.BTTTBTT.BTBTTTBBTTT.
  localed-locale (F  0% f  0% S  0% B 12% => P 54%/) 
.BTTTBTT.BTBTTTBBTTT.
  boot-and-services  (F  4% f  0% S  0% B 12% => P 50%/) 

[Touch-packages] [Bug 1915126] Re: autopkgtest times out (or fails before that) in hirsute on test infra, passes locally

2021-02-11 Thread Iain Lane
I'm running a test on Canonistack. I'm hoping that this will reproduce
the failures we're seeing, and then they can be investigated.

That is closer to what is running in production than the QEMU runner.

I don't think we have evidence that this is an 'infra issue', so I'm
marking the auto-package-testing task as incomplete.

Will follow back up probably tomorrow once that test is finished.

** Changed in: auto-package-testing
   Status: New => Incomplete

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

Title:
  autopkgtest times out (or fails before that) in hirsute on test infra,
  passes locally

Status in Auto Package Testing:
  Incomplete
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Hi,
  I've asked yesterday on IRC but so far got no answer. I think it is right to 
file a bug about the current state of systemd autopkgtest to unite the efforts 
in regard to it.

  I was looking at the systemd tests for a no-change rebuild that really
  had no reason to now make it fail. While checking I found that as of
  this month (first bad test on 1st of February) most of the systemd
  test runs on amd64 will not pass/fail but instead in most cases time
  out.

  I've seen various people retry the case as it shows the typical
  symptoms of a "not the fault of the package, let us retry this" case.
  But it seems that won't help as the test history is rather clear.

  
  * Watch this in monospace to make more sense of it *

  $ check-autopkgtest-stats.sh -c 50 -p systemd -r "hirsute" -a "amd64"
  Check last 50 test results for src:systemd on releases 'hirsute' on 
architectures 'amd64'
  Of the 50 last tests, we had these subtest failing per release/arch:

  hirsute
amd64
  tests-in-lxd   (F  2% f  0% S  0% B 12% => P 52%/) 
.BTTTBTT.BTBTTTBBTTT..F..
  hostnamed  (F  0% f  0% S  0% B 12% => P 54%/) 
.BTTTBTT.BTBTTTBBTTT.
  build-login(F  0% f  0% S  0% B 12% => P 54%/) 
.BTTTBTT.BTBTTTBBTTT.
  unit-config(F  0% f  0% S  0% B 12% => P 54%/) 
.BTTTBTT.BTBTTTBBTTT.
  networkd-testpy(F  0% f  0% S  0% B 12% => P 54%/) 
.BTTTBTT.BTBTTTBBTTT.
  localed-locale (F  0% f  0% S  0% B 12% => P 54%/) 
.BTTTBTT.BTBTTTBBTTT.
  boot-and-services  (F  4% f  0% S  0% B 12% => P 50%/) 
.BTTTBTT.BTBTTTBBTTT...F.F...
  timedated  (F  0% f  0% S  0% B 12% => P 54%/) 
.BTTTBTT.BTBTTTBBTTT.
  boot-smoke (F  0% f  0% S  0% B 12% => P 54%/) 
.BTTTBTT.BTBTTTBBTTT.
  logind (F  0% f  0% S  0% B 12% => P 54%/) 
.BTTTBTT.BTBTTTBBTTT.
  storage(F  0% f  0% S  0% B 12% => P 54%/) 
.BTTTBTT.BTBTTTBBTTT.
  upstream   (F 12% f  0% S  0% B 12% => P 42%/) 
.BTTTBTT.BTBTTTBBTTTF.F.F..FF..F.
  udev   (F  0% f  0% S  0% B 12% => P 54%/) 
.BTTTBTT.BTBTTTBBTTT.
  systemd-fsckd  (F  8% f  0% S  0% B 12% => P 46%/) 
FBTTTBTTFBTBTTTBBTTT.F..F
  root-unittests (F  0% f  0% S  0% B 12% => P 54%/) 
.BTTTBTT.BTBTTTBBTTT.
  localed-x11-keymap (F  0% f  0% S  0% B 12% => P 54%/) 
.BTTTBTT.BTBTTTBBTTT.

  We see that formerly we had the known to be somewhat flaky, but
  otherwise working test (time goes from right to left). So we had the
  usual suspects of tests like upstream/systemd-fsck that failed a few
  times, but also working runs in between.

  But since February 22/24 runs failed very bad.
  6 (=B) of those cases are aborting mid execution
autopkgtest [22:08:58]: ERROR: testbed failure: testbed auxverb failed with 
exit code 255
  And 16 of them timed out
: failure: Timed out on waiting for ssh connection

  Sadly the 2/24 that didn't hard fail by that where broken by the known
  flaky systemd-fsckd test.

  Something drives this test crazy that we have to find and resolve, at
  the current rate nothing depending on it is likely to migrate.

To manage notifications about this bug go to:
https://bugs.launchpad.net/auto-package-testing/+bug/1915126/+subscriptions

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


Re: [Touch-packages] [Bug 1915126] Re: autopkgtest times out (or fails before that) in hirsute on test infra, passes locally

2021-02-11 Thread Iain Lane
On Thu, Feb 11, 2021 at 01:49:45PM -, Balint Reczey wrote:
> There is not much to do about the failures on systemd's side. The tests
> are reliably passing in qemu on my i5-4670 testbed from 2013, also
> passing on @paelzer's presumably newer machine.
> 
> This is an infra issue. The Release Team can decide if they want to hint
> the test and lose gating coverage, but I'm not filing the hint because
> IMO the test infra should be fixed.

Is there chance we can be a little bit more constructive? We're not 
warring factions here.

-- 
Iain Lane  [ i...@orangesquash.org.uk ]
Debian Developer   [ la...@debian.org ]
Ubuntu Developer   [ la...@ubuntu.com ]

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

Title:
  autopkgtest times out (or fails before that) in hirsute on test infra,
  passes locally

Status in Auto Package Testing:
  New
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Hi,
  I've asked yesterday on IRC but so far got no answer. I think it is right to 
file a bug about the current state of systemd autopkgtest to unite the efforts 
in regard to it.

  I was looking at the systemd tests for a no-change rebuild that really
  had no reason to now make it fail. While checking I found that as of
  this month (first bad test on 1st of February) most of the systemd
  test runs on amd64 will not pass/fail but instead in most cases time
  out.

  I've seen various people retry the case as it shows the typical
  symptoms of a "not the fault of the package, let us retry this" case.
  But it seems that won't help as the test history is rather clear.

  
  * Watch this in monospace to make more sense of it *

  $ check-autopkgtest-stats.sh -c 50 -p systemd -r "hirsute" -a "amd64"
  Check last 50 test results for src:systemd on releases 'hirsute' on 
architectures 'amd64'
  Of the 50 last tests, we had these subtest failing per release/arch:

  hirsute
amd64
  tests-in-lxd   (F  2% f  0% S  0% B 12% => P 52%/) 
.BTTTBTT.BTBTTTBBTTT..F..
  hostnamed  (F  0% f  0% S  0% B 12% => P 54%/) 
.BTTTBTT.BTBTTTBBTTT.
  build-login(F  0% f  0% S  0% B 12% => P 54%/) 
.BTTTBTT.BTBTTTBBTTT.
  unit-config(F  0% f  0% S  0% B 12% => P 54%/) 
.BTTTBTT.BTBTTTBBTTT.
  networkd-testpy(F  0% f  0% S  0% B 12% => P 54%/) 
.BTTTBTT.BTBTTTBBTTT.
  localed-locale (F  0% f  0% S  0% B 12% => P 54%/) 
.BTTTBTT.BTBTTTBBTTT.
  boot-and-services  (F  4% f  0% S  0% B 12% => P 50%/) 
.BTTTBTT.BTBTTTBBTTT...F.F...
  timedated  (F  0% f  0% S  0% B 12% => P 54%/) 
.BTTTBTT.BTBTTTBBTTT.
  boot-smoke (F  0% f  0% S  0% B 12% => P 54%/) 
.BTTTBTT.BTBTTTBBTTT.
  logind (F  0% f  0% S  0% B 12% => P 54%/) 
.BTTTBTT.BTBTTTBBTTT.
  storage(F  0% f  0% S  0% B 12% => P 54%/) 
.BTTTBTT.BTBTTTBBTTT.
  upstream   (F 12% f  0% S  0% B 12% => P 42%/) 
.BTTTBTT.BTBTTTBBTTTF.F.F..FF..F.
  udev   (F  0% f  0% S  0% B 12% => P 54%/) 
.BTTTBTT.BTBTTTBBTTT.
  systemd-fsckd  (F  8% f  0% S  0% B 12% => P 46%/) 
FBTTTBTTFBTBTTTBBTTT.F..F
  root-unittests (F  0% f  0% S  0% B 12% => P 54%/) 
.BTTTBTT.BTBTTTBBTTT.
  localed-x11-keymap (F  0% f  0% S  0% B 12% => P 54%/) 
.BTTTBTT.BTBTTTBBTTT.

  We see that formerly we had the known to be somewhat flaky, but
  otherwise working test (time goes from right to left). So we had the
  usual suspects of tests like upstream/systemd-fsck that failed a few
  times, but also working runs in between.

  But since February 22/24 runs failed very bad.
  6 (=B) of those cases are aborting mid execution
autopkgtest [22:08:58]: ERROR: testbed failure: testbed auxverb failed with 
exit code 255
  And 16 of them timed out
: failure: Timed out on waiting for ssh connection

  Sadly the 2/24 that didn't hard fail by that where broken by the known
  flaky systemd-fsckd test.

  Something drives this test crazy that we have to find and resolve, at
  the current rate nothing depending on it is likely to migrate.

[Touch-packages] [Bug 1907433] Re: [SRU] New stable release 2.64.6

2021-01-27 Thread Iain Lane
> retry the test

That has been done. Now the only red is netplan.io.

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

Title:
  [SRU] New stable release 2.64.6

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Focal:
  Fix Committed

Bug description:
  [ Description ]

  Take this new upstrem stable release.

  It was easiest for me to merge the latest release in this series from
  Debian, and then import the subsequent point releases on top of that.

  Visually in the diff there is one change resulting from this:
  splitting a two-patch upstream cherry pick into two individual patch
  files. This is cleaner anyway IMO, but is also no change if you look
  at the resulting patched source.

  Overview of changes in GLib 2.64.6
  ==

  * This is expected to be the last release in the 2.64 series; the new stable
    series is 2.66, and maintenance efforts will shift to that

  * Bugs fixed:
   - #2194 gtk3/glib crash on gimp
   - #2209 gthreadedresolver: faulty logic in parse_res_txt
   - !1633 Backport !1632 Fix large writes in gfileutils to glib-2-64
   - !1634 Backport !1631 “Fix splice behavior on cancellation” to glib-2-64
   - !1656 Backport !1187 “Define G_MSVC_SYMBOL_PREFIX correctly for ARM32” to 
glib-2-64
   - !1659 Backport !1652 “trash portal: Handle portal failures” to glib-2-64
   - !1666 Backport !1665 “Fix g_module_symbol() under Windows sometimes not 
succeeding” to glib-2-64
   - !1672 Backport !1671 “gdatetime: Avoid integer overflow creating dates too 
far in the past” to glib-2-64

  * Translation updates:
   - Croatian
   - Portuguese

  Overview of changes in GLib 2.64.5
  ==

  * Fix deadlock in `g_subprocess_communicate_async()` (work by
  Alexander Larsson) (#2182)

  * Fix cross-compilation on iOS (work by Nirbheek Chauhan) (#1868)

  * Bugs fixed:
   - !1519 Backport !1468 “glib-compile-resources: Fix exporting on Visual 
Studio” to glib-2-64
   - !1520 Backport !1517 “GWin32RegistryKey: Move assertions” to glib-2-64
   - !1565 Backport !1563 “gdesktopappinfo: Fix unnecessarily copied and leaked 
URI list” to glib-2-64
   - !1608 Backport !1607 “meson: Don't use gnulib for printf on iOS” to 
glib-2-64
   - !1618 Backport !1617 “Ensure g_subprocess_communicate_async() never 
blocks” to glib-2-64
   - !1621 Backport !1620 “gvariant: Ensure GVS.depth is initialised” to 
glib-2-64

  Overview of changes in GLib 2.64.4
  ==

  * Bugs fixed:
   - #2140 calling malloc in fork child is undefined-behaviour
   - !1507 Backport !1504 “win32 gpoll: Fix wait for at least one thread to 
return” to glib-2-64
   - !1523 Backport !1522 “meson: Fix gnulib printf checks” to glib-2-64
   - !1547 Backport !1544 “Resolve "calling malloc in fork child is 
undefined-behaviour"” to glib-2-64

  * Translation updates:
   - Kazakh
   - Slovenian

  [ QA ]

  Upstream release, so QA already performed by maintainers

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

  This upload will trigger many autopkgtests that we expect to not be
  regressed by this upload.

  [ What could go wrong ]

  This update contains fixes in multiple places so multiple apps could
  be affected. The consequences of a broken GLib can range from some
  functions returning bad results sometimes, which have minimal runtime
  implications, up to the system simply crashing all the time.

  Pretty much all parts of GNOME use GLib, so test anything in the
  desktop that you can. If you reboot the machine and can get to the
  desktop, that's already tested GLib extensively. But also run
  applications like GNOME terminal, Files and Epiphany.

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

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


[Touch-packages] [Bug 1907433] Re: [SRU] New stable release 2.64.6

2021-01-25 Thread Iain Lane
> retry the test

with a trigger on libxmlb to get the -proposed version installed.

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

Title:
  [SRU] New stable release 2.64.6

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Focal:
  Fix Committed

Bug description:
  [ Description ]

  Take this new upstrem stable release.

  It was easiest for me to merge the latest release in this series from
  Debian, and then import the subsequent point releases on top of that.

  Visually in the diff there is one change resulting from this:
  splitting a two-patch upstream cherry pick into two individual patch
  files. This is cleaner anyway IMO, but is also no change if you look
  at the resulting patched source.

  Overview of changes in GLib 2.64.6
  ==

  * This is expected to be the last release in the 2.64 series; the new stable
    series is 2.66, and maintenance efforts will shift to that

  * Bugs fixed:
   - #2194 gtk3/glib crash on gimp
   - #2209 gthreadedresolver: faulty logic in parse_res_txt
   - !1633 Backport !1632 Fix large writes in gfileutils to glib-2-64
   - !1634 Backport !1631 “Fix splice behavior on cancellation” to glib-2-64
   - !1656 Backport !1187 “Define G_MSVC_SYMBOL_PREFIX correctly for ARM32” to 
glib-2-64
   - !1659 Backport !1652 “trash portal: Handle portal failures” to glib-2-64
   - !1666 Backport !1665 “Fix g_module_symbol() under Windows sometimes not 
succeeding” to glib-2-64
   - !1672 Backport !1671 “gdatetime: Avoid integer overflow creating dates too 
far in the past” to glib-2-64

  * Translation updates:
   - Croatian
   - Portuguese

  Overview of changes in GLib 2.64.5
  ==

  * Fix deadlock in `g_subprocess_communicate_async()` (work by
  Alexander Larsson) (#2182)

  * Fix cross-compilation on iOS (work by Nirbheek Chauhan) (#1868)

  * Bugs fixed:
   - !1519 Backport !1468 “glib-compile-resources: Fix exporting on Visual 
Studio” to glib-2-64
   - !1520 Backport !1517 “GWin32RegistryKey: Move assertions” to glib-2-64
   - !1565 Backport !1563 “gdesktopappinfo: Fix unnecessarily copied and leaked 
URI list” to glib-2-64
   - !1608 Backport !1607 “meson: Don't use gnulib for printf on iOS” to 
glib-2-64
   - !1618 Backport !1617 “Ensure g_subprocess_communicate_async() never 
blocks” to glib-2-64
   - !1621 Backport !1620 “gvariant: Ensure GVS.depth is initialised” to 
glib-2-64

  Overview of changes in GLib 2.64.4
  ==

  * Bugs fixed:
   - #2140 calling malloc in fork child is undefined-behaviour
   - !1507 Backport !1504 “win32 gpoll: Fix wait for at least one thread to 
return” to glib-2-64
   - !1523 Backport !1522 “meson: Fix gnulib printf checks” to glib-2-64
   - !1547 Backport !1544 “Resolve "calling malloc in fork child is 
undefined-behaviour"” to glib-2-64

  * Translation updates:
   - Kazakh
   - Slovenian

  [ QA ]

  Upstream release, so QA already performed by maintainers

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

  This upload will trigger many autopkgtests that we expect to not be
  regressed by this upload.

  [ What could go wrong ]

  This update contains fixes in multiple places so multiple apps could
  be affected. The consequences of a broken GLib can range from some
  functions returning bad results sometimes, which have minimal runtime
  implications, up to the system simply crashing all the time.

  Pretty much all parts of GNOME use GLib, so test anything in the
  desktop that you can. If you reboot the machine and can get to the
  desktop, that's already tested GLib extensively. But also run
  applications like GNOME terminal, Files and Epiphany.

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

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


[Touch-packages] [Bug 1907433] Re: [SRU] New stable release 2.64.6

2021-01-25 Thread Iain Lane
Okay I've verified this now, thanks for adding. Using
2.64.6-1~ubuntu20.04.1 I tested

  - Logging in to Ubuntu
  - Logging out from Ubuntu
  - Fast user switching w/gdm3
  - Many applications which use GLib, including gedit and epiphany-browser

It seems good to me.

There are two outstanding autopkgtest regressions.

The libxmlb failure is bug #1890313 and I just fixed it upstream, in
hirsute (devel) & uploaded to the queue for focal/groovy. If you prefer
you can accept that and retry the test, it should go green.

netplan.io's one I didn't look into, but I think it is bug #1875677
(i.e. pre-existing). Should be hinted if not fixed?

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

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

Title:
  [SRU] New stable release 2.64.6

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Focal:
  Fix Committed

Bug description:
  [ Description ]

  Take this new upstrem stable release.

  It was easiest for me to merge the latest release in this series from
  Debian, and then import the subsequent point releases on top of that.

  Visually in the diff there is one change resulting from this:
  splitting a two-patch upstream cherry pick into two individual patch
  files. This is cleaner anyway IMO, but is also no change if you look
  at the resulting patched source.

  Overview of changes in GLib 2.64.6
  ==

  * This is expected to be the last release in the 2.64 series; the new stable
    series is 2.66, and maintenance efforts will shift to that

  * Bugs fixed:
   - #2194 gtk3/glib crash on gimp
   - #2209 gthreadedresolver: faulty logic in parse_res_txt
   - !1633 Backport !1632 Fix large writes in gfileutils to glib-2-64
   - !1634 Backport !1631 “Fix splice behavior on cancellation” to glib-2-64
   - !1656 Backport !1187 “Define G_MSVC_SYMBOL_PREFIX correctly for ARM32” to 
glib-2-64
   - !1659 Backport !1652 “trash portal: Handle portal failures” to glib-2-64
   - !1666 Backport !1665 “Fix g_module_symbol() under Windows sometimes not 
succeeding” to glib-2-64
   - !1672 Backport !1671 “gdatetime: Avoid integer overflow creating dates too 
far in the past” to glib-2-64

  * Translation updates:
   - Croatian
   - Portuguese

  Overview of changes in GLib 2.64.5
  ==

  * Fix deadlock in `g_subprocess_communicate_async()` (work by
  Alexander Larsson) (#2182)

  * Fix cross-compilation on iOS (work by Nirbheek Chauhan) (#1868)

  * Bugs fixed:
   - !1519 Backport !1468 “glib-compile-resources: Fix exporting on Visual 
Studio” to glib-2-64
   - !1520 Backport !1517 “GWin32RegistryKey: Move assertions” to glib-2-64
   - !1565 Backport !1563 “gdesktopappinfo: Fix unnecessarily copied and leaked 
URI list” to glib-2-64
   - !1608 Backport !1607 “meson: Don't use gnulib for printf on iOS” to 
glib-2-64
   - !1618 Backport !1617 “Ensure g_subprocess_communicate_async() never 
blocks” to glib-2-64
   - !1621 Backport !1620 “gvariant: Ensure GVS.depth is initialised” to 
glib-2-64

  Overview of changes in GLib 2.64.4
  ==

  * Bugs fixed:
   - #2140 calling malloc in fork child is undefined-behaviour
   - !1507 Backport !1504 “win32 gpoll: Fix wait for at least one thread to 
return” to glib-2-64
   - !1523 Backport !1522 “meson: Fix gnulib printf checks” to glib-2-64
   - !1547 Backport !1544 “Resolve "calling malloc in fork child is 
undefined-behaviour"” to glib-2-64

  * Translation updates:
   - Kazakh
   - Slovenian

  [ QA ]

  Upstream release, so QA already performed by maintainers

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

  This upload will trigger many autopkgtests that we expect to not be
  regressed by this upload.

  [ What could go wrong ]

  This update contains fixes in multiple places so multiple apps could
  be affected. The consequences of a broken GLib can range from some
  functions returning bad results sometimes, which have minimal runtime
  implications, up to the system simply crashing all the time.

  Pretty much all parts of GNOME use GLib, so test anything in the
  desktop that you can. If you reboot the machine and can get to the
  desktop, that's already tested GLib extensively. But also run
  applications like GNOME terminal, Files and Epiphany.

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

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


[Touch-packages] [Bug 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected

2021-01-19 Thread Iain Lane
** Changed in: ubuntu-cdimage
 Assignee: Shamindra (wy-354) => (unassigned)

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

Title:
  Installation fails due to useless immediate configuration error when
  "Install Third-Party Drivers" is selected

Status in Ubuntu CD Images:
  Fix Released
Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Bionic:
  In Progress
Status in apt source package in Focal:
  Fix Committed
Status in apt source package in Groovy:
  Fix Committed
Status in apt package in Debian:
  Unknown

Bug description:
  [Impact]
  Installations that really succeeded would then fail because APT could not 
immediately configure a package. Which is a pointless way to fail at that 
point, because everything did work out anyway.

  We have two changes that help address this:

  * The first one stops immediately configuring multi-arch siblings
  (e.g. libc6:i386 when it's configuring libc6:amd64). This was not
  necessary, and caused all the libc6:i386 failures here.

  * The second change sort of also supersedes the first one: It just
  ignores any errors from immediate configuration, relying on the fact
  that it's checked and rectified at a later point if there are
  unconfigured packages (which is what made all those failures happen
  spuriously after having successfully installed everything).

  [Test case]
  We have one test case in EIPP format in the Debian bug 973305 which was only 
helped by the second change, not the first one. Run /usr/lib/apt/planners < 
eipp.log and check there are no errors.

  TODO: It's unclear if the APT from proposed installed in the live
  session will fix the installer, needs investigation, but would make a
  useful test case.

  [Regression potential]
  It's imaginable that we missed something somewhere and some path that checked 
for a set error doesn't check it anymore, and we report success when we hit an 
error, but it seems unlikely.

  Behavior of --simulate changes. This used to fail before as well, and
  will now only produce a warning. We don't believe that is a reason of
  concern.

  [Groovy SRU]
  The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable 
which also incorporates changes to the documentation: A typo fix, replacing 
focal with groovy in examples, and minor Dutch manual pages translation updates.

  We do not have test cases for the documentation changes, and we do not
  consider there to be a huge regression potential. As long as they
  build, they should be readable - maybe some words are wrong in the
  translation, who knows.

  [Original bug report]
  Test Case
  1. Install Ubuntu Desktop on hardware with an nVidia card and select to 
install 3rd party drivers
  2. Proceed with installation

  The following error message is displayed in /var/log/syslog
  /plugininstall.py: Verifying downloads ...
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: 
"Version: '4.4.10-10ubuntu4' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: 
'1.2.11.dfsg-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: 
'1.0.9-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: 
'1.1.3-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: 
'1.3.4-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: 
'3.6.0-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: 
'1.1.5-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: 
'5.0.3-1' not found."
  /plugininstall.py: Failed to find package object for 

[Touch-packages] [Bug 1910576] Re: [MIR] libbpf (dependency of iproute2)

2021-01-15 Thread Iain Lane
laney@dev> ./change-override -S -c main -s hirsute libbpf
Override component to main
libbpf 0.3-2 in hirsute: universe/misc -> main
libbpf-dev 1:0.3-2 in hirsute amd64: universe/libdevel/optional/100% -> main
libbpf-dev 1:0.3-2 in hirsute arm64: universe/libdevel/optional/100% -> main
libbpf-dev 1:0.3-2 in hirsute armhf: universe/libdevel/optional/100% -> main
libbpf-dev 1:0.3-2 in hirsute ppc64el: universe/libdevel/optional/100% -> main
libbpf-dev 1:0.3-2 in hirsute riscv64: universe/libdevel/optional/100% -> main
libbpf-dev 1:0.3-2 in hirsute s390x: universe/libdevel/optional/100% -> main
libbpf0 1:0.3-2 in hirsute amd64: universe/libs/optional/100% -> main
libbpf0 1:0.3-2 in hirsute arm64: universe/libs/optional/100% -> main
libbpf0 1:0.3-2 in hirsute armhf: universe/libs/optional/100% -> main
libbpf0 1:0.3-2 in hirsute ppc64el: universe/libs/optional/100% -> main
libbpf0 1:0.3-2 in hirsute riscv64: universe/libs/optional/100% -> main
libbpf0 1:0.3-2 in hirsute s390x: universe/libs/optional/100% -> main
Override [y|N]? y
13 publications overridden.


** Changed in: libbpf (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 iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/1910576

Title:
  [MIR] libbpf (dependency of iproute2)

Status in iproute2 package in Ubuntu:
  Invalid
Status in libbpf package in Ubuntu:
  Fix Released

Bug description:
  [Availability]
  libbpf | 0.1.0-1 | groovy/universe  | source
  libbpf | 0.3-2   | hirsute/universe | source

  [Rationale]
  Libbpf is (or is about to become) a dependency for building iproute2 which 
already is in main. Using BPF is becoming more wide-spread. The library allows 
to load and use eBPF programs from user-space (functionality provided by the 
kernel). It is already maintained in main for Debian 
(https://tracker.debian.org/pkg/libbpf)

  [Security]
  Since the code is taken out of the Linux kernel, this should be treated 
similar to the kernel for security. Research uncovered no records about 
security issues.

  [Quality assurance]
  At this point there are no open bug reports against libbpf (except this one) 
in Ubuntu. Also no open bugs found in Debian. Project is taken from the kernel 
source and claims static analysis via LGTM and Coverty. Also has CI via Travis 
(https://travis-ci.com/github/libbpf/libbpf).
  Right now there are no dep-8 tests. Though potentially it should be possible 
to create those, would this really add additional benefit beyond having 
upstream CI?
  A test build on hirsute was showing no warnings beyond lintian complaining 
about things which would be changed if we had delta (unstable as series for 
example). Otherwise was clean.

  [Dependencies]
  libc6: main
  libelf1: main
  zlib1g: main

  [Standards compliance]
  $ lintian --pedantic libbpf_0.3-2.dsc
  P: libbpf source: no-homepage-field
  P: libbpf source: silent-on-rules-requiring-root

  [Maintenance]
  As this is only taking out code from the kernel into a separate library 
package, the maintenance effort should be minimal. Packaging is done in Debian 
and is synced into Ubuntu (no delta).

  [Background information]
  A discourse about why this is packaged outside the kernel can be found at 
https://lwn.net/Articles/836911/.

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

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


[Touch-packages] [Bug 1779767] Re: Default cron PATH does not include /snap/bin

2021-01-14 Thread Iain Lane
This bug is old but I'm going to un-duplicate it. I don't believe it is
fixed.

I've got a cron script on focal (cron 3.0pl1-136ubuntu1) which is
indirectly running `lxc` from a snap (/snap/bin/lxc).

I found the following in mail though:

/home/ubuntu/autopkgtest/tools/autopkgtest-build-lxd: 139: lxc: not found
/home/ubuntu/autopkgtest/tools/autopkgtest-build-lxd: 1: lxc: not found

crontab(5) mentions the default as being "/usr/bin:/bin", and how it
does NOT come from /etc/environment. What you have to do is set
"PATH=/snap/bin:/usr/bin:/bin" at the top of the crontab file if you
want to be able to use snaps. (You can't do "PATH=/snap/bin:$PATH"...)

pathnames.h has a #define for _PATH_DEFPATH where AFAICS this comes
from. Maybe it's that which we would want to modify to fix this for cron
in Ubuntu.

** This bug is no longer a duplicate of bug 1771858
   /snap/bin not in default PATH for units, snapd should ship 
system-environment-generators to inject /snap/bin into $PATH

** Changed in: cron (Ubuntu)
 Assignee: Dimitri John Ledkov (xnox) => (unassigned)

** Tags removed: rls-ee-incoming
** Tags added: rls-ff-incoming rls-hh-incoming

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

Title:
  Default cron PATH does not include /snap/bin

Status in cron package in Ubuntu:
  Confirmed

Bug description:
  I recently changed from a .deb install of LXD to a snap, and was
  surprised that one of my crontab scripts stopped working.

  I see that $PATH in a cron script only contains "/usr/bin:/bin",
  whereas my default shell also includes "/snap/bin".

  It seems to me that for the best user experience with snaps,
  "/snap/bin" should be part of the default $PATH in cron.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cron 3.0pl1-128.1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_20_21_generic_40 
kpatch_livepatch_Ubuntu_4_15_0_20_21_generic_39 
livepatch_livepatch_Ubuntu_4_15_0_20_21_generic_ zfs zunicode zavl icp zcommon 
znvpair
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul  2 14:30:06 2018
  InstallationDate: Installed on 2017-12-20 (194 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171219)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: cron
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1908502] Re: [MIR] libtiff5 dependency on libdeflate0

2021-01-13 Thread Iain Lane
** Also affects: tiff (Ubuntu Hirsute)
   Importance: Undecided
 Assignee: Olivier Tilloy (osomon)
   Status: Confirmed

** Also affects: libdeflate (Ubuntu Hirsute)
   Importance: Undecided
   Status: Incomplete

** Tags removed: rls-hh-incoming

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

Title:
  [MIR] libtiff5 dependency on libdeflate0

Status in libdeflate package in Ubuntu:
  Incomplete
Status in tiff package in Ubuntu:
  Confirmed
Status in libdeflate source package in Hirsute:
  Incomplete
Status in tiff source package in Hirsute:
  Confirmed

Bug description:
  tiff 4.1.0+git201212-1 enabled deflate support, adding libdeflate0 as
  a dependency to libtiff5, making the package uninstallable.

  Therefor I uploaded 4.1.0+git201212-1ubuntu1 disabling the deflate
  support to make libtiff5 installable again.

  Either this package stays this way, or it needs a MIR for libdeflate.

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

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


[Touch-packages] [Bug 1627564] Re: Debconf crash due to assertion failure in ensure_surface_for_gicon [gtkiconhelper.c:493] (when png loader is missing/during upgrades)

2021-01-13 Thread Iain Lane
> OTOH I think there is an easy fix for GTK+ to always include an
"image-missing" icon at compile time

I'm sorry, it's not that easy. A PNG icon is indeed included, and it
gets found properly (also from the actual icon theme; that is a
dependency of GTK). The problem is the ability to load PNGs *at all* is
not available sometimes during the middle of dist-upgrades.

I think extending that test program in Debconf (referred to in the IRC
log above) to do a bit more work - trying to load an icon - might make
the fallback trigger in this case too.

e.g:

  my $window = Gtk3::Window->new('toplevel');
  my $icontheme = Gtk3::IconTheme::get_default;
  my $icon = $icontheme->load_icon('image-missing', 32, []);

If you manually remove '/usr/lib/*/gdk-pixbuf-2.0/2.10.0/loaders.cache'
(suggest doing this in a VM) then you can reproduce this by extracting
the program out of Debconf.

** Changed in: gtk+3.0 (Ubuntu)
   Status: New => Invalid

** Changed in: gtk+3.0 (Ubuntu Focal)
   Status: New => Invalid

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

Title:
  Debconf crash due to assertion failure in ensure_surface_for_gicon
  [gtkiconhelper.c:493] (when png loader is missing/during upgrades)

Status in debconf package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Invalid
Status in debconf source package in Focal:
  Confirmed
Status in gtk+3.0 source package in Focal:
  Invalid

Bug description:
  https://errors.ubuntu.com/problem/2b11576fed59ad23c640bc85a266cc82ec30a689
  https://errors.ubuntu.com/problem/9d612b3f25168e76adb91fa4eedc301ffa632383

  ---

  bubble opened up indicating there was a failure during the latest
  update.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: lightdm-gtk-greeter 2.0.1-2ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7
  Uname: Linux 4.4.0-9136-generic i686
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: i386
  Date: Sun Sep 25 20:37:06 2016
  ExecutablePath: /usr/sbin/lightdm-gtk-greeter
  InstallationDate: Installed on 2016-08-04 (52 days ago)
  InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Alpha i386 (20160727)
  ProcCmdline: /usr/sbin/lightdm-gtk-greeter
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/false
  Signal: 6
  SourcePackage: lightdm-gtk-greeter
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  modified.conffile..etc.lightdm.lightdm-gtk-greeter.conf:
   [greeter]
   theme-name = Lubuntu-dark-panel
  mtime.conffile..etc.lightdm.lightdm-gtk-greeter.conf: 
2016-08-14T22:33:57.293011

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

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


[Touch-packages] [Bug 1908136] Re: no_proxy=::1 is not honored by curl in Bionic and earlier versions

2020-12-16 Thread Iain Lane
** Changed in: auto-package-testing
   Status: New => Fix Released

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

Title:
  no_proxy=::1 is not honored by curl in Bionic and earlier versions

Status in Auto Package Testing:
  Fix Released
Status in curl package in Ubuntu:
  Fix Released
Status in curl source package in Xenial:
  New
Status in curl source package in Bionic:
  New
Status in curl source package in Focal:
  Fix Released

Bug description:
  Bionic:

  env no_proxy=::1 http_proxy=http://foo:8080 curl -v http://[::1]:80/bar.html
  * Could not resolve proxy: foo
  * Closing connection 0
  curl: (5) Could not resolve proxy: foo

  Focal:

  $ env no_proxy=::1 http_proxy=http://foo:8080 curl -v http://[::1]:80/bar.html
  * Uses proxy env variable no_proxy == '::1'
  *   Trying ::1:80...
  * TCP_NODELAY set
  * Immediate connect fail for ::1: Network is unreachable
  * Closing connection 0
  curl: (7) Couldn't connect to server

To manage notifications about this bug go to:
https://bugs.launchpad.net/auto-package-testing/+bug/1908136/+subscriptions

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


[Touch-packages] [Bug 1907433] Re: [SRU] New stable release 2.64.6

2020-12-09 Thread Iain Lane
** Description changed:

  [ Description ]
  
  Take this new upstrem stable release.
  
  Overview of changes in GLib 2.64.6
  ==
  
  * This is expected to be the last release in the 2.64 series; the new stable
-   series is 2.66, and maintenance efforts will shift to that
+   series is 2.66, and maintenance efforts will shift to that
  
  * Bugs fixed:
-  - #2194 gtk3/glib crash on gimp
-  - #2209 gthreadedresolver: faulty logic in parse_res_txt
-  - !1633 Backport !1632 Fix large writes in gfileutils to glib-2-64
-  - !1634 Backport !1631 “Fix splice behavior on cancellation” to glib-2-64
-  - !1656 Backport !1187 “Define G_MSVC_SYMBOL_PREFIX correctly for ARM32” to 
glib-2-64
-  - !1659 Backport !1652 “trash portal: Handle portal failures” to glib-2-64
-  - !1666 Backport !1665 “Fix g_module_symbol() under Windows sometimes not 
succeeding” to glib-2-64
-  - !1672 Backport !1671 “gdatetime: Avoid integer overflow creating dates too 
far in the past” to glib-2-64
+  - #2194 gtk3/glib crash on gimp
+  - #2209 gthreadedresolver: faulty logic in parse_res_txt
+  - !1633 Backport !1632 Fix large writes in gfileutils to glib-2-64
+  - !1634 Backport !1631 “Fix splice behavior on cancellation” to glib-2-64
+  - !1656 Backport !1187 “Define G_MSVC_SYMBOL_PREFIX correctly for ARM32” to 
glib-2-64
+  - !1659 Backport !1652 “trash portal: Handle portal failures” to glib-2-64
+  - !1666 Backport !1665 “Fix g_module_symbol() under Windows sometimes not 
succeeding” to glib-2-64
+  - !1672 Backport !1671 “gdatetime: Avoid integer overflow creating dates too 
far in the past” to glib-2-64
  
  * Translation updates:
-  - Croatian
-  - Portuguese
- 
+  - Croatian
+  - Portuguese
  
  Overview of changes in GLib 2.64.5
  ==
  
  * Fix deadlock in `g_subprocess_communicate_async()` (work by Alexander
  Larsson) (#2182)
  
  * Fix cross-compilation on iOS (work by Nirbheek Chauhan) (#1868)
  
  * Bugs fixed:
-  - !1519 Backport !1468 “glib-compile-resources: Fix exporting on Visual 
Studio” to glib-2-64
-  - !1520 Backport !1517 “GWin32RegistryKey: Move assertions” to glib-2-64
-  - !1565 Backport !1563 “gdesktopappinfo: Fix unnecessarily copied and leaked 
URI list” to glib-2-64
-  - !1608 Backport !1607 “meson: Don't use gnulib for printf on iOS” to 
glib-2-64
-  - !1618 Backport !1617 “Ensure g_subprocess_communicate_async() never 
blocks” to glib-2-64
-  - !1621 Backport !1620 “gvariant: Ensure GVS.depth is initialised” to 
glib-2-64
- 
+  - !1519 Backport !1468 “glib-compile-resources: Fix exporting on Visual 
Studio” to glib-2-64
+  - !1520 Backport !1517 “GWin32RegistryKey: Move assertions” to glib-2-64
+  - !1565 Backport !1563 “gdesktopappinfo: Fix unnecessarily copied and leaked 
URI list” to glib-2-64
+  - !1608 Backport !1607 “meson: Don't use gnulib for printf on iOS” to 
glib-2-64
+  - !1618 Backport !1617 “Ensure g_subprocess_communicate_async() never 
blocks” to glib-2-64
+  - !1621 Backport !1620 “gvariant: Ensure GVS.depth is initialised” to 
glib-2-64
  
  Overview of changes in GLib 2.64.4
  ==
  
  * Bugs fixed:
-  - #2140 calling malloc in fork child is undefined-behaviour
-  - !1507 Backport !1504 “win32 gpoll: Fix wait for at least one thread to 
return” to glib-2-64
-  - !1523 Backport !1522 “meson: Fix gnulib printf checks” to glib-2-64
-  - !1547 Backport !1544 “Resolve "calling malloc in fork child is 
undefined-behaviour"” to glib-2-64
+  - #2140 calling malloc in fork child is undefined-behaviour
+  - !1507 Backport !1504 “win32 gpoll: Fix wait for at least one thread to 
return” to glib-2-64
+  - !1523 Backport !1522 “meson: Fix gnulib printf checks” to glib-2-64
+  - !1547 Backport !1544 “Resolve "calling malloc in fork child is 
undefined-behaviour"” to glib-2-64
  
  * Translation updates:
-  - Kazakh
-  - Slovenian
+  - Kazakh
+  - Slovenian
  
  [ QA ]
  
  Upstream release, so QA already performed by maintainers
  
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME
  
  This upload will trigger many autopkgtests that we expect to not be
  regressed by this upload.
  
- [ Regression potential ]
+ [ What could go wrong ]
  
- Various fixes in multiple places so multiple apps could be affected.
+ This update contains fixes in multiple places so multiple apps could be
+ affected. The consequences of a broken GLib can range from some
+ functions returning bad results sometimes, which have minimal runtime
+ implications, up to the system simply crashing all the time.
+ 
  Pretty much all parts of GNOME use GLib, so test anything in the desktop
  that you can. If you reboot the machine and can get to the desktop,
  that's already tested GLib extensively. But also run applications like
  GNOME terminal, Files and Epiphany.

** Description changed:

  [ Description ]
  
  Take this new upstrem stable release.
+ 
+ It was easiest for me to merge the latest release in this series from
+ Debian, 

[Touch-packages] [Bug 1907433] [NEW] [SRU] New stable release 2.64.6

2020-12-09 Thread Iain Lane
Public bug reported:

[ Description ]

Take this new upstrem stable release.

Overview of changes in GLib 2.64.6
==

* This is expected to be the last release in the 2.64 series; the new stable
  series is 2.66, and maintenance efforts will shift to that

* Bugs fixed:
 - #2194 gtk3/glib crash on gimp
 - #2209 gthreadedresolver: faulty logic in parse_res_txt
 - !1633 Backport !1632 Fix large writes in gfileutils to glib-2-64
 - !1634 Backport !1631 “Fix splice behavior on cancellation” to glib-2-64
 - !1656 Backport !1187 “Define G_MSVC_SYMBOL_PREFIX correctly for ARM32” to 
glib-2-64
 - !1659 Backport !1652 “trash portal: Handle portal failures” to glib-2-64
 - !1666 Backport !1665 “Fix g_module_symbol() under Windows sometimes not 
succeeding” to glib-2-64
 - !1672 Backport !1671 “gdatetime: Avoid integer overflow creating dates too 
far in the past” to glib-2-64

* Translation updates:
 - Croatian
 - Portuguese


Overview of changes in GLib 2.64.5
==

* Fix deadlock in `g_subprocess_communicate_async()` (work by Alexander
Larsson) (#2182)

* Fix cross-compilation on iOS (work by Nirbheek Chauhan) (#1868)

* Bugs fixed:
 - !1519 Backport !1468 “glib-compile-resources: Fix exporting on Visual 
Studio” to glib-2-64
 - !1520 Backport !1517 “GWin32RegistryKey: Move assertions” to glib-2-64
 - !1565 Backport !1563 “gdesktopappinfo: Fix unnecessarily copied and leaked 
URI list” to glib-2-64
 - !1608 Backport !1607 “meson: Don't use gnulib for printf on iOS” to glib-2-64
 - !1618 Backport !1617 “Ensure g_subprocess_communicate_async() never blocks” 
to glib-2-64
 - !1621 Backport !1620 “gvariant: Ensure GVS.depth is initialised” to glib-2-64


Overview of changes in GLib 2.64.4
==

* Bugs fixed:
 - #2140 calling malloc in fork child is undefined-behaviour
 - !1507 Backport !1504 “win32 gpoll: Fix wait for at least one thread to 
return” to glib-2-64
 - !1523 Backport !1522 “meson: Fix gnulib printf checks” to glib-2-64
 - !1547 Backport !1544 “Resolve "calling malloc in fork child is 
undefined-behaviour"” to glib-2-64

* Translation updates:
 - Kazakh
 - Slovenian

[ QA ]

Upstream release, so QA already performed by maintainers

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

This upload will trigger many autopkgtests that we expect to not be
regressed by this upload.

[ Regression potential ]

Various fixes in multiple places so multiple apps could be affected.
Pretty much all parts of GNOME use GLib, so test anything in the desktop
that you can. If you reboot the machine and can get to the desktop,
that's already tested GLib extensively. But also run applications like
GNOME terminal, Files and Epiphany.

** Affects: glib2.0 (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: glib2.0 (Ubuntu Focal)
 Importance: Undecided
 Assignee: Iain Lane (laney)
 Status: In Progress

** Also affects: glib2.0 (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Changed in: glib2.0 (Ubuntu Focal)
   Status: New => In Progress

** Changed in: glib2.0 (Ubuntu Focal)
 Assignee: (unassigned) => Iain Lane (laney)

** Changed in: glib2.0 (Ubuntu)
   Status: New => Fix Released

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

Title:
  [SRU] New stable release 2.64.6

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Focal:
  In Progress

Bug description:
  [ Description ]

  Take this new upstrem stable release.

  Overview of changes in GLib 2.64.6
  ==

  * This is expected to be the last release in the 2.64 series; the new stable
series is 2.66, and maintenance efforts will shift to that

  * Bugs fixed:
   - #2194 gtk3/glib crash on gimp
   - #2209 gthreadedresolver: faulty logic in parse_res_txt
   - !1633 Backport !1632 Fix large writes in gfileutils to glib-2-64
   - !1634 Backport !1631 “Fix splice behavior on cancellation” to glib-2-64
   - !1656 Backport !1187 “Define G_MSVC_SYMBOL_PREFIX correctly for ARM32” to 
glib-2-64
   - !1659 Backport !1652 “trash portal: Handle portal failures” to glib-2-64
   - !1666 Backport !1665 “Fix g_module_symbol() under Windows sometimes not 
succeeding” to glib-2-64
   - !1672 Backport !1671 “gdatetime: Avoid integer overflow creating dates too 
far in the past” to glib-2-64

  * Translation updates:
   - Croatian
   - Portuguese

  
  Overview of changes in GLib 2.64.5
  ==

  * Fix deadlock in `g_subprocess_communicate_async()` (work by
  Alexander Larsson) (#2182)

  * Fix cross-compilation on iOS (work by Nirbheek Chauhan) (#1868)

  * Bugs fixed:
   - !1519 Backport !1468 “glib-compile-resources: Fix exporting on Visual 
Studio” to glib-2-64
   - !

[Touch-packages] [Bug 1903048] Re: [SRU] Bluetooth won't activate on the pi 400

2020-11-13 Thread Iain Lane
The point for me is that we should be trying to avoid taking on
indefinite technical debt (patches that have to be rebased forever).
It's "fine" to include them ahead of any upstream schedule if we need to
for hardware enablement, but we do need to have plans to make this be a
non permanent situation. That's what Seb is asking for, and I'm totally
on board with that.

btw, I don't think it's fair to characterise code review as pedantry

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

Title:
  [SRU] Bluetooth won't activate on the pi 400

Status in bluez package in Ubuntu:
  Triaged
Status in bluez source package in Hirsute:
  Triaged

Bug description:
  [Impact]

  Without these patches, Bluetooth is inoperable on the recently
  released Raspberry Pi 400.

  [Test Case]

  * Boot the Ubuntu Desktop for Pi image on a Pi 400.
  * Start the Settings application and switch to the Bluetooth tab
  * Verify that Bluetooth is not enabled and attempting to activate it fails
  * sudo add-apt-repository ppa:waveform/pi-bluetooth
  * sudo apt update
  * sudo apt install bluez
  * sudo reboot
  * Start the Settings application and switch to the Bluetooth tab
  * Verify that Bluetooth is active and that Bluetooth devices (e.g. mice, 
mobile phones, headphones, etc.) can connect and operate correctly 

  [Regression Potential]

  Extremely low (on groovy in particular, this has the same version of
  bluez as hirsute). The only significant risk is to non-Pi platforms or
  dongles which also use the Broadcom 43xx (or Cypress 305) chips for
  Bluetooth which might be inadvertently affected by these patches.

  [Original Description]

  The new Pi 400 has a slightly different Wifi/BT chip to the Pi4.
  Whilst wifi works happily, Bluetooth fails to operate. This doesn't
  appear to be an issue with either the firmware (the latest versions
  from upstream Raspbian have been tried), or the kernel (a known-good
  raspi kernel has been tested under Ubuntu), but with Bluez itself.
  Specifically, tracing the initialization with btmon on Raspbian and
  Ubuntu, the stack consistently fails when attempting to "Set Default
  PHY" on the latter. Curiously, under Ubuntu the adapter also appears
  to lack a MAC address.

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

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


[Touch-packages] [Bug 1902898] Re: power-button action inconsistent between user session and greeter

2020-11-04 Thread Iain Lane
Issue here I think is that we use per-session overrides for the majority
of our Ubuntu customisations, and these don't apply to greeter sessions.

** Tags added: rls-hh-incoming

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

Title:
  power-button action inconsistent between user session and greeter

Status in ubuntu-settings package in Ubuntu:
  New
Status in ubuntu-settings source package in Focal:
  Confirmed
Status in ubuntu-settings source package in Groovy:
  New
Status in ubuntu-settings source package in Hirsute:
  New

Bug description:
  When a user is logged in to the Ubuntu desktop, a power button event
  will cause the user to be prompted to choose if they'd like to proceed
  with a shutdown. However, if the system is sitting at a greeter
  screen, a power button event will instead attempt a suspend w/o
  prompting. This is due to a different set of defaults for the greeter
  and the user:

  For a logged-in desktop user, they
  see:

  $ gsettings get org.gnome.settings-daemon.plugins.power
  power-button-action 'interactive'

  But the gdm user sees:
  $ sudo machinectl shell gdm@ /bin/bash
  Connected to the local host. Press ^] three times within 1s to exit session.
  gdm:~$ gsettings get org.gnome.settings-daemon.plugins.power 
power-button-action
  'suspend'

  Changing the gdm user's setting to "interactive" using gsettings
  causes the greeter to begin prompting, consistent with the logged in
  user experience.

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

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


[Touch-packages] [Bug 1897934] Re: [SRU][Intel HDA] The initial sound level is set to zero (muted)

2020-10-22 Thread Iain Lane
ah I see, OK - I will upload, thanks!

can you update the test case to say that this version of alsa-utils is
needed please? maybe provide a PPA link for people to install it with,
until that is accepted into focal?

** Changed in: alsa-lib (Ubuntu Focal)
   Status: Incomplete => Fix Committed

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

Title:
  [SRU][Intel HDA] The initial sound level is set to zero (muted)

Status in Release Notes for Ubuntu:
  New
Status in alsa-lib package in Ubuntu:
  Fix Committed
Status in alsa-lib source package in Focal:
  Fix Committed
Status in alsa-lib source package in Groovy:
  Fix Committed

Bug description:
  [Impact]
  Fail to run '/usr/sbin/alsactl restore' on the HDA-Intel machines, this
  results in the failure on setting the init mixer values for HDA sound
  card, and users experience the mute of audio after installing the 20.10.  

  [Fix]
  Backport a patch from the latest alsa-lib (v1.2.3+)

  [Test]
  Without the patched alsa-lib, rm ~/.config/pulse/*;sudo rm /var/lib/alsa/*;
  sudo sh -c "echo b > /proc/sysrq-trigger", after booting up, the audio is
  muted.

  Install the patched alsa-lib, rm ~/.config/pulse/*;sudo rm /var/lib/alsa/*;
  sudo sh -c "echo b > /proc/sysrq-trigger", after booting up, the audio is
  not muted.

  [Regression Potential]
  This could make the ucm audio fail to initialize, but this possibility is
  very low, since this patch is from upstream, and I tested on a ucm based
  machine, the audio is good.

  
  On boot into the live session - or on first install the sound level is muted.

  I have to use GNOME Control Center - Sounds to change to an
  appropriate level.  Once changed the level chosen is correctly
  retained between reboots.

  This appears to be a regression from 20.04 where the sound level was
  set to - I guess - 80% on the live-session/first install

  ProblemType: BugDistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.1-1ubuntu11
  ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10
  Uname: Linux 5.8.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu48
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu-budgie   5041 F pulseaudio
  CasperMD5CheckResult: pass
  CasperVersion: 1.452
  CurrentDesktop: Budgie:GNOME
  Date: Wed Sep 30 16:03:08 2020
  LiveMediaBuild: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Beta amd64 (20200930)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bashSourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/15/2016
  dmi.bios.release: 15.31
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.1F
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80BF
  dmi.board.vendor: HP
  dmi.board.version: 95.16
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 95.22
  dmi.modalias: 
dmi:bvnInsyde:bvrF.1F:bd02/15/2016:br15.31:efr95.22:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.sku: N9S73EA#ABU
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1897934/+subscriptions

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


[Touch-packages] [Bug 1897934] Re: [SRU][Intel HDA] The initial sound level is set to zero (muted)

2020-10-22 Thread Iain Lane
I don't see the same problem on the Focal ISO - do we need to fix this
in Focal?

** Changed in: alsa-lib (Ubuntu Focal)
   Status: In Progress => Incomplete

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

Title:
  [SRU][Intel HDA] The initial sound level is set to zero (muted)

Status in Release Notes for Ubuntu:
  New
Status in alsa-lib package in Ubuntu:
  Fix Committed
Status in alsa-lib source package in Focal:
  Incomplete
Status in alsa-lib source package in Groovy:
  Fix Committed

Bug description:
  [Impact]
  Fail to run '/usr/sbin/alsactl restore' on the HDA-Intel machines, this
  results in the failure on setting the init mixer values for HDA sound
  card, and users experience the mute of audio after installing the 20.10.  

  [Fix]
  Backport a patch from the latest alsa-lib (v1.2.3+)

  [Test]
  Without the patched alsa-lib, rm ~/.config/pulse/*;sudo rm /var/lib/alsa/*;
  sudo sh -c "echo b > /proc/sysrq-trigger", after booting up, the audio is
  muted.

  Install the patched alsa-lib, rm ~/.config/pulse/*;sudo rm /var/lib/alsa/*;
  sudo sh -c "echo b > /proc/sysrq-trigger", after booting up, the audio is
  not muted.

  [Regression Potential]
  This could make the ucm audio fail to initialize, but this possibility is
  very low, since this patch is from upstream, and I tested on a ucm based
  machine, the audio is good.

  
  On boot into the live session - or on first install the sound level is muted.

  I have to use GNOME Control Center - Sounds to change to an
  appropriate level.  Once changed the level chosen is correctly
  retained between reboots.

  This appears to be a regression from 20.04 where the sound level was
  set to - I guess - 80% on the live-session/first install

  ProblemType: BugDistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.1-1ubuntu11
  ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10
  Uname: Linux 5.8.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu48
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu-budgie   5041 F pulseaudio
  CasperMD5CheckResult: pass
  CasperVersion: 1.452
  CurrentDesktop: Budgie:GNOME
  Date: Wed Sep 30 16:03:08 2020
  LiveMediaBuild: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Beta amd64 (20200930)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bashSourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/15/2016
  dmi.bios.release: 15.31
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.1F
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80BF
  dmi.board.vendor: HP
  dmi.board.version: 95.16
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 95.22
  dmi.modalias: 
dmi:bvnInsyde:bvrF.1F:bd02/15/2016:br15.31:efr95.22:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.sku: N9S73EA#ABU
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1897934/+subscriptions

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


[Touch-packages] [Bug 1898729] Re: shim can end up being removed

2020-10-07 Thread Iain Lane
That does sound useful and worth scheduling I think. I didn't know about
that until now!

I'll try to find some time soon to go back to the release I installed
from and take a look there, per Steve's suggestion.

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

Title:
  shim can end up being removed

Status in apt package in Ubuntu:
  New
Status in shim package in Ubuntu:
  New

Bug description:
  I just did a set of package updates in focal that ended up with shim
  shim-signed mokutil being autoremoved.

  I rebooted without noticing, and had to manually recover the system
  thereafter. :(

  Julian says there was a period of time where these were marked auto. I
  suppose that I installed during this window, and now some dependency
  change meant that as far as apt was concerned they weren't required
  any more.

  Can we please consider never proposing these packages for autoremoval?
  apt has NeverAutoRemove for this which could be used, or some other
  appropriate method.

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

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


[Touch-packages] [Bug 1898729] Re: shim can end up being removed

2020-10-06 Thread Iain Lane
Cheers Steve. Nope, -proposed is not enabled.

Yes, it happened - it was the result of an explicit autoremove on my
part though after I had dist-upgraded to current focal-updates. I should
have noticed that this was happening and stopped it, granted. :)

Attached is the snippet of apt's term.log corresponding to the
autoremove run. It crapped out at the end as usual because I have a tiny
/boot; not included but mentioning because it might mean the log is
truncated a bit.

Now, this system has been through several Ubuntu development cycles.
It's likely to be unclean. So I don't mind if the priority is low but
making use of this feature of apt feels sensible to me, although
admittedly there's a question about where we would stop if we started to
do it.

** Attachment added: "shim"
   
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1898729/+attachment/5418422/+files/shim

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

Title:
  shim can end up being removed

Status in apt package in Ubuntu:
  New
Status in shim package in Ubuntu:
  New

Bug description:
  I just did a set of package updates in focal that ended up with shim
  shim-signed mokutil being autoremoved.

  I rebooted without noticing, and had to manually recover the system
  thereafter. :(

  Julian says there was a period of time where these were marked auto. I
  suppose that I installed during this window, and now some dependency
  change meant that as far as apt was concerned they weren't required
  any more.

  Can we please consider never proposing these packages for autoremoval?
  apt has NeverAutoRemove for this which could be used, or some other
  appropriate method.

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

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


[Touch-packages] [Bug 1898729] Re: shim can end up being removed

2020-10-06 Thread Iain Lane
I've marked apt as affected because it ships
/etc/apt/apt.conf.d/01autoremove but I suppose each of the affected
packages could also supply their own snippets.

** Tags added: rls-ff-incoming

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

Title:
  shim can end up being removed

Status in apt package in Ubuntu:
  New
Status in shim package in Ubuntu:
  New

Bug description:
  I just did a set of package updates in focal that ended up with shim
  shim-signed mokutil being autoremoved.

  I rebooted without noticing, and had to manually recover the system
  thereafter. :(

  Julian says there was a period of time where these were marked auto. I
  suppose that I installed during this window, and now some dependency
  change meant that as far as apt was concerned they weren't required
  any more.

  Can we please consider never proposing these packages for autoremoval?
  apt has NeverAutoRemove for this which could be used, or some other
  appropriate method.

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

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


[Touch-packages] [Bug 1898729] [NEW] shim can end up being removed

2020-10-06 Thread Iain Lane
Public bug reported:

I just did a set of package updates in focal that ended up with shim
shim-signed mokutil being autoremoved.

I rebooted without noticing, and had to manually recover the system
thereafter. :(

Julian says there was a period of time where these were marked auto. I
suppose that I installed during this window, and now some dependency
change meant that as far as apt was concerned they weren't required any
more.

Can we please consider never proposing these packages for autoremoval?
apt has NeverAutoRemove for this which could be used, or some other
appropriate method.

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

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


** Tags: rls-ff-incoming

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

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

Title:
  shim can end up being removed

Status in apt package in Ubuntu:
  New
Status in shim package in Ubuntu:
  New

Bug description:
  I just did a set of package updates in focal that ended up with shim
  shim-signed mokutil being autoremoved.

  I rebooted without noticing, and had to manually recover the system
  thereafter. :(

  Julian says there was a period of time where these were marked auto. I
  suppose that I installed during this window, and now some dependency
  change meant that as far as apt was concerned they weren't required
  any more.

  Can we please consider never proposing these packages for autoremoval?
  apt has NeverAutoRemove for this which could be used, or some other
  appropriate method.

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

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


[Touch-packages] [Bug 1897932] [NEW] systemd-repart not packaged

2020-09-30 Thread Iain Lane
Public bug reported:

systemd-repart is not (as of 246.6-1ubuntu1) packaged in the
Ubuntu/Debian packages of systemd - probably because it has an extra
dependency?

I'd like to use it in our new raspberry pi images where we don't have
cloud-init installed. We're already using systemd-growfs, but we are
missing the nice partition resizing part (so are using cloud-initramfs-
growroot).

Could you please consider enabling it? In another binary package - so it
can have extra deps - would be just fine by me.

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

** Summary changed:

- systemd-repart not packages
+ systemd-repart not packaged

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

Title:
  systemd-repart not packaged

Status in systemd package in Ubuntu:
  New

Bug description:
  systemd-repart is not (as of 246.6-1ubuntu1) packaged in the
  Ubuntu/Debian packages of systemd - probably because it has an extra
  dependency?

  I'd like to use it in our new raspberry pi images where we don't have
  cloud-init installed. We're already using systemd-growfs, but we are
  missing the nice partition resizing part (so are using cloud-
  initramfs-growroot).

  Could you please consider enabling it? In another binary package - so
  it can have extra deps - would be just fine by me.

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

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


[Touch-packages] [Bug 1896577] Re: FFE: new upstream release 20.2 and migrate to llvm 11

2020-09-29 Thread Iain Lane
Already said on IRC, but mentioning here for other RT members:

I'd like to see (1) an analysis of the risks of this update, and (2) a
description of what testing you've done, please.

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

Title:
  FFE: new upstream release 20.2 and migrate to llvm 11

Status in mesa package in Ubuntu:
  New

Bug description:
  Mesa 20.2.0 has been delayed by upstream, but we still want it in
  20.10. It's currrently at rc4, final was supposed to be out a month
  ago. It's been in debian experimental since rc1.

  The packaging in debian also migrates to use llvm 11.

  packages for groovy are available on ppa:canonical-x/x-staging

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

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


[Touch-packages] [Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm

2020-09-25 Thread Iain Lane
Yeah, sorry, I don't think that's a reproducer for the bug. You killed
dbus, gdm and everything else, and they obligingly died on you. :)

My feeling is that this bug is about a deadlock that somehow happens
when dbus and/or systemd are reloaded, possibly at the same time. It
looks like dbus stops responding to systemd, and so when it calls
GetNameOwner() to be able to watch type=dbus units, it gets no reply and
then decides to kill all type=dbus units, which is a lot of things. If
that's right, it's most likely to be a dbus bug that it can get into
this state. But I'm personally at a bit of a loss as to how to approach
it without being able to reproduce.

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

Title:
  dbus timeout-ed during an upgrade, taking services down including gdm

Status in systemd:
  New
Status in accountsservice package in Ubuntu:
  Invalid
Status in dbus package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Invalid
Status in accountsservice source package in Focal:
  Invalid
Status in dbus source package in Focal:
  Incomplete
Status in gnome-shell source package in Focal:
  Invalid

Bug description:
  This morning I found my computer on the login screen.
  But not the one of the screen log, no a new one - so something must have 
crashed.

  Logging in again confirmed that all apps were gone and the gnome shell
  was brought down what seems like triggered by a background update o
  accountsservice.

  As always things are not perfectly clear :-/
  The following goes *back* in time through my logs one by one.

  Multiple apps crashed at 06:09, but we will find later that this is a follow 
on issue of the underlying gnome/X/... recycling.
  -rw-r-  1 paelzer  whoopsie 52962868 Apr  8 06:09 
_usr_bin_konversation.1000.crash
  -rw-r-  1 paelzer  whoopsie   986433 Apr  8 06:09 
_usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash

  
  rdkit was failing fast and giving up (that will be a different bug, it just 
seems broken on my system):
  Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling 
Policy Service.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully called 
chroot.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully dropped 
privileges.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully limited 
resources.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: pthread_create failed: 
Resource temporarily unavailable
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Canary thread running.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Exiting canary thread.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoting known real-time 
threads.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoted 0 threads.
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Main process 
exited, code=exited, status=1/FAILURE
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with 
result 'exit-code'.
  Apr 08 06:10:13 Keschdeichel dbus-daemon[1208]: [system] Activating via 
systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.1176' (uid=121 pid=>
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Start request 
repeated too quickly.
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with 
result 'exit-code'.
  Apr 08 06:10:13 Keschdeichel systemd[1]: Failed to start RealtimeKit 
Scheduling Policy Service.
  Apr 08 06:10:13 Keschdeichel bluetoothd[1729331]: Bluetooth daemon 5.53

  
  But that already was only triggered by a gnome restart that kicked of earlier:

  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Started GNOME Shell on Wayland.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Shell on 
Wayland.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session 
is initialized.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Wayland 
Session.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session 
(session: gnome-login).

  
  X was recycleing before:
  Apr 08 06:09:19 Keschdeichel systemd[10683]: Stopping GNOME Shell on X11...
  ...
  Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (EE) 
systemd-logind: ReleaseControl failed: Unknown object 
'/org/freedesktop/login1/session/_32'.
  Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (II) Server 
terminated successfully (0). Closing log file.

  
  It seems like some internal service broke and everything that followed was a 
secondary issue to that:
  Apr 08 06:09:19 Keschdeichel systemd[1]: NetworkManager.service: Unexpected 
error response from GetNameOwner(): Connection terminated
  Apr 08 06:09:19 Keschdeichel systemd[1]: wpa_supplicant.service: Unexpected 
error 

[Touch-packages] [Bug 1894195] Re: FFe: Merge iptables 1.8.5-3 (main) from Debian sid (main)

2020-09-25 Thread Iain Lane
Right, yes, please do go ahead. It was pointed out before that this
would be desirable after we switched away from -legacy due to the nature
of the fixes.

I had thought from the diff of debian/tests/control that the test
coverage of the nft backend was being reduced, but then I took a look at
https://salsa.debian.org/pkg-netfilter-team/pkg-
iptables/-/blob/master/debian/tests/control and actually both are being
tested explicitly, so that seems sensible.

I'm certainly not fully competent to assess the entire impact here. A
suggestion: maybe the server team could be asked to give it a round of
extra testing / eyes after upload?

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

Title:
  FFe: Merge iptables 1.8.5-3 (main) from Debian sid (main)

Status in iptables package in Ubuntu:
  New

Bug description:
  Please merge iptables 1.8.5-3 (main) from Debian sid (main)

  Explanation of FeatureFreeze exception:
  Current iptables is using the same upstream version in focal, which had 
problems with the nft backend and was then reverted to the legacy backend.
  1.8.5 has many fixes for the nft backend. For example these Debian bugs are 
fixed in 1.8.5:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950535
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961117
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968457
  Please merge it.

  Changelog entries since current groovy version 1.8.4-3ubuntu3:

  iptables (1.8.5-3) unstable; urgency=medium

    * [2d587e5] src:iptables: bump build-dep version on libnftnl to
  1.1.6

   -- Arturo Borrero Gonzalez   Tue, 25 Aug 2020
  11:56:55 +0200

  iptables (1.8.5-2) unstable; urgency=medium

    [ Alberto Molina Coballes ]
    * [d90516d] d/control: modify breaks and replaces fields (Closes: #949576)
    * [4754a45] d/not-installed: arch independ files
    * [780330f] d/tests/control: Run iptables-legacy-* tests explicitly

    [ Arturo Borrero Gonzalez ]
    * [6fb6557] d/patches: add -upstream-fix-xtables-translate.patch
  (Closes: #962724)

   -- Arturo Borrero Gonzalez   Wed, 24 Jun 2020
  10:56:19 +0200

  iptables (1.8.5-1) unstable; urgency=medium

    [ Debian Janitor ]
    * [c3deeb3] Wrap long lines in changelog entries: 1.8.2-1, 1.8.0-1~exp1,
    1.6.0-1.
    * [214468e] Update standards version to 4.5.0, no changes needed.

    [ Arturo Borrero Gonzalez ]
    * [eb1d7c5] New upstream version 1.8.5 (Closes: #950535)
    * [7a119db] d/patches: drop all patches
    * [ec63c87] libxtables12.symbols: add new symbol
    * [4056ce6] iptables: bump debhelper-compat to 13

   -- Arturo Borrero Gonzalez   Thu, 04 Jun 2020
  13:33:22 +0200

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

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


[Touch-packages] [Bug 1895060] Re: [FFe] apparmor 3 upstream release

2020-09-21 Thread Iain Lane
OK, go for it!

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

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

Title:
  [FFe] apparmor 3 upstream release

Status in apparmor package in Ubuntu:
  Confirmed

Bug description:
  As per the draft upstream release notes[1]:

  AppArmor 3.0 is a major new release of the AppArmor user space that makes
  an important change to policy development and support. Its focus is
  transitioning policy to the new features ABI and as such other new features
  have been limited.

  Apprmor 3.0 is a bridge release between older AppArmor 2.x policy and the
  newer AppArmor 3 style policy which requires the declaration of a features
  abi. As such AppArmor 3.0 will be a short lived release, and will not
  receive long term support. The following AppArmor 3.1 feature release is
  planned to be a regular release, please take this into account when
  including AppArmor 3.0 into a distro release.

  As such, Ubuntu 20.10 provides a great opportunity to introduce AppArmor3
  to Ubuntu and provide these new capabilities to users and system
  administrators. The short support lifespan of Ubuntu 20.10 ensures that
  there is alignment with the limited support lifetime of AppArmor 3.0 from
  upstream, whilst giving good exposure and opportunity to test and exercise
  the new features in AppArmor 3.x on the road to Ubuntu 22.04. A highlight
  of new features provided by AppArmor 3.0 include:

  - Policy now must declare the feature abi it was developed for if it is to
    use any new features. This ensures that old policy will not become
    incompatible with new kernels that support additional AppArmor features.
  - The use of profile names that are based on pathnames are deprecated.
  - Support for new kernel features (requires appropriate features abi
    tagging in policy)
    - upstream v8 network socket rules
    - xattr attachment conditionals
    - capabilities PERFMON and BPF
  - Improved compiler warnings and semantic checks
  - aa-status rewritten in C (previously was python) with additional features
    - supports use in systems/images where python is not available
    - supports kill, unconfined and mixed profile modes
  - Rewritten aa-notify (previously was perl, now python3)
    - shared backend with other python tools
    - support use of aa.CONFDIR instead of hard coded /etc/apparmor
    - improved message layout
  - Improved support for kernels that support LSM stacking
  - New utility aa-features-abi to extract and work with kernel abi features
  - New utility aa-load to load binary policy without calling the
    apparmor_parser
  - Support for profile modes
    - enforce (default when no mode flag is supplied)
    - kill (experimental)
    - unconfined (experimental)

  The use of the new AppArmor profile feature ABI includes a default
  configuration (for the Ubuntu packaged version of AppArmor proposed in this
  FFE) for the AppArmor features within the 5.4 Linux kernel - this ensures
  that all profiles provided in AppArmor3 for groovy will conform to this
  feature set and that upgrades to the kernel version (say to 5.8) that may
  include newer AppArmor confinement features will not result in additional
  policy denials as a result (since say the existing profile did not specify
  a rule for a new AppArmor feature which is now supported by the upgraded
  kernel). This ensures that there will be no regressions in application
  behaviour as a result of AppArmor kernel feature upgrades.

  TESTING

  This has been extensively tested by the security team - this includes
  following the documented Ubuntu merges test plan[2] for AppArmor and the
  extensive QA Regression Tests[3] for AppArmor as well. This ensures that the
  various applications that make heavy use of AppArmor (LXD, docker, lxc,
  dbus, libvirt, snapd etc) have all been exercised and no regressions have
  been observed. All tests have passed and demonstrated both apparmor and the
  various applications that use it to be working as expected.

  BUILD LOGS

  This is currently uploaded to groovy-proposed, build logs can be found on
  Launchpad at:
  https://launchpad.net/ubuntu/+source/apparmor/3.0.0~beta1-0ubuntu1

  INSTALL LOG

  See attached
  
(https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1895060/+attachment/5411197/+files
  /groovy-proposed-apparmor-install.log) for a log showing install of
  the packages from groovy-proposed

  [1] https://gitlab.com/apparmor/apparmor/-/wikis/Release_Notes_3.0
  [2] https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor
  [3] 
https://git.launchpad.net/qa-regression-testing/tree/scripts/test-apparmor.py

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

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

[Touch-packages] [Bug 1895060] Re: [FFe] apparmor 3 upstream release

2020-09-21 Thread Iain Lane
Just to confirm, your intention (barring bugs) is that there should be
no breakage for existing apparmor profiles and consumers of the
rewritten tools?

If so, I think this should still be fine at this stage.

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

Title:
  [FFe] apparmor 3 upstream release

Status in apparmor package in Ubuntu:
  New

Bug description:
  As per the draft upstream release notes[1]:

  AppArmor 3.0 is a major new release of the AppArmor user space that makes
  an important change to policy development and support. Its focus is
  transitioning policy to the new features ABI and as such other new features
  have been limited.

  Apprmor 3.0 is a bridge release between older AppArmor 2.x policy and the
  newer AppArmor 3 style policy which requires the declaration of a features
  abi. As such AppArmor 3.0 will be a short lived release, and will not
  receive long term support. The following AppArmor 3.1 feature release is
  planned to be a regular release, please take this into account when
  including AppArmor 3.0 into a distro release.

  As such, Ubuntu 20.10 provides a great opportunity to introduce AppArmor3
  to Ubuntu and provide these new capabilities to users and system
  administrators. The short support lifespan of Ubuntu 20.10 ensures that
  there is alignment with the limited support lifetime of AppArmor 3.0 from
  upstream, whilst giving good exposure and opportunity to test and exercise
  the new features in AppArmor 3.x on the road to Ubuntu 22.04. A highlight
  of new features provided by AppArmor 3.0 include:

  - Policy now must declare the feature abi it was developed for if it is to
    use any new features. This ensures that old policy will not become
    incompatible with new kernels that support additional AppArmor features.
  - The use of profile names that are based on pathnames are deprecated.
  - Support for new kernel features (requires appropriate features abi
    tagging in policy)
    - upstream v8 network socket rules
    - xattr attachment conditionals
    - capabilities PERFMON and BPF
  - Improved compiler warnings and semantic checks
  - aa-status rewritten in C (previously was python) with additional features
    - supports use in systems/images where python is not available
    - supports kill, unconfined and mixed profile modes
  - Rewritten aa-notify (previously was perl, now python3)
    - shared backend with other python tools
    - support use of aa.CONFDIR instead of hard coded /etc/apparmor
    - improved message layout
  - Improved support for kernels that support LSM stacking
  - New utility aa-features-abi to extract and work with kernel abi features
  - New utility aa-load to load binary policy without calling the
    apparmor_parser
  - Support for profile modes
    - enforce (default when no mode flag is supplied)
    - kill (experimental)
    - unconfined (experimental)

  The use of the new AppArmor profile feature ABI includes a default
  configuration (for the Ubuntu packaged version of AppArmor proposed in this
  FFE) for the AppArmor features within the 5.4 Linux kernel - this ensures
  that all profiles provided in AppArmor3 for groovy will conform to this
  feature set and that upgrades to the kernel version (say to 5.8) that may
  include newer AppArmor confinement features will not result in additional
  policy denials as a result (since say the existing profile did not specify
  a rule for a new AppArmor feature which is now supported by the upgraded
  kernel). This ensures that there will be no regressions in application
  behaviour as a result of AppArmor kernel feature upgrades.

  TESTING

  This has been extensively tested by the security team - this includes
  following the documented Ubuntu merges test plan[2] for AppArmor and the
  extensive QA Regression Tests[3] for AppArmor as well. This ensures that the
  various applications that make heavy use of AppArmor (LXD, docker, lxc,
  dbus, libvirt, snapd etc) have all been exercised and no regressions have
  been observed. All tests have passed and demonstrated both apparmor and the
  various applications that use it to be working as expected.

  BUILD LOGS

  This is currently uploaded to groovy-proposed, build logs can be found on
  Launchpad at:
  https://launchpad.net/ubuntu/+source/apparmor/3.0.0~beta1-0ubuntu1

  INSTALL LOG

  See attached
  
(https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1895060/+attachment/5411197/+files
  /groovy-proposed-apparmor-install.log) for a log showing install of
  the packages from groovy-proposed

  [1] https://gitlab.com/apparmor/apparmor/-/wikis/Release_Notes_3.0
  [2] https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor
  [3] 
https://git.launchpad.net/qa-regression-testing/tree/scripts/test-apparmor.py

To manage notifications about this bug go to:

[Touch-packages] [Bug 1891632] Re: The network manager does not check the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE bit

2020-09-16 Thread Iain Lane
I've uploaded, thanks.

But the regression potential section needs improving, "None" isn't
enough. Please improve it to discuss where people should focus their
attention / testing.

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

Title:
  The network manager does not check the
  NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE bit

Status in OEM Priority Project:
  New
Status in OEM Priority Project focal series:
  Invalid
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Focal:
  In Progress

Bug description:
  [Impact]

   In some cases, the wow is not configured and the
  NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set (for to disable
  management of wake-on-LAN in NetworkManager).

   The network manager only checks the NM_SETTING_WIRELESS_WAKE_ON_WLAN_NONE 
bit.
   But, the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE does not be check.
   So, the management of wake-on-LAN still is done by NetworkManager.

  [Test Case]

   On a machine with killer 500s Wi-Fi and install the Qualcomm's driver.
   Step 1. Enter suspend (s2idle)
   Setp 2. Resume from suspend

   After resume from suspend, the Wi-Fi functiall still is normal.

   You can download the kernel and linux-firmware that backport the Qucalcomm's 
dirver fro focal from below link:
   https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1879633

  [Regression Potential]

   * No potential regressions.

  [Other Info]
   
   * None

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1891632/+subscriptions

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


[Touch-packages] [Bug 1891632] Re: The network manager does not check the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE bit

2020-09-16 Thread Iain Lane
** Also affects: oem-priority/focal
   Importance: Undecided
   Status: New

** Changed in: oem-priority/focal
   Status: New => Invalid

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

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

** Changed in: network-manager (Ubuntu Focal)
   Status: New => In Progress

** Changed in: network-manager (Ubuntu Focal)
 Assignee: (unassigned) => Leon Liao (lihow731)

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

Title:
  The network manager does not check the
  NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE bit

Status in OEM Priority Project:
  New
Status in OEM Priority Project focal series:
  Invalid
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Focal:
  In Progress

Bug description:
  [Impact]

   In some cases, the wow is not configured and the
  NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set (for to disable
  management of wake-on-LAN in NetworkManager).

   The network manager only checks the NM_SETTING_WIRELESS_WAKE_ON_WLAN_NONE 
bit.
   But, the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE does not be check.
   So, the management of wake-on-LAN still is done by NetworkManager.

  [Test Case]

   On a machine with killer 500s Wi-Fi and install the Qualcomm's driver.
   Step 1. Enter suspend (s2idle)
   Setp 2. Resume from suspend

   After resume from suspend, the Wi-Fi functiall still is normal.

   You can download the kernel and linux-firmware that backport the Qucalcomm's 
dirver fro focal from below link:
   https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1879633

  [Regression Potential]

   * No potential regressions.

  [Other Info]
   
   * None

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1891632/+subscriptions

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


[Touch-packages] [Bug 1894838] Re: FFe: update to 2.4.53, fixing crash bugs

2020-09-15 Thread Iain Lane
Agreed that taking the unit which upstream has validated is more
sensible than backporting. Thanks for the detailed report. I think the
only thing which I would like to see in future is you saying that (and
how) you've tested it manually and spotted no regressions.

But go ahead this time.

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

Title:
  FFe: update to 2.4.53, fixing crash bugs

Status in openldap package in Ubuntu:
  Confirmed

Bug description:
  Groovy has openldap 2.4.51

  Upstream made two quick new releases after that: 2.4.52 and 2.4.53. A
  crash was reported in the mailing list:

  https://lists.openldap.org/hyperkitty/list/openldap-
  techni...@openldap.org/thread/NKOM6DI7RQY6FDLRZGSGYJSGONKIRFEP/

  """
  This segfault is due to a problem with the fix for ITS#9282 that went into 
  the OpenLDAP 2.4.51 and OpenLDAP 2.4.52 releases.  This is fixed in the 
  2.4.53 release (released today).
  """

  Almost all changes in 2.4.52 and 2.4.53 are bug fixes, but a few feathre 
changes/additions slipped through, hence this FFe:
  OpenLDAP 2.4.53 (2020/09/07)
  Added slapd syncrepl additional SYNC logging (ITS#9043)
  Fixed slapd syncrepl segfault on NULL cookie on REFRESH (ITS#9282)
  Fixed slapd syncrepl to use fresh connection on REFRESH fallback 
(ITS#9338)
  Fixed slapo-ppolicy race condition for pwdFailureTime (ITS#9302,ITS#9334)
  Build
  Require OpenSSL 1.0.2 or later (ITS#9323)
  Fixed libldap compilation issue with broken C compilers (ITS#9332)

  OpenLDAP 2.4.52 (2020/08/28)
  Added libldap LDAP_OPT_X_TLS_REQUIRE_SAN option (ITS#9318)
  Added libldap OpenSSL support for multiple EECDH curves (ITS#9054)
  Added slapd OpenSSL support for multiple EECDH curves (ITS#9054)
  Fixed librewrite malloc/free corruption (ITS#9249)
  Fixed libldap hang when using UDP and server down (ITS#9328)
  Fixed slapd syncrepl rare deadlock due to network issues (ITS#9324)
  Fixed slapd syncrepl regression that could trigger an assert (ITS#9329)
  Fixed slapd-mdb index error with collapsed range (ITS#9135)

  I grouped the changes with links to the bug reports:
  Replication fixes:
  Fixed slapd syncrepl segfault on NULL cookie on REFRESH 
(https://bugs.openldap.org/show_bug.cgi?id=9282)
  Fixed slapd syncrepl to use fresh connection on REFRESH fallback 
(https://bugs.openldap.org/show_bug.cgi?id=9338)
  Fixed slapd syncrepl rare deadlock due to network issues 
(https://bugs.openldap.org/show_bug.cgi?id=9324)
  Fixed slapd syncrepl regression that could trigger an assert 
(https://bugs.openldap.org/show_bug.cgi?id=9329)

  Features and other non-fixes changes:
  Added slapd syncrepl additional SYNC logging 
(https://bugs.openldap.org/show_bug.cgi?id=9043)
  Require OpenSSL 1.0.2 or later 
(https://bugs.openldap.org/show_bug.cgi?id=9323)
  Added libldap LDAP_OPT_X_TLS_REQUIRE_SAN option 
(https://bugs.openldap.org/show_bug.cgi?id=9318)
  Added libldap OpenSSL support for multiple EECDH curves 
(https://bugs.openldap.org/show_bug.cgi?id=9054)
  Added slapd OpenSSL support for multiple EECDH curves 
(https://bugs.openldap.org/show_bug.cgi?id=9054)

  Other fixes:
  Fixed slapo-ppolicy race condition for pwdFailureTime 
(https://bugs.openldap.org/show_bug.cgi?id=9302,https://bugs.openldap.org/show_bug.cgi?id=9334)
  Fixed libldap compilation issue with broken C compilers 
(https://bugs.openldap.org/show_bug.cgi?id=9332)
  Fixed librewrite malloc/free corruption 
(https://bugs.openldap.org/show_bug.cgi?id=9249)
  Fixed libldap hang when using UDP and server down 
(https://bugs.openldap.org/show_bug.cgi?id=9328)
  Fixed slapd-mdb index error with collapsed range 
(https://bugs.openldap.org/show_bug.cgi?id=9135)

  
  PPA with a groovy proposed and all arches test build (still ongoing as I 
write this): 
https://launchpad.net/~ahasenack/+archive/ubuntu/openldap-2453/+packages

  I believe a backport of that many fixes is riskier than an update to
  the new upstream version at this point.

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

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


[Touch-packages] [Bug 1894619] Re: [2.82 regression] router announcements have 'forever' lifetime by default

2020-09-09 Thread Iain Lane
I think either of the patches is probably fine, no idea what any
upstream reviewer will prefer.

I guess it would be good to upload one of them sooner rather than later
though, to (1) unbreak dnsmasq, (2) unblock network-manager.

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

Title:
  [2.82 regression] router announcements have 'forever' lifetime by
  default

Status in dnsmasq package in Ubuntu:
  Triaged

Bug description:
  The default lifetime was changed to 1 day in 2.82 in the change
  corresponding to this changelog entry:

  Change default lease time for DHCPv6 to one day.

  Fine, but the same commit also did this:

Alter calculation of preferred and valid times in router
advertisements, so that these do not have a floor applied
of the lease time in the dhcp-range if this is not explicitly
specified and is merely the default.

  And that change is buggy and causes advertisements to have infinite
  lifetime, when you are using the default.

  See this thread

http://lists.thekelleys.org.uk/pipermail/dnsmasq-
  discuss/2020q3/014341.html

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

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


[Touch-packages] [Bug 1881699] Re: No analog output

2020-09-08 Thread Iain Lane
there's an updated kernel in that bug, jibel can you test it please to
confirm if this is a dupe or not?

** Tags removed: rls-gg-incoming

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

Title:
  No analog output

Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After a fresh boot and login, there is no analog output. Only HDMI and 
bluetooth are available.
  It becomes available when I kill pulseaudio with 'pulseaudio -k' but the 
sound indicator only shows 'dummy' output and I cannot control the output from 
the sound settings or the sound indicator.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.1-1ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu36
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  j-lallement  184080 F pulseaudio
   /dev/snd/controlC1:  j-lallement  184080 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun  2 06:32:09 2020
  InstallationDate: Installed on 2020-05-31 (1 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200527)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/21/2019
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: FNCML357.0032.2019.1021.1624
  dmi.board.asset.tag: Default string
  dmi.board.name: NUC10i7FNB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: K61360-302
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 35
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrFNCML357.0032.2019.1021.1624:bd10/21/2019:svnIntel(R)ClientSystems:pnNUC10i7FNH:pvrK61081-302:rvnIntelCorporation:rnNUC10i7FNB:rvrK61360-302:cvnIntelCorporation:ct35:cvr2.0:
  dmi.product.family: FN
  dmi.product.name: NUC10i7FNH
  dmi.product.sku: BXNUC10i7FNH
  dmi.product.version: K61081-302
  dmi.sys.vendor: Intel(R) Client Systems
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu36
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  j-lallement   3669 F pulseaudio
   /dev/snd/controlC0:  j-lallement   3669 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-05-31 (1 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200527)
  MachineType: Intel(R) Client Systems NUC10i7FNH
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: pulseaudio 1:13.99.1-1ubuntu3
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_huyn9u@/vmlinuz-5.4.0-26-generic 
root=ZFS=rpool/ROOT/ubuntu_huyn9u ro snd-intel-dspcfg.dsp_driver=1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-26-generic N/A
   linux-backports-modules-5.4.0-26-generic  N/A
   linux-firmware1.187
  Tags:  groovy
  Uname: Linux 5.4.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/21/2019
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: FNCML357.0032.2019.1021.1624
  dmi.board.asset.tag: Default string
  dmi.board.name: NUC10i7FNB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: K61360-302
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 35
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrFNCML357.0032.2019.1021.1624:bd10/21/2019:svnIntel(R)ClientSystems:pnNUC10i7FNH:pvrK61081-302:rvnIntelCorporation:rnNUC10i7FNB:rvrK61360-302:cvnIntelCorporation:ct35:cvr2.0:
  dmi.product.family: FN
  dmi.product.name: NUC10i7FNH
  dmi.product.sku: BXNUC10i7FNH
  dmi.product.version: K61081-302
  dmi.sys.vendor: Intel(R) Client Systems

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

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


[Touch-packages] [Bug 1881699] Re: No analog output

2020-09-08 Thread Iain Lane
please re-add the tag if it's not

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

Title:
  No analog output

Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After a fresh boot and login, there is no analog output. Only HDMI and 
bluetooth are available.
  It becomes available when I kill pulseaudio with 'pulseaudio -k' but the 
sound indicator only shows 'dummy' output and I cannot control the output from 
the sound settings or the sound indicator.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.1-1ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu36
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  j-lallement  184080 F pulseaudio
   /dev/snd/controlC1:  j-lallement  184080 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun  2 06:32:09 2020
  InstallationDate: Installed on 2020-05-31 (1 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200527)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/21/2019
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: FNCML357.0032.2019.1021.1624
  dmi.board.asset.tag: Default string
  dmi.board.name: NUC10i7FNB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: K61360-302
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 35
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrFNCML357.0032.2019.1021.1624:bd10/21/2019:svnIntel(R)ClientSystems:pnNUC10i7FNH:pvrK61081-302:rvnIntelCorporation:rnNUC10i7FNB:rvrK61360-302:cvnIntelCorporation:ct35:cvr2.0:
  dmi.product.family: FN
  dmi.product.name: NUC10i7FNH
  dmi.product.sku: BXNUC10i7FNH
  dmi.product.version: K61081-302
  dmi.sys.vendor: Intel(R) Client Systems
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu36
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  j-lallement   3669 F pulseaudio
   /dev/snd/controlC0:  j-lallement   3669 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-05-31 (1 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200527)
  MachineType: Intel(R) Client Systems NUC10i7FNH
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: pulseaudio 1:13.99.1-1ubuntu3
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_huyn9u@/vmlinuz-5.4.0-26-generic 
root=ZFS=rpool/ROOT/ubuntu_huyn9u ro snd-intel-dspcfg.dsp_driver=1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-26-generic N/A
   linux-backports-modules-5.4.0-26-generic  N/A
   linux-firmware1.187
  Tags:  groovy
  Uname: Linux 5.4.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/21/2019
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: FNCML357.0032.2019.1021.1624
  dmi.board.asset.tag: Default string
  dmi.board.name: NUC10i7FNB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: K61360-302
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 35
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrFNCML357.0032.2019.1021.1624:bd10/21/2019:svnIntel(R)ClientSystems:pnNUC10i7FNH:pvrK61081-302:rvnIntelCorporation:rnNUC10i7FNB:rvrK61360-302:cvnIntelCorporation:ct35:cvr2.0:
  dmi.product.family: FN
  dmi.product.name: NUC10i7FNH
  dmi.product.sku: BXNUC10i7FNH
  dmi.product.version: K61081-302
  dmi.sys.vendor: Intel(R) Client Systems

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

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


[Touch-packages] [Bug 1894619] Re: [2.82 regression] router announcements have 'forever' lifetime by default

2020-09-07 Thread Iain Lane
I proposed a patch on the thread, waiting for feedback.

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

Title:
  [2.82 regression] router announcements have 'forever' lifetime by
  default

Status in dnsmasq package in Ubuntu:
  Triaged

Bug description:
  The default lifetime was changed to 1 day in 2.82 in the change
  corresponding to this changelog entry:

  Change default lease time for DHCPv6 to one day.

  Fine, but the same commit also did this:

Alter calculation of preferred and valid times in router
advertisements, so that these do not have a floor applied
of the lease time in the dhcp-range if this is not explicitly
specified and is merely the default.

  And that change is buggy and causes advertisements to have infinite
  lifetime, when you are using the default.

  See this thread

http://lists.thekelleys.org.uk/pipermail/dnsmasq-
  discuss/2020q3/014341.html

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

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


[Touch-packages] [Bug 1894619] [NEW] [2.82 regression] router announcements have 'forever' lifetime by default

2020-09-07 Thread Iain Lane
Public bug reported:

The default lifetime was changed to 1 day in 2.82 in the change
corresponding to this changelog entry:

Change default lease time for DHCPv6 to one day.

Fine, but the same commit also did this:

Alter calculation of preferred and valid times in router
advertisements, so that these do not have a floor applied
of the lease time in the dhcp-range if this is not explicitly
specified and is merely the default.

And that change is buggy and causes advertisements to have infinite
lifetime, when you are using the default.

See this thread

  http://lists.thekelleys.org.uk/pipermail/dnsmasq-
discuss/2020q3/014341.html

** Affects: dnsmasq (Ubuntu)
 Importance: High
 Status: Triaged


** Tags: update-excuse

** Tags added: update-excuse

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

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

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

Title:
  [2.82 regression] router announcements have 'forever' lifetime by
  default

Status in dnsmasq package in Ubuntu:
  Triaged

Bug description:
  The default lifetime was changed to 1 day in 2.82 in the change
  corresponding to this changelog entry:

  Change default lease time for DHCPv6 to one day.

  Fine, but the same commit also did this:

Alter calculation of preferred and valid times in router
advertisements, so that these do not have a floor applied
of the lease time in the dhcp-range if this is not explicitly
specified and is merely the default.

  And that change is buggy and causes advertisements to have infinite
  lifetime, when you are using the default.

  See this thread

http://lists.thekelleys.org.uk/pipermail/dnsmasq-
  discuss/2020q3/014341.html

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

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


[Touch-packages] [Bug 1893958] Re: [FFe] Please accept iptables 1.8.4-3ubuntu3 switching to nftables backend

2020-09-03 Thread Iain Lane
** Changed in: iptables (Ubuntu)
   Status: New => Confirmed

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

Title:
  [FFe] Please accept iptables 1.8.4-3ubuntu3 switching to nftables
  backend

Status in iptables package in Ubuntu:
  Confirmed

Bug description:
  The change is a planned change for this development cycle and the fix
  has been tested as described in LP: #1887186 and
  https://lists.ubuntu.com/archives/ubuntu-devel/2020-August/041142.html
  .

  
  Changes:
   iptables (1.8.4-3ubuntu3) groovy; urgency=medium
   .
 * Swap alternative priority and prefer nftables backend over legacy
   (LP: #1887186)

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

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


[Touch-packages] [Bug 1893958] Re: [FFe] Please accept iptables 1.8.4-3ubuntu3 switching to nftables backend

2020-09-03 Thread Iain Lane
Have you checked with the LXD team that they are happy with this?

If so, ack from me.

If 1.8.5 fixes bugs then we should take that for sure - please could you
make sure to do that (can be later, but not much later)?

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

Title:
  [FFe] Please accept iptables 1.8.4-3ubuntu3 switching to nftables
  backend

Status in iptables package in Ubuntu:
  New

Bug description:
  The change is a planned change for this development cycle and the fix
  has been tested as described in LP: #1887186 and
  https://lists.ubuntu.com/archives/ubuntu-devel/2020-August/041142.html
  .

  
  Changes:
   iptables (1.8.4-3ubuntu3) groovy; urgency=medium
   .
 * Swap alternative priority and prefer nftables backend over legacy
   (LP: #1887186)

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

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


[Touch-packages] [Bug 1883694] Re: [SRU] New upstream release 2.64.3

2020-07-06 Thread Iain Lane
I've retried them all and it's green now.

Just verified this SRU in a VM. I upgraded to the proposed glib2.0 and
then tried logging in and launching and using various GNOME
applications.

  - gedit
  - epiphany-browser (to test glib-networking & webkit)
  - totem (GStreamer)

All seems good to me.

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

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

Title:
  [SRU] New upstream release 2.64.3

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Focal:
  Fix Committed

Bug description:
  [ Description ]

  Take this new upstrem stable release.

  +glib2.0 (2.64.3-1~ubuntu20.04.1) UNRELEASED; urgency=medium
  +
  +  * No-change backport from unstable / groovy to focal.
  +
  + -- Iain Lane   Tue, 16 Jun 2020 11:53:34 +0100
  +
  +glib2.0 (2.64.3-1) unstable; urgency=medium
  +
  +  * Team upload
  +
  +  [ Laurent Bigonville ]
  +  * Drop the libgio-fam package, and install the fam GIO plugin in
  +libglib2.0-0 on Hurd ports. See: #885011 (Closes: #875915)
  +  * Stop building the libgio-fam package on kFreeBSD ports.
  +It is no longer necessary now that gkqueuefilemonitor is available.
  +
  +  [ Simon McVittie ]
  +  * Clarify changelog entry regarding Hurd and kFreeBSD
  +  * New upstream stable release
  +
  + -- Simon McVittie   Fri, 29 May 2020 20:24:33 +0100

  The gio-fam related changes do not affect Ubuntu, as they are for
  hurd/kfreebsd only.

  Upstream NEWS diff:

  * Stability improvements for various unit tests

  * Bugs fixed:
   - #1954 gdbus-server-auth intermittent failure
   - #2094 Deprecation warnings when compiling with 
-DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_28 
-DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_28
   - !1470 Backport !1440 -Wformat-nonliteral fixes to glib-2-64
   - !1471 Backport !1448 memory monitor test dependency fixes to glib-2-64
   - !1473 CI: Switch to new Windows runners (2.64)
   - !1478 Backport !1477 D-Bus keyring handling fixes to glib-2-64
   - !1483 Backport !1481 “array: fix corrupt state of GPtrArray after 
g_ptr_array_extend_and_steal()” to glib-2-64
   - !1484 Backport !1480 “CI: Make sure we use meson 0.49.2 in MSYS2” to 
glib-2-64
   - !1486 Backport !1472 “gthread: ignore deprecated declarations in static 
inline functions” to glib-2-64
   - !1495 Backport !1493 “meson: Remove stray ], in O_DIRECTORY check” to 
glib-2-64
   - !1501 Backport !1439 “Fix stpcpy() detection“ to glib-2-64

  * Translation updates:
   - Chinese (Taiwan)
   - German

  [ QA ]

  Upstream release, so QA already performed by maintainers

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

  This upload will trigger many autopkgtests that we expect to not be
  regressed by this upload.

  [ Regression potential ]

  Various fixes in multiple places so multiple apps could be affected.
  Pretty much all parts of GNOME use GLib, so test anything in the
  desktop that you can.

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

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


[Touch-packages] [Bug 1860620] Re: ubuntu-desktop-minimal should not depend on mysql libs

2020-06-30 Thread Iain Lane
I’m not sure if depending on a library and -common (the initial apt log
shows the client and server themselves were *not* installed) is a
particular problem, but if so, this is coming from libsnmp35.

** Package changed: ubuntu-meta (Ubuntu) => net-snmp (Ubuntu)

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

Title:
  ubuntu-desktop-minimal should not depend on mysql libs

Status in net-snmp package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 20.04 I decided to remove packages that I don't
  need or use.

  I was surprised to find that mysql client, server and common packages
  were installed, as I could not remember having installed mysql -- I
  don't use it or develop for it...

  When I removed them, ubuntu-desktop-minimal went along for the ride:

  c@slate:~$ sudo apt-get purge -y mysql-client-core-5.7 mysql-common 
mysql-server-core-5.7 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Package 'mysql-client-core-5.7' is not installed, so not removed
  Package 'mysql-server-core-5.7' is not installed, so not removed
  The following package was automatically installed and is no longer required:
libgsound0
  Use 'sudo apt autoremove' to remove it.
  The following packages will be REMOVED:
colord* gnome-control-center* libmysqlclient21* libsane* libsnmp30* 
mysql-common* ubuntu-desktop-minimal*
  0 upgraded, 0 newly installed, 7 to remove and 0 not upgraded.
  After this operation, 28.4 MB disk space will be freed.
  (Reading database ... 381127 files and directories currently installed.)
  Removing ubuntu-desktop-minimal (1.443) ...
  Removing gnome-control-center (1:3.34.1-1ubuntu3) ...
  Removing colord (1.4.4-1ubuntu1) ...
  Removing libsane:amd64 (1.0.27-3.2ubuntu3) ...
  Removing libsnmp30:amd64 (5.7.3+dfsg-5ubuntu6) ...
  Removing libmysqlclient21:amd64 (8.0.18-0ubuntu5) ...
  Removing mysql-common (5.8+1.0.5ubuntu2) ...
  Processing triggers for mime-support (3.64ubuntu1) ...
  Processing triggers for gnome-menus (3.32.0-1ubuntu1) ...
  Processing triggers for libglib2.0-0:amd64 (2.63.3-1) ...
  Processing triggers for libc-bin (2.30-0ubuntu3) ...
  Processing triggers for man-db (2.9.0-2) ...
  Processing triggers for dbus (1.12.16-2ubuntu2) ...
  Processing triggers for udev (244-3ubuntu1) ...
  Processing triggers for desktop-file-utils (0.24-1ubuntu1) ...
  (Reading database ... 380812 files and directories currently installed.)
  Purging configuration files for mysql-common (5.8+1.0.5ubuntu2) ...
  Purging configuration files for colord (1.4.4-1ubuntu1) ...

  And, reinstalling ubuntu-desktop-minimal wants to brings them back,
  even with recommends and suggests turned off:

  c@slate:~$ sudo apt install ubuntu-desktop-minimal --no-install-recommends 
--no-install-
  --no-install-recommends  --no-install-suggests
  c@slate:~$ sudo apt install ubuntu-desktop-minimal --no-install-recommends 
--no-install-suggests 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following additional packages will be installed:
colord gnome-control-center libmysqlclient21 libsane libsnmp30 mysql-common
  Suggested packages:
colord-sensor-argyll gnome-user-share realmd libcanberra-gtk-module hplip
  Recommended packages:
gnome-online-accounts gnome-control-center-faces rygel | rygel-tracker 
sane-utils firefox hplip
  The following NEW packages will be installed:
colord gnome-control-center libmysqlclient21 libsane libsnmp30 mysql-common 
ubuntu-desktop-minimal
  0 upgraded, 7 newly installed, 0 to remove and 0 not upgraded.
  Need to get 0 B/6,114 kB of archives.
  After this operation, 28.4 MB of additional disk space will be used.
  Do you want to continue? [Y/n] 

  This seems really wrong... and looks like a transitive dependency, as
  I don't see it in apt-get showpkg ubuntu-desktop-minimal.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-desktop-minimal 1.443
  ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18
  Uname: Linux 4.15.0-74-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair binder_linux 
ashmem_linux
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 22 19:26:53 2020
  InstallationDate: Installed on 2018-08-26 (514 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-meta
  UpgradeStatus: Upgraded to focal on 2020-01-23 (0 days ago)

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

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

[Touch-packages] [Bug 1876693] Re: [SRU] New stable release 1.64.1

2020-06-16 Thread Iain Lane
Retried those tests, they are green now. Also tested per the description
and it was good.

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

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

Title:
  [SRU] New stable release 1.64.1

Status in gobject-introspection package in Ubuntu:
  Fix Released
Status in gobject-introspection source package in Focal:
  Fix Committed

Bug description:
  [ Description ]

  GNOME upstream have released a new stable version of gobject-
  introspection.

  Changes:

  1.64.1 - 2020-04-05
  ---

  * Replace calls to deprecated xml.etree.cElementTree removed in Python 3.9 
:mr:`202` (:user:`Stephen Gallagher `)
  * gimarshallingtests: Use g_assert_cmpfloat_with_epsilon. Fixes tests on some 
architectures :mr:`200` (:user:`Iain Lane `)

  [ QA ]

  GNOME has a micro release exception that covers this package.

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

  So we don't need to verify the fixes explicitly.

  Do this:

- Install the update, smoke test some of the reverse depends (apt rdepends 
libgirepository-1.0-1 and more importantly the indirect rdepends via python3-gi)
- Run "reverse-depends -b src:gobject-introspection" and test rebuild a few 
of them

  [ Regression potential ]

  g-i being broken will break pretty much the whole desktop, but you'd
  know that quite fast.

  The .py changes, if they're wrong or bad, could break the build of r
  -build-deps.

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

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


[Touch-packages] [Bug 1883694] [NEW] [SRU] New upstream release 2.64.3

2020-06-16 Thread Iain Lane
Public bug reported:

[ Description ]

Take this new upstrem stable release.

+glib2.0 (2.64.3-1~ubuntu20.04.1) UNRELEASED; urgency=medium
+
+  * No-change backport from unstable / groovy to focal.
+
+ -- Iain Lane   Tue, 16 Jun 2020 11:53:34 +0100
+
+glib2.0 (2.64.3-1) unstable; urgency=medium
+
+  * Team upload
+
+  [ Laurent Bigonville ]
+  * Drop the libgio-fam package, and install the fam GIO plugin in
+libglib2.0-0 on Hurd ports. See: #885011 (Closes: #875915)
+  * Stop building the libgio-fam package on kFreeBSD ports.
+It is no longer necessary now that gkqueuefilemonitor is available.
+
+  [ Simon McVittie ]
+  * Clarify changelog entry regarding Hurd and kFreeBSD
+  * New upstream stable release
+
+ -- Simon McVittie   Fri, 29 May 2020 20:24:33 +0100

The gio-fam related changes do not affect Ubuntu, as they are for
hurd/kfreebsd only.

Upstream NEWS diff:

* Stability improvements for various unit tests

* Bugs fixed:
 - #1954 gdbus-server-auth intermittent failure
 - #2094 Deprecation warnings when compiling with 
-DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_28 
-DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_28
 - !1470 Backport !1440 -Wformat-nonliteral fixes to glib-2-64
 - !1471 Backport !1448 memory monitor test dependency fixes to glib-2-64
 - !1473 CI: Switch to new Windows runners (2.64)
 - !1478 Backport !1477 D-Bus keyring handling fixes to glib-2-64
 - !1483 Backport !1481 “array: fix corrupt state of GPtrArray after 
g_ptr_array_extend_and_steal()” to glib-2-64
 - !1484 Backport !1480 “CI: Make sure we use meson 0.49.2 in MSYS2” to 
glib-2-64
 - !1486 Backport !1472 “gthread: ignore deprecated declarations in static 
inline functions” to glib-2-64
 - !1495 Backport !1493 “meson: Remove stray ], in O_DIRECTORY check” to 
glib-2-64
 - !1501 Backport !1439 “Fix stpcpy() detection“ to glib-2-64

* Translation updates:
 - Chinese (Taiwan)
 - German

[ QA ]

Upstream release, so QA already performed by maintainers

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

This upload will trigger many autopkgtests that we expect to not be
regressed by this upload.

[ Regression potential ]

Various fixes in multiple places so multiple apps could be affected.
Pretty much all parts of GNOME use GLib, so test anything in the desktop
that you can.

** Affects: glib2.0 (Ubuntu)
 Importance: Undecided
 Assignee: Iain Lane (laney)
 Status: Fix Released

** Affects: glib2.0 (Ubuntu Focal)
 Importance: Undecided
 Assignee: Iain Lane (laney)
 Status: In Progress

** Changed in: glib2.0 (Ubuntu)
   Status: New => Fix Released

** Changed in: glib2.0 (Ubuntu)
 Assignee: (unassigned) => Iain Lane (laney)

** Also affects: glib2.0 (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Changed in: glib2.0 (Ubuntu Focal)
   Status: New => In Progress

** Changed in: glib2.0 (Ubuntu Focal)
 Assignee: (unassigned) => Iain Lane (laney)

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

Title:
  [SRU] New upstream release 2.64.3

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Focal:
  In Progress

Bug description:
  [ Description ]

  Take this new upstrem stable release.

  +glib2.0 (2.64.3-1~ubuntu20.04.1) UNRELEASED; urgency=medium
  +
  +  * No-change backport from unstable / groovy to focal.
  +
  + -- Iain Lane   Tue, 16 Jun 2020 11:53:34 +0100
  +
  +glib2.0 (2.64.3-1) unstable; urgency=medium
  +
  +  * Team upload
  +
  +  [ Laurent Bigonville ]
  +  * Drop the libgio-fam package, and install the fam GIO plugin in
  +libglib2.0-0 on Hurd ports. See: #885011 (Closes: #875915)
  +  * Stop building the libgio-fam package on kFreeBSD ports.
  +It is no longer necessary now that gkqueuefilemonitor is available.
  +
  +  [ Simon McVittie ]
  +  * Clarify changelog entry regarding Hurd and kFreeBSD
  +  * New upstream stable release
  +
  + -- Simon McVittie   Fri, 29 May 2020 20:24:33 +0100

  The gio-fam related changes do not affect Ubuntu, as they are for
  hurd/kfreebsd only.

  Upstream NEWS diff:

  * Stability improvements for various unit tests

  * Bugs fixed:
   - #1954 gdbus-server-auth intermittent failure
   - #2094 Deprecation warnings when compiling with 
-DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_28 
-DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_28
   - !1470 Backport !1440 -Wformat-nonliteral fixes to glib-2-64
   - !1471 Backport !1448 memory monitor test dependency fixes to glib-2-64
   - !1473 CI: Switch to new Windows runners (2.64)
   - !1478 Backport !1477 D-Bus keyring handling fixes to glib-2-64
   - !1483 Backport !1481 “array: fix corrupt state of GPtrArray after 
g_ptr_array_extend_and_steal()” to glib-2-64
   - !1484 Backport !1480 “CI: Make sure we use meson 0.49.2 in MSYS2” to 
glib-2-64
   - !1486 Backport !1472 “gthread: ignore deprecated 

[Touch-packages] [Bug 1559650] Re: gnome-shell crashed with SIGSEGV in ___vsnprintf_chk()

2020-06-15 Thread Iain Lane
I've sponsored the debdiff to bionic's queue

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

Title:
  gnome-shell crashed with SIGSEGV in ___vsnprintf_chk()

Status in libxau package in Ubuntu:
  Fix Released
Status in libxau source package in Bionic:
  In Progress
Status in libxau source package in Eoan:
  Fix Released
Status in libxau source package in Focal:
  Fix Released

Bug description:
  [Impact]

  gnome-shell crashes a lot. Over 38000 times in bionic so far:
  https://errors.ubuntu.com/problem/00455200cd9fb890dacfe09b92c7bda2f6ad3af7

  [Test Case]

  None known yet. Just keeping an eye on the above link for regressions.

  [Regression Potential]

  Low. The same fix has been released to newer distros for the past 2
  years already.

  [Other Info]

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: gnome-shell 3.18.4-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5
  Uname: Linux 4.4.0-13-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Wed Mar 16 17:15:11 2016
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:

  InstallationDate: Installed on 2016-03-13 (6 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160311)
  ProcCmdline: gnome-shell --mode=gdm --wayland --display-server
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x7f1ff33f46ab <___vsnprintf_chk+107>: movb   
$0x0,(%r12)
   PC (0x7f1ff33f46ab) ok
   source "$0x0" ok
   destination "(%r12)" (0x) not located in a known VMA region (needed 
writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   ___vsnprintf_chk (s=0x0, maxlen=, flags=1, slen=, format=0x7f1fe54ccae5 "%s%s", args=args@entry=0x7f1fce502da8) at 
vsnprintf_chk.c:55
   ___snprintf_chk (s=, maxlen=, flags=, slen=, format=) at snprintf_chk.c:34
   XauFileName () from /usr/lib/x86_64-linux-gnu/libXau.so.6
   XauGetBestAuthByAddr () from /usr/lib/x86_64-linux-gnu/libXau.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
  Title: gnome-shell crashed with SIGSEGV in ___vsnprintf_chk()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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


[Touch-packages] [Bug 1875558] Re: [SRU] libproxy1-plugin-gsettings triggers a lot of warnings

2020-06-08 Thread Iain Lane
Checked too, seems good to me - updating tags. Thanks!

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

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

Title:
  [SRU] libproxy1-plugin-gsettings triggers a lot of warnings

Status in libproxy package in Ubuntu:
  Fix Released
Status in libproxy source package in Focal:
  Fix Committed

Bug description:
  [Impact]

   * The proxy configuration from GSettings is not getting exported and
  thus is not used by libproxy-enabled applications.

   * Many GLib applications are now throwing critical messages in the
  logs when running. This is escpecially true for WebKitGtk applications
  which are throwing one message by subprocess.

  [Test Case]

   * Open a WebKitGtk application such as Epiphany (GNOME Web) with the
  terminal and see the critical messages

  GLib-GObject-WARNING **: 09:00:09.217:
  ../../../gobject/gsignal.c:2617: signal 'changed::' is invalid for
  instance '0x55b923a6b430' of type 'GSettings'

  [Regression Potential]

   * No regression is to expect from this patch

  [Other Info]
   
   * The patch is already in debian experimental and is available since 
0.4.15-12

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

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


[Touch-packages] [Bug 1859308] Re: software-properties-gtk erroneously reports that certain Intel wireless adapter cards are not working

2020-05-19 Thread Iain Lane
** Also affects: software-properties (Ubuntu Groovy)
   Importance: Low
 Assignee: Olivier Tilloy (osomon)
   Status: Confirmed

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

Title:
  software-properties-gtk erroneously reports that certain Intel
  wireless adapter cards are not working

Status in software-properties package in Ubuntu:
  Confirmed
Status in software-properties source package in Groovy:
  Confirmed

Bug description:
  On Ubuntu 20.04 (development branch), as of today, Additional Drivers
  (software-properties-gtk 0.98.6) reports that the device "Intel
  Corporation: Wireless-AC 9260" is not working, and suggests using a
  manually installed driver (cf. screenshot).

  However the device is working correctly:

    * lsmod | grep iwlwifi, lspci -v, lshw, dmesg | grep iwlwifi all show
  that its driver iwlwifi is in use
    * ls /lib/firmware/*9260* show that the appropriate firmware files
  are present

  And I am indeed writing this bug report connected to an ac (5 GHz)
  wifi network, where I can verify a ~130-160 Mbps download speed, so
  software-properties-gtk shouldn't report the device as not working and
  suggest manually installing a driver. Not sure why it says so?

  EDIT: bug confirmed as affecting the following Intel wireless adapter
  cards, and assumedly more to come:

Intel Wi-Fi 6 AX200
Intel Dual Band Wireless-AC 3165
Intel Dual Band Wireless-AC 7260
Intel Dual Band Wireless-AC 8260
Intel Wireless-AC 9260

  Also for reference here are the specs of Intel adapter cards:

ark.intel.com/content/www/us/en/ark.html#@WirelessNetworking

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: software-properties-gtk 0.98.6
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 12 00:53:43 2020
  ExecutablePath: /usr/bin/software-properties-gtk
  InstallationDate: Installed on 2019-12-29 (13 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191226)
  InterpreterPath: /usr/bin/python3.7
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.7, Python 3.7.6, python3-minimal, 
3.7.5-1ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.17-1
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1878553] Re: Ubuntu could not install Virtualbox Guest addons

2020-05-19 Thread Iain Lane
** Also affects: software-properties (Ubuntu Groovy)
   Importance: Undecided
 Assignee: Olivier Tilloy (osomon)
   Status: New

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

Title:
  Ubuntu could not install Virtualbox Guest addons

Status in software-properties package in Ubuntu:
  New
Status in software-properties source package in Groovy:
  New

Bug description:
  It seems that Ubuntu is not able to install the VirtualBox Guest add-
  ons even Ubuntu is able to detect it.

  See Attachement.

  Ubuntu 20.04
  Basic install after Reboot, Update and Reboot again.

  Similar Tickets in Launchpad but really old:
  https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1434579

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

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


[Touch-packages] [Bug 1843982] Re: Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from update_user()

2020-05-15 Thread Iain Lane
Right. It's in the library. Programs will remain using the versions of
the libraries that were on the system when they started, so that means
that you need to upgrade, reboot, and *then* try the restart. I should
update the QA steps to make that more clear, will do.

** Description changed:

  [ Description ]
  
  When accountsservice's daemon is restarted - particularly when there is
  a user configured for auto login - it can cause code using its library
  to crash. This is bad because gnome-shell is one of those users which
  crashes.
  
  [ QA ]
  
  Configure a user for automatic login in gnome-shell.
+ 
+ Update to this SRU, and then *restart your system*. The crash is in the
+ library part, and so you will still see it if programs loaded the buggy
+ version. Restarting is the easiest way to make sure you're not on it.
  
  Restart accounts-daemon.service (sudo systemctl restart accounts-
  daemon.service) a few times, leaving several seconds between each
  attempt.
  
  See that it crashes if you don't have this SRU, and doesn't if you do
  have it.
  
  ---
  
  Test that fast user switching still works properly.
  
  ---
  
  Take a look at the error reports listed below and hopefully see them not
  occurring (barring the usual noise) with the SRU.
  
  [ Regression potential ]
  
  We think this is safe - it tells clients that the daemon is away when it
  quits, and is back when it comes back. They should get appropriate
  signals to indicate this. Nevertheless, these signals are sent when they
  weren't before now, so that could cause problems. Watch out for errors
  creeping up with this SRU.
  
  We wondered upstream whether some more protections might be needed. I'm
  thinking that those should be *additional* safety rails around this fix,
  but it could actually be that more is needed and this fix isn't
  complete.
  
  [ Original report ]
  
  https://errors.ubuntu.com/problem/597be858df957473f357a9249b002b0e39f42781
  https://errors.ubuntu.com/problem/3a817938d76d231fdfc8f698392fbf5e3724084f
  https://errors.ubuntu.com/problem/3945cd9cdcec914cab9a3220d05e969696c7
  
  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 14 10:29:16 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2019-05-24 (112 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190523)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=nb_NO.UTF-8
   LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.34.0-2ubuntu1
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libaccountsservice.so.0
   g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell crashed with SIGSEGV in g_str_hash()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

Title:
  Various programs crashed with SIGSEGV in g_str_hash() from
  g_hash_table_lookup() from update_user()

Status in accountsservice:
  New
Status in accountsservice package in Ubuntu:
  Fix Released
Status in accountsservice source package in Focal:
  Fix Committed
Status in accountsservice package in Debian:
  Confirmed

Bug description:
  [ Description ]

  When accountsservice's daemon is restarted - particularly when there
  is a user configured for auto login - it can cause code using its
  library to crash. This is bad because gnome-shell is one of those
  users which crashes.

  [ QA ]

  Configure a user for automatic login in gnome-shell.

  Update to this SRU, and then *restart your system*. The crash is in
  the library part, and so you will still see it if programs loaded the
  buggy version. Restarting is the easiest way to make sure you're not
  on it.

  Restart accounts-daemon.service (sudo systemctl restart accounts-
  daemon.service) a few times, leaving several seconds between each
  attempt.

  See that it crashes if you don't have this SRU, and doesn't if you do
  have it.

  ---

  Test that fast user switching still works properly.

  ---

  Take a look at the error reports listed below and hopefully see them
  not occurring (barring the usual noise) with the SRU.

  [ Regression potential ]

  We think this is safe - it 

[Touch-packages] [Bug 1878611] Re: accountsservice 0.6.55-0ubuntu12~20.04.1 update crashes into greeter

2020-05-15 Thread Iain Lane
*** This bug is a duplicate of bug 1843982 ***
https://bugs.launchpad.net/bugs/1843982

It's not a regression. It is in fact the same bug happening one last
time. I just explained it in the other bug, hope that's clear.

(If I'm not understanding right, please un-dupe and re-open this bug.)

** This bug has been marked a duplicate of bug 1843982
   Various programs crashed with SIGSEGV in g_str_hash() from 
g_hash_table_lookup() from update_user()

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

Title:
  accountsservice 0.6.55-0ubuntu12~20.04.1 update crashes into  greeter

Status in accountsservice package in Ubuntu:
  New

Bug description:
  When updating Ubuntu 20.04 to the current proposed updates with the
  accountsservice 0.6.55-0ubuntu12~20.04.1 update, the current gnome
  session crashes out reproducibly into the the gdm3 greeter. At that
  point, when you try to log back in, only the background color is
  displayed but no desktop or menus ever appears. One has to perform a
  hard reboot at this point to get back to a greeter that will
  successfully login.

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

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


[Touch-packages] [Bug 1877093] Re: [SRU] New stable release 2.34.2

2020-05-09 Thread Iain Lane
autopkgtest [15:02:47]: test tests: ---]
autopkgtest [15:02:48]: test tests:  - - - - - - - - - - results - - - - - - - 
- - -
testsPASS
autopkgtest [15:02:49]:  summary
testsPASS

Successfully signed dsc, buildinfo, changes files
Uploading at-spi2-atk_2.34.2-0ubuntu2~20.04.1.dsc
Uploading at-spi2-atk_2.34.2-0ubuntu2~20.04.1.debian.tar.xz
Uploading at-spi2-atk_2.34.2-0ubuntu2~20.04.1_source.buildinfo
Uploading at-spi2-atk_2.34.2-0ubuntu2~20.04.1_source.changes

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

Title:
  [SRU] New stable release 2.34.2

Status in at-spi2-atk package in Ubuntu:
  Fix Released
Status in at-spi2-atk source package in Focal:
  In Progress

Bug description:
  [ Description ]

  GNOME upstream have released a new stable version of at-spi2-atk.

  Changes:

  What's new in at-spi2-atk 2.34.2:

  * Meson: don't hard-code shared_library (!19).

  * Mitigate missing window events at startup.

  * Set C standard to gnu99 (#10).

  * Tests: include sys/time.h (#14).

  [ QA ]

  GNOME has a micro release exception that covers this package.

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

  So we don't need to verify the fixes explicitly.

  Install the desktop and exercise the screen reader in a variety of
  situations.

  Optionally, but ideally, test the installer too.

  [ Regression potential ]

  If this update is busted the screen reader might not work. This
  changes the C standard too, which should be fine, but make sure to do
  some QA.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/at-spi2-atk/+bug/1877093/+subscriptions

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


[Touch-packages] [Bug 1877093] Re: [SRU] New stable release 2.34.2

2020-05-09 Thread Iain Lane
Thanks.

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

Title:
  [SRU] New stable release 2.34.2

Status in at-spi2-atk package in Ubuntu:
  Fix Released
Status in at-spi2-atk source package in Focal:
  In Progress

Bug description:
  [ Description ]

  GNOME upstream have released a new stable version of at-spi2-atk.

  Changes:

  What's new in at-spi2-atk 2.34.2:

  * Meson: don't hard-code shared_library (!19).

  * Mitigate missing window events at startup.

  * Set C standard to gnu99 (#10).

  * Tests: include sys/time.h (#14).

  [ QA ]

  GNOME has a micro release exception that covers this package.

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

  So we don't need to verify the fixes explicitly.

  Install the desktop and exercise the screen reader in a variety of
  situations.

  Optionally, but ideally, test the installer too.

  [ Regression potential ]

  If this update is busted the screen reader might not work. This
  changes the C standard too, which should be fine, but make sure to do
  some QA.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/at-spi2-atk/+bug/1877093/+subscriptions

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


[Touch-packages] [Bug 1877093] [NEW] [SRU] New stable release 2.34.2

2020-05-06 Thread Iain Lane
Public bug reported:

[ Description ]

GNOME upstream have released a new stable version of at-spi2-atk.

Changes:

What's new in at-spi2-atk 2.34.2:

* Meson: don't hard-code shared_library (!19).

* Mitigate missing window events at startup.

* Set C standard to gnu99 (#10).

* Tests: include sys/time.h (#14).

[ QA ]

GNOME has a micro release exception that covers this package.

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

So we don't need to verify the fixes explicitly.

Install the desktop and exercise the screen reader in a variety of
situations.

Optionally, but ideally, test the installer too.

[ Regression potential ]

If this update is busted the screen reader might not work. This changes
the C standard too, which should be fine, but make sure to do some QA.

** Affects: at-spi2-atk (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: at-spi2-atk (Ubuntu Focal)
 Importance: Undecided
 Assignee: Iain Lane (laney)
 Status: In Progress

** Also affects: at-spi2-atk (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Changed in: at-spi2-atk (Ubuntu Focal)
   Status: New => In Progress

** Changed in: at-spi2-atk (Ubuntu Focal)
 Assignee: (unassigned) => Iain Lane (laney)

** Changed in: at-spi2-atk (Ubuntu)
   Status: New => Fix Released

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

Title:
  [SRU] New stable release 2.34.2

Status in at-spi2-atk package in Ubuntu:
  Fix Released
Status in at-spi2-atk source package in Focal:
  In Progress

Bug description:
  [ Description ]

  GNOME upstream have released a new stable version of at-spi2-atk.

  Changes:

  What's new in at-spi2-atk 2.34.2:

  * Meson: don't hard-code shared_library (!19).

  * Mitigate missing window events at startup.

  * Set C standard to gnu99 (#10).

  * Tests: include sys/time.h (#14).

  [ QA ]

  GNOME has a micro release exception that covers this package.

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

  So we don't need to verify the fixes explicitly.

  Install the desktop and exercise the screen reader in a variety of
  situations.

  Optionally, but ideally, test the installer too.

  [ Regression potential ]

  If this update is busted the screen reader might not work. This
  changes the C standard too, which should be fine, but make sure to do
  some QA.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/at-spi2-atk/+bug/1877093/+subscriptions

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


[Touch-packages] [Bug 1843982] Re: Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from update_user()

2020-05-05 Thread Iain Lane
Okay, I've uploaded a fix to groovy and the review queue for 20.04.

** Description changed:

+ [ Description ]
+ 
+ When accountsservice's daemon is restarted - particularly when there is
+ a user configured for auto login - it can cause code using its library
+ to crash. This is bad because gnome-shell is one of those users which
+ crashes.
+ 
+ [ QA ]
+ 
+ Configure a user for automatic login in gnome-shell.
+ 
+ Restart accounts-daemon.service (sudo systemctl restart accounts-
+ daemon.service) a few times, leaving several seconds between each
+ attempt.
+ 
+ See that it crashes if you don't have this SRU, and doesn't if you do
+ have it.
+ 
+ ---
+ 
+ Test that fast user switching still works properly.
+ 
+ ---
+ 
+ Take a look at the error reports listed below and hopefully see them not
+ occurring (barring the usual noise) with the SRU.
+ 
+ [ Regression potential ]
+ 
+ We think this is safe - it tells clients that the daemon is away when it
+ quits, and is back when it comes back. They should get appropriate
+ signals to indicate this. Nevertheless, these signals are sent when they
+ weren't before now, so that could cause problems. Watch out for errors
+ creeping up with this SRU.
+ 
+ We wondered upstream whether some more protections might be needed. I'm
+ thinking that those should be *additional* safety rails around this fix,
+ but it could actually be that more is needed and this fix isn't
+ complete.
+ 
+ [ Original report ]
+ 
  https://errors.ubuntu.com/problem/597be858df957473f357a9249b002b0e39f42781
  https://errors.ubuntu.com/problem/3a817938d76d231fdfc8f698392fbf5e3724084f
  https://errors.ubuntu.com/problem/3945cd9cdcec914cab9a3220d05e969696c7
  
  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 14 10:29:16 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2019-05-24 (112 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190523)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=nb_NO.UTF-8
   LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.34.0-2ubuntu1
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libaccountsservice.so.0
   g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell crashed with SIGSEGV in g_str_hash()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

Title:
  Various programs crashed with SIGSEGV in g_str_hash() from
  g_hash_table_lookup() from update_user()

Status in accountsservice:
  New
Status in accountsservice package in Ubuntu:
  Triaged
Status in accountsservice source package in Focal:
  Triaged
Status in accountsservice package in Debian:
  Confirmed

Bug description:
  [ Description ]

  When accountsservice's daemon is restarted - particularly when there
  is a user configured for auto login - it can cause code using its
  library to crash. This is bad because gnome-shell is one of those
  users which crashes.

  [ QA ]

  Configure a user for automatic login in gnome-shell.

  Restart accounts-daemon.service (sudo systemctl restart accounts-
  daemon.service) a few times, leaving several seconds between each
  attempt.

  See that it crashes if you don't have this SRU, and doesn't if you do
  have it.

  ---

  Test that fast user switching still works properly.

  ---

  Take a look at the error reports listed below and hopefully see them
  not occurring (barring the usual noise) with the SRU.

  [ Regression potential ]

  We think this is safe - it tells clients that the daemon is away when
  it quits, and is back when it comes back. They should get appropriate
  signals to indicate this. Nevertheless, these signals are sent when
  they weren't before now, so that could cause problems. Watch out for
  errors creeping up with this SRU.

  We wondered upstream whether some more protections might be needed.
  I'm thinking that those should be *additional* safety rails around
  this fix, but it could actually be that more is needed and this fix
  isn't complete.

  [ Original report ]

  https://errors.ubuntu.com/problem/597be858df957473f357a9249b002b0e39f42781
  

[Touch-packages] [Bug 1876693] [NEW] [SRU] New stable release 1.64.1

2020-05-04 Thread Iain Lane
Public bug reported:

[ Description ]

GNOME upstream have released a new stable version of gobject-
introspection.

Changes:

1.64.1 - 2020-04-05
---

* Replace calls to deprecated xml.etree.cElementTree removed in Python 3.9 
:mr:`202` (:user:`Stephen Gallagher `)
* gimarshallingtests: Use g_assert_cmpfloat_with_epsilon. Fixes tests on some 
architectures :mr:`200` (:user:`Iain Lane `)

[ QA ]

GNOME has a micro release exception that covers this package.

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

So we don't need to verify the fixes explicitly.

Do this:

  - Install the update, smoke test some of the reverse depends (apt rdepends 
libgirepository-1.0-1 and more importantly the indirect rdepends via python3-gi)
  - Run "reverse-depends -b src:gobject-introspection" and test rebuild a few 
of them

[ Regression potential ]

g-i being broken will break pretty much the whole desktop, but you'd
know that quite fast.

The .py changes, if they're wrong or bad, could break the build of r
-build-deps.

** Affects: gobject-introspection (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: gobject-introspection (Ubuntu Focal)
 Importance: Undecided
 Assignee: Iain Lane (laney)
 Status: In Progress

** Also affects: gobject-introspection (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Changed in: gobject-introspection (Ubuntu)
   Status: New => Fix Released

** Changed in: gobject-introspection (Ubuntu Focal)
 Assignee: (unassigned) => Iain Lane (laney)

** Changed in: gobject-introspection (Ubuntu Focal)
   Status: New => In Progress

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

Title:
  [SRU] New stable release 1.64.1

Status in gobject-introspection package in Ubuntu:
  Fix Released
Status in gobject-introspection source package in Focal:
  In Progress

Bug description:
  [ Description ]

  GNOME upstream have released a new stable version of gobject-
  introspection.

  Changes:

  1.64.1 - 2020-04-05
  ---

  * Replace calls to deprecated xml.etree.cElementTree removed in Python 3.9 
:mr:`202` (:user:`Stephen Gallagher `)
  * gimarshallingtests: Use g_assert_cmpfloat_with_epsilon. Fixes tests on some 
architectures :mr:`200` (:user:`Iain Lane `)

  [ QA ]

  GNOME has a micro release exception that covers this package.

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

  So we don't need to verify the fixes explicitly.

  Do this:

- Install the update, smoke test some of the reverse depends (apt rdepends 
libgirepository-1.0-1 and more importantly the indirect rdepends via python3-gi)
- Run "reverse-depends -b src:gobject-introspection" and test rebuild a few 
of them

  [ Regression potential ]

  g-i being broken will break pretty much the whole desktop, but you'd
  know that quite fast.

  The .py changes, if they're wrong or bad, could break the build of r
  -build-deps.

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

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


[Touch-packages] [Bug 1873658] Re: Deb Files are not associated with an application that manages packages

2020-04-24 Thread Iain Lane
We discussed this a bit amongst the release team, and there was a
concern that this might not work properly for flavours - which I think
that Ken believes is fine, but it would be good to actually verify
explicitly.

So please could you flesh out the description to fit the SRU template,
and add a test case which makes sure to check all of these mime types
for flavours which still seed gnome-software (e.g. boot live session,
install -proposed update, try to open each of those mime types).

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

Title:
  Deb Files are not associated with an application that manages packages

Status in desktop-file-utils package in Ubuntu:
  Confirmed
Status in gdebi package in Ubuntu:
  Invalid
Status in desktop-file-utils source package in Focal:
  Confirmed
Status in gdebi source package in Focal:
  Invalid

Bug description:
  When you download a DEB file within 20.04 Ubuntu Beta and you double
  click it the file is opened by the archive manager.  I would expect
  the installer to open the file just like in previous versions of
  Ubuntu.

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

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


[Touch-packages] [Bug 1843982] Re: Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from update_user()

2020-04-15 Thread Iain Lane
** Also affects: accountsservice (Ubuntu Focal)
   Importance: High
 Assignee: Iain Lane (laney)
   Status: Triaged

** Changed in: accountsservice (Ubuntu Focal)
Milestone: None => ubuntu-20.04.1

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

Title:
  Various programs crashed with SIGSEGV in g_str_hash() from
  g_hash_table_lookup() from update_user()

Status in accountsservice:
  New
Status in accountsservice package in Ubuntu:
  Triaged
Status in accountsservice source package in Focal:
  Triaged
Status in accountsservice package in Debian:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/597be858df957473f357a9249b002b0e39f42781
  https://errors.ubuntu.com/problem/3a817938d76d231fdfc8f698392fbf5e3724084f
  https://errors.ubuntu.com/problem/3945cd9cdcec914cab9a3220d05e969696c7

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 14 10:29:16 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2019-05-24 (112 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190523)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=nb_NO.UTF-8
   LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.34.0-2ubuntu1
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libaccountsservice.so.0
   g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell crashed with SIGSEGV in g_str_hash()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

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


[Touch-packages] [Bug 1864274] Re: crunchy pixels

2020-03-17 Thread Iain Lane
** Also affects: mesa (Ubuntu Focal)
   Importance: Undecided
   Status: Confirmed

** Changed in: mesa (Ubuntu Focal)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

** Tags removed: champagne

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

Title:
  crunchy pixels

Status in Mesa:
  Unknown
Status in mesa package in Ubuntu:
  Confirmed
Status in mesa source package in Focal:
  Confirmed

Bug description:
  Hello, after upgrading firefox (and many other packages) on focal
  today, I've got some video artifacts in firefox.

  When typing in text boxes and text fields, the new character is drawn
  very slowly, pixel-by-pixel, and isn't complete until the cursor has
  moved on. When larger portions of the screen are updated, it looks a
  lot like the entire window is being run through a video codec or you
  can see parts of the video memory from other processes. (But it looks
  more deliberate and predictable than either of these descriptions.)

  So far Firefox is the only application I've found that is affected.
  urxvt, libreoffice, xfontsel, glxgears all seem to work as expected.

  I did get cairo package update today, but the changelog is just:

  pango1.0 (1.44.7-1ubuntu2) focal; urgency=medium
* No-change rebuild with fixed binutils on arm64.
   -- Matthias Klose   Sat, 08 Feb 2020 11:15:23 +

  And an xorg update:

  xorg (1:7.7+19ubuntu14) focal; urgency=medium
* No-change rebuild with fixed binutils on arm64.
   -- Matthias Klose   Sat, 08 Feb 2020 11:21:28 +

  
  So I don't believe these are involved.

  00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620
  (rev 07)

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 73.0.1+build1-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-14-generic.
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sarnold3296 F pulseaudio
   /dev/snd/controlC0:  sarnold3296 F pulseaudio
  BuildID: 20200217142647
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 144'
 Mixer name : 'Realtek ALC285'
 Components : 'HDA:10ec0285,17aa225c,0012 
HDA:8086280b,80860101,0010'
 Controls  : 53
 Simple ctrls  : 15
  Card1.Amixer.info:
   Card hw:1 'Audio'/'Generic ThinkPad Dock USB Audio at 
usb-:00:14.0-4.2.4, high speed'
 Mixer name : 'USB Mixer'
 Components : 'USB17ef:306f'
 Controls  : 9
 Simple ctrls  : 4
  Channel: Unavailable
  Date: Sat Feb 22 05:41:10 2020
  ForcedLayersAccel: False
  IncompatibleExtensions:
   Pentadactyl - pentadac...@dactyl.googlecode.com
   English (GB) Language Pack - langpack-en...@firefox.mozilla.org
   English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
   Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  IpRoute:
   default via 192.168.0.1 dev enp0s31f6 proto dhcp metric 100 
   10.23.231.0/24 dev lxdbr0 proto kernel scope link src 10.23.231.1 
   192.168.0.0/24 dev enp0s31f6 proto kernel scope link src 192.168.0.34 metric 
100 
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  MostRecentCrashID: bp-ea952d4d-f25a-4ced-893c-8cabb2160112
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:737
  PrefSources: prefs.js
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=73.0.1/20200217142647 (In use)
  RunningIncompatibleAddons: True
  SourcePackage: firefox
  UpgradeStatus: Upgraded to focal on 2020-01-24 (28 days ago)
  dmi.bios.date: 11/25/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET69W (1.44 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET69W(1.44):bd11/25/2019:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KHCTO1WW
  dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO

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

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

  1   2   3   4   5   6   7   8   9   10   >