[Touch-packages] [Bug 1907956] Re: ubiquity crash on whoopsie removal, Xubuntu 21.04 minimal install

2021-01-22 Thread Brian Murray
Incidentally, why are apport-gtk and whoopsie being removed? I'd think
crash reporting would be useful.

https://git.launchpad.net/~xubuntu-dev/ubuntu-
seeds/+git/xubuntu/commit/?id=c6d4cd2e0a24a5114dfe1cb8554d99ca91630a91

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

Title:
  ubiquity crash on whoopsie removal, Xubuntu 21.04 minimal install

Status in ubiquity package in Ubuntu:
  New
Status in whoopsie package in Ubuntu:
  New
Status in ubiquity source package in Hirsute:
  New
Status in whoopsie source package in Hirsute:
  New

Bug description:
  Xubuntu hirsute 20201213 minimal install crashed on whoopsie removal
  but finished installing. This is 1907951 with hopefully more crash
  information.

  Related logs identified:
  Dec 13 12:37:05 xubuntu ubiquity: Purging configuration files for whoopsie 
(0.2.73) ...
  Dec 13 12:37:05 xubuntu ubiquity: #015
  Dec 13 12:37:05 xubuntu ubiquity: Running in chroot, ignoring command 
'daemon-reload'#015
  Dec 13 12:37:05 xubuntu ubiquity: message repeated 2 times: [ Running in 
chroot, ignoring command 'daemon-reload'#015]
  Dec 13 12:37:05 xubuntu ubiquity: rm:
  Dec 13 12:37:05 xubuntu ubiquity: cannot remove 
'/var/lib/whoopsie/whoopsie-id'
  Dec 13 12:37:05 xubuntu ubiquity: : No such file or directory
  Dec 13 12:37:05 xubuntu ubiquity: #015
  Dec 13 12:37:05 xubuntu ubiquity: dpkg: error processing package whoopsie 
(--purge):
  Dec 13 12:37:05 xubuntu ubiquity: #015
  Dec 13 12:37:05 xubuntu ubiquity:  installed whoopsie package post-removal 
script subprocess returned error exit status 1
  Dec 13 12:37:05 xubuntu ubiquity: #015

  Looks like it's a bug in the postrm script:
  #! /bin/sh

  set -e

  #DEBHELPER#

  if [ "$1" = "purge" ]; then
  deluser --quiet --system whoopsie > /dev/null || true
  chmod g-s /var/crash >/dev/null 2>&1
  chgrp root /var/crash >/dev/null 2>&1
  rm /var/lib/whoopsie/whoopsie-id >/dev/null
  fi

  exit 0

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: ubiquity 21.04.3
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu55
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.456
  Date: Sun Dec 13 07:40:33 2020
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/xubuntu.seed 
maybe-ubiquity quiet splash ---
  LiveMediaBuild: Xubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201213)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
  RebootRequiredPkgs:
   linux-image-5.8.0-25-generic
   linux-base
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1889742] Re: [UBUNTU 20.04] Accept vector alignment hints on z13 (binutils)

2021-01-21 Thread Brian Murray
I haven't looked at the debdiff in detail but the version number could
use changing to ubuntu1.1 per
https://wiki.ubuntu.com/SecurityTeam/UpdatePreparation#Update_the_packaging.

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

Title:
  [UBUNTU 20.04] Accept vector alignment hints on z13 (binutils)

Status in Ubuntu on IBM z Systems:
  In Progress
Status in binutils package in Ubuntu:
  Fix Released
Status in binutils source package in Focal:
  New
Status in binutils source package in Groovy:
  Fix Released

Bug description:
  == Comment: #0 - Heinz-Werner Seeck  - 
2020-07-31 03:28:30 ==
  On z13 we have that vector alignment hints are already accepted. This 
backport enables GAS to accept such hints not only for target z14 but also for 
z13. Since GCCs default target on Ubuntu is z13 for s390x, we could greatly 
benefit from such alignment hints. (note a separate bugzilla entry for GCC 
allowing to emit alignment hints for z13 will be opened shortly)

  This is a backport of upstreams commit 26b6ab7a0e.
   
  Userspace tool common name: as 
   
  The userspace tool has the following bit modes: 64-bit 

  Userspace rpm: binutils

  
  Already included within 20.10 via LP:
  https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1888654

  This should also be SRUed for 20.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1889742/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-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-19 Thread Brian Murray
Hello Iain, or anyone else affected,

Accepted glib2.0 into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/glib2.0/2.64.6-1~ubuntu20.04.1 in a
few hours, and then in the -proposed repository.

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

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

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

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

** Changed in: glib2.0 (Ubuntu Focal)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-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
  

[Touch-packages] [Bug 1908473] Please test proposed package

2021-01-19 Thread Brian Murray
Hello Matthew, or anyone else affected,

Accepted librelp into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/librelp/1.5.0-1ubuntu2.20.04.1 in a
few hours, and then in the -proposed repository.

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

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

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

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

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

Title:
  rsyslog-relp: imrelp module leaves sockets in CLOSE_WAIT state which
  leads to file descriptor leak

Status in librelp package in Ubuntu:
  Fix Released
Status in rsyslog package in Ubuntu:
  Fix Released
Status in librelp source package in Focal:
  Fix Committed
Status in rsyslog source package in Focal:
  Won't Fix
Status in librelp source package in Groovy:
  Fix Committed
Status in rsyslog source package in Groovy:
  Fix Released
Status in librelp source package in Hirsute:
  Fix Released
Status in rsyslog source package in Hirsute:
  Fix Released

Bug description:
  [Impact]

  In recent versions of rsyslog and librelp, the imrelp module leaks
  file descriptors due to a bug where it does not correctly close
  sockets, and instead, leaves them in the CLOSE_WAIT state.

  This causes rsyslogd on busy servers to eventually hit the limit of
  maximum open files allowed, which locks rsyslogd up until it is
  restarted.

  A workaround is to restart rsyslogd every month or so to manually
  close all of the open sockets.

  Only users of the imrelp module are affected, and not rsyslog users in
  general.

  [Testcase]

  Install the rsyslog-relp module like so:

  $ sudo apt install rsyslog rsyslog-relp

  Next, generate a working directory, and make a config file that loads
  the relp module.

  $ sudo mkdir /workdir
  $ cat << EOF >> ./spool.conf
  \$LocalHostName spool
  \$AbortOnUncleanConfig on
  \$PreserveFQDN on

  global(
  workDirectory="/workdir"
  maxMessageSize="256k"
  )

  main_queue(queue.type="Direct")
  module(load="imrelp")
  input(
  type="imrelp"
  name="imrelp"
  port="601"
  ruleset="spool"
  MaxDataSize="256k"
  )

  ruleset(name="spool" queue.type="direct") {
  }

  # Just so rsyslog doesn't whine that we do not have outputs
  ruleset(name="noop" queue.type="direct") {
  action(
  type="omfile"
  name="omfile"
  file="/workdir/spool.log"
  )
  }
  EOF

  Verify that the config is valid, then start a rsyslog server.

  $ sudo rsyslogd -f ./spool.conf -N9
  $ sudo rsyslogd -f ./spool.conf -i /workdir/rsyslogd.pid

  Fetch the rsyslogd PID and check for open files.

  $ RLOGPID=$(cat /workdir/rsyslogd.pid)
  $ sudo ls -l /proc/$RLOGPID/fd
  total 0
  lr-x-- 1 root root 64 Dec 17 01:22 0 -> /dev/urandom
  lrwx-- 1 root root 64 Dec 17 01:22 1 -> 'socket:[41228]'
  lrwx-- 1 root root 64 Dec 17 01:22 3 -> 'socket:[41222]'
  lrwx-- 1 root root 64 Dec 17 01:22 4 -> 'socket:[41223]'
  lrwx-- 1 root root 64 Dec 17 01:22 7 -> 'anon_inode:[eventpoll]'

  We have 3 sockets open by default. Next, use netcat to open 100
  connections:

  $ for i in {1..100} ; do nc -z 127.0.0.1 601 ; done

  Now check for open file descriptors, and there will be an extra 100 sockets
  in the list:

  $ sudo ls -l /proc/$RLOGPID/fd

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

  We can check the state of these sockets with:

  $ ss -t

  https://paste.ubuntu.com/p/7Ts2FbxJrg/

  The listening sockets will be in CLOSE-WAIT, and the netcat sockets
  will be in FIN-WAIT-2.

  $ ss -t | grep CLOSE-WAIT | wc -l
  100

  If you install the test package available in the following ppa:

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

  When you open connections with netcat, these will be closed properly,
  and the file descriptor leak will be fixed.

  [Where problems could occur]

  If a regression were to occur, it would be limited to users of the
  imrelp module, which is a part of the rsyslogd-relp 

[Touch-packages] [Bug 1908473] Re: rsyslog-relp: imrelp module leaves sockets in CLOSE_WAIT state which leads to file descriptor leak

2021-01-19 Thread Brian Murray
Hello Matthew, or anyone else affected,

Accepted librelp into groovy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/librelp/1.5.0-1ubuntu2.20.10.1 in a
few hours, and then in the -proposed repository.

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

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

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

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

** Changed in: librelp (Ubuntu Groovy)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-groovy

** Changed in: librelp (Ubuntu Focal)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-focal

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

Title:
  rsyslog-relp: imrelp module leaves sockets in CLOSE_WAIT state which
  leads to file descriptor leak

Status in librelp package in Ubuntu:
  Fix Released
Status in rsyslog package in Ubuntu:
  Fix Released
Status in librelp source package in Focal:
  Fix Committed
Status in rsyslog source package in Focal:
  Won't Fix
Status in librelp source package in Groovy:
  Fix Committed
Status in rsyslog source package in Groovy:
  Fix Released
Status in librelp source package in Hirsute:
  Fix Released
Status in rsyslog source package in Hirsute:
  Fix Released

Bug description:
  [Impact]

  In recent versions of rsyslog and librelp, the imrelp module leaks
  file descriptors due to a bug where it does not correctly close
  sockets, and instead, leaves them in the CLOSE_WAIT state.

  This causes rsyslogd on busy servers to eventually hit the limit of
  maximum open files allowed, which locks rsyslogd up until it is
  restarted.

  A workaround is to restart rsyslogd every month or so to manually
  close all of the open sockets.

  Only users of the imrelp module are affected, and not rsyslog users in
  general.

  [Testcase]

  Install the rsyslog-relp module like so:

  $ sudo apt install rsyslog rsyslog-relp

  Next, generate a working directory, and make a config file that loads
  the relp module.

  $ sudo mkdir /workdir
  $ cat << EOF >> ./spool.conf
  \$LocalHostName spool
  \$AbortOnUncleanConfig on
  \$PreserveFQDN on

  global(
  workDirectory="/workdir"
  maxMessageSize="256k"
  )

  main_queue(queue.type="Direct")
  module(load="imrelp")
  input(
  type="imrelp"
  name="imrelp"
  port="601"
  ruleset="spool"
  MaxDataSize="256k"
  )

  ruleset(name="spool" queue.type="direct") {
  }

  # Just so rsyslog doesn't whine that we do not have outputs
  ruleset(name="noop" queue.type="direct") {
  action(
  type="omfile"
  name="omfile"
  file="/workdir/spool.log"
  )
  }
  EOF

  Verify that the config is valid, then start a rsyslog server.

  $ sudo rsyslogd -f ./spool.conf -N9
  $ sudo rsyslogd -f ./spool.conf -i /workdir/rsyslogd.pid

  Fetch the rsyslogd PID and check for open files.

  $ RLOGPID=$(cat /workdir/rsyslogd.pid)
  $ sudo ls -l /proc/$RLOGPID/fd
  total 0
  lr-x-- 1 root root 64 Dec 17 01:22 0 -> /dev/urandom
  lrwx-- 1 root root 64 Dec 17 01:22 1 -> 'socket:[41228]'
  lrwx-- 1 root root 64 Dec 17 01:22 3 -> 'socket:[41222]'
  lrwx-- 1 root root 64 Dec 17 01:22 4 -> 'socket:[41223]'
  lrwx-- 1 root root 64 Dec 17 01:22 7 -> 'anon_inode:[eventpoll]'

  We have 3 sockets open by default. Next, use netcat to open 100
  connections:

  $ for i in {1..100} ; do nc -z 127.0.0.1 601 ; done

  Now check for open file descriptors, and there will be an extra 100 sockets
  in the list:

  $ sudo ls -l /proc/$RLOGPID/fd

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

  We can check the state of these sockets with:

  $ ss -t

  https://paste.ubuntu.com/p/7Ts2FbxJrg/

  The listening sockets will be in CLOSE-WAIT, and the netcat sockets
  will be in FIN-WAIT-2.

  $ ss -t | grep CLOSE-WAIT | wc -l
  100

  If you install the test package available in the following ppa:

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

[Touch-packages] [Bug 1901528] Re: [Ubuntu 20.10] - When zlib acceleration is enabled, gzip fails when given multiple files larger than 5KB (gzip)

2021-01-18 Thread Brian Murray
** Changed in: gzip (Ubuntu)
   Status: New => In Progress

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

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

Title:
  [Ubuntu 20.10] - When zlib acceleration is enabled, gzip fails when
  given multiple files larger than 5KB (gzip)

Status in Ubuntu on IBM z Systems:
  New
Status in gzip package in Ubuntu:
  In Progress
Status in zlib package in Ubuntu:
  Invalid

Bug description:
  When zlib acceleration is enabled, gzip fails when given multiple
  files larger than 5KB.

  This problem does not happen when running gzip against a single file
  at a time. It only happens when you provide multiple files as gzip
  arguments.

  So this works whether zlib acceleration is enabled or not:

  for file in file1 file2; do gzip $file ; done

  But this fails (when zlib acceleration is enabled):

  gzip file1 file2

  The patch to fix this has been accepted upstream:
  
https://git.savannah.gnu.org/cgit/gzip.git/commit/?id=be0a534ba2b6e77da289de8da79e70843b1028cc

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1901528/+subscriptions

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


[Touch-packages] [Bug 1911614] Re: Ubuntu 20.04 and 20.04.1 images use linux-generic-hwe-20.04 instead of linux-generic

2021-01-18 Thread Brian Murray
I did a fresh installation of the 20.04 LTS media from 20200423 and can
confirm this. See the attached screenshot.

** Attachment added: "Screenshot from 2021-01-18 09-46-39.png"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1911614/+attachment/5454217/+files/Screenshot%20from%202021-01-18%2009-46-39.png

** Tags added: rls-ff-incoming

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

Title:
  Ubuntu 20.04 and 20.04.1 images use linux-generic-hwe-20.04 instead of
  linux-generic

Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  Beginning about January 8th Focal users that installed Focal using
  either the Ubuntu 20.04 or 20.04.1 installation media began getting
  updated to the 5.8 series linux kernel. Those who had installed using
  the Ubuntu Focal Beta were not effected. This is because Focal Beta
  was properly built with ‘linux-generic’ but the 20.04 and 20.04.1
  images were built with ‘linux-generic-hwe-20.04‘. This can be easily
  verified by looking at the iso manifest:

  https://releases.ubuntu.com/20.04.1/ubuntu-20.04.1-desktop-
  amd64.manifest

  Note: old-release manifests (where 20.04 Beta and 20.04 reside) must
  be downloaded here:

  https://old-releases.ubuntu.com/releases/20.04/

  The expected behavior is for Ubuntu Focal users to remain on the 5.4
  series kernel unless they install with 20.04.2 or later images as
  indicated here:

  https://wiki.ubuntu.com/Kernel/LTSEnablementStack

  While not entirely updated it says “if one wants to remain on the
  original GA (General Availability) stacks, the options [include];
  Install from a previous
  12.04.0/12.04.1/14.04.0/14.04.1/16.04.0/16.04.1/18.04.0/18.04.1 point
  release and update”.

  Jump just below that to the Focal specific notes and it says “The
  20.04.2 and newer point releases will ship with an updated kernel and
  X stack by default for the desktop”. Since 20.04.2 is not even due for
  release until next month it makes no sense for updates to the 5.8
  series kernel to be occurring unless the focal-proposed repos are
  enabled even if HWE protocols had been changed.

  It’s also worth noting that thankfully no accompanying HWE X stack is
  yet available in the repos. I say thankfully because my efforts at
  downgrading the X stack in 16.04 and 18.04 were never successful! But
  the lack of a matching X stack may explain the many complaints on the
  forums about broken graphics???

  It’s also worth noting that even the release notes say that “Ubuntu
  20.04 LTS is based on the long-term supported Linux release series
  5.4“.

  https://wiki.ubuntu.com/FocalFossa/ReleaseNotes#Linux_Kernel

  Scroll to the bottom here and you’ll also see that 20.04 and 20.04.1
  are supposed to be supported with the 5.4 series kernel for the entire
  5 year life span:

  https://ubuntu.com/kernel/lifecycle

  The other flavors’ 20.04 and 20.04.1 images were all built correctly
  with ‘linux-generic’ with the possible exception of Ubuntu Studio
  which uses a kernel stack I’m not familiar with. I’m also uncertain
  about Ubuntu server because I’m simply not familiar with it.

  Original bug description below:

  ##

  Just as the title says, the 20.04 and 20.04.1 images use the HWE
  version of linux-generic resulting in upgrades to the 5.8 series
  kernel. This seems to effect Ubuntu only, or I should say I checked
  the Kubuntu, Ubuntu Mate, Xubuntu, and Lubuntu iso manifests which all
  correctly list linux-generic. Also HWE is not truly complete without
  the accompanying HWE Xstack.

  I checked all the documentation I could find and this was clearly not
  intentional. In fact the manifest for Ubuntu Focal Beta still used
  linux-generic, so this got messed up some time between April 3, 2020
  and April 23, 2020. Here's just one example of the documentation for
  kernel support in Focal LTS:

  https://ubuntu.com/about/release-cycle#ubuntu-kernel-release-cycle

  Installations performed with 20.04 and 20.04.1 media were supposed to
  remain on the 5.4 series kernel throughout Focal's 5 year lifespan as
  had been the case since HWE was introduced. The first step in fixing
  this needs to be stopping fresh installs of Focal using the 20.04 and
  20.04.1 media from immediately upgrading to the 5.8 series kernel.

  It might be a little tricky to revert users from 5.8 to 5.4, but there
  have been reports of breakage, particularly concerning Broadcom wifi
  drivers and some graphics problems. But the graphics problems could
  also be exacerbated by the lack of the matching HWE Xstack? At any
  rate it's a bug.

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

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

[Touch-packages] [Bug 1911802] Re: Video glitches playing hardware accelerated video through VAAPI

2021-01-18 Thread Brian Murray
** Tags added: rls-ff-incoming

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

Title:
  Video glitches playing hardware accelerated video through VAAPI

Status in mesa package in Ubuntu:
  New

Bug description:
  Same issue as the post here describes:
  https://gitlab.freedesktop.org/mesa/mesa/-/issues/3681

  The video is scaled unevenly in the vertical axis, with a black bar
  appearing in the bottom of the video window for a few frames. It
  happens seemingly on all videos able to be hardware decoded, upon
  starting the video and upon seeking.

  The regression happened somewhere between 20.0.8-0ubuntu1~20.04.1 and
  20.2.6-0ubuntu0.20.04.1 but apparently has been fixed in mesa 20.3

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

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


[Touch-packages] [Bug 1911456] Re: Can't receive files over bluetooth unless settings dialog is open

2021-01-14 Thread Brian Murray
** Tags added: focal

** Package changed: ubuntu => bluez (Ubuntu)

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

Title:
  Can't receive files over bluetooth unless settings dialog is open

Status in bluez package in Ubuntu:
  New

Bug description:
  On 18.04 I could send files from my phone to my laptop at any time.
  On 20.04 I can't get files to be accepted by the laptop over bluetooth. After 
much frustration and experimenting, I figured out that it will work, but only 
if the bluetooth settings dialog is open. If the settings dialog is not open, 
the incoming file is rejected.  If the dialog is closed after the file transfer 
begins, the transfer continues but the file is discarded when the transfer is 
complete.  This is very frustrating.
  I need to be able to send files (mostly photos and videos) from my phone to 
my laptop without having to open the settings dialog on the laptop, just like I 
could before upgrading.

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

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


[Touch-packages] [Bug 1905627] Re: Bluetooth stops working on Raspberry Pi 4 with bluez 5.55-0ubuntu1.1

2021-01-14 Thread Brian Murray
** Also affects: bluez (Ubuntu Groovy)
   Importance: Undecided
   Status: New

** Also affects: bluez (Ubuntu Hirsute)
   Importance: High
 Assignee: Dave Jones (waveform)
   Status: New

** Tags removed: rls-gg-incoming rls-hh-incoming

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

Title:
  Bluetooth stops working on Raspberry Pi 4 with bluez 5.55-0ubuntu1.1

Status in bluez package in Ubuntu:
  New
Status in bluez source package in Groovy:
  New
Status in bluez source package in Hirsute:
  New

Bug description:
  Bluetooth stops working after updating to bluez version
  5.55-0ubuntu1.1. /usr/bin/btuart returns "bcm43xx_init Initialization
  timed out". Bluetooth is working again if bluez is reverted to version
  5.55-0ubuntu1. I don't have any unusual setup like miniuart-bt.

  Release:  20.10
  bluez:
Installed: 5.55-0ubuntu1.1
Candidate: 5.55-0ubuntu1.1
Version table:
   *** 5.55-0ubuntu1.1 500
  500 http://ports.ubuntu.com/ubuntu-ports groovy-updates/main arm64 
Packages
  100 /var/lib/dpkg/status
   5.55-0ubuntu1 500
  500 http://ports.ubuntu.com/ubuntu-ports groovy/main arm64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: bluez 5.55-0ubuntu1.1
  ProcVersionSignature: Ubuntu 5.8.0-1007.10-raspi 5.8.14
  Uname: Linux 5.8.0-1007-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu50.2
  Architecture: arm64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 25 16:09:03 2020
  ImageMediaBuild: 20200423.1
  InterestingModules: bnep bluetooth
  Lspci-vt: -[:00]---00.0-[01]00.0  VIA Technologies, Inc. VL805 USB 
3.0 Host Controller
  Lsusb:
   Bus 002 Device 002: ID 1058:25ee Western Digital Technologies, Inc. My Book 
25EE
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
   |__ Port 2: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M
   |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
  ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 
snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 
snd_bcm2835.enable_headphones=1 video=HDMI-A-1:1920x1080M@60 
smsc95xx.macaddr=DC:A6:32:B9:18:CC vc_mem.mem_base=0x3eb0 
vc_mem.mem_size=0x3ff0  dwc_otg.lpm_enable=0 console=tty1 
root=PARTUUID=5f9d0997-1b4e-423b-ad5e-8bce1a7e1ae4 rootfstype=ext4 
elevator=deadline rootwait fixrtc
  SourcePackage: bluez
  UpgradeStatus: Upgraded to groovy on 2020-10-23 (33 days ago)
  acpidump:
   
  hciconfig:
   
  rfkill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

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

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


[Touch-packages] [Bug 1908756] Re: Ubuntu 20.10 - elfutils unwinding broken for s390 compat

2021-01-12 Thread Brian Murray
Hello bugproxy, or anyone else affected,

Accepted elfutils into groovy-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/elfutils/0.181-1ubuntu0.1 in a few
hours, and then in the -proposed repository.

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

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

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

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

** Changed in: elfutils (Ubuntu Groovy)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-groovy

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

Title:
  Ubuntu 20.10 - elfutils unwinding broken for s390 compat

Status in Ubuntu on IBM z Systems:
  In Progress
Status in elfutils package in Ubuntu:
  Fix Released
Status in elfutils source package in Groovy:
  Fix Committed
Status in elfutils source package in Hirsute:
  Fix Released

Bug description:
  SRU Bug Template:
  =

  [Impact]

   * There is an endianess problem in pid_memory_read that impacts
  s390x.

   * Due to this elfutils biarch test fails on s390x doing unwinding for
  a 32 bit process.

  [Fix]

   * e4d985a3c1c873f77d20fa0cd421458cc2824996 e4d985a3 "IBM Z: Fix endianess 
problem in pid_memory_read"
   
  [Test Case]

   * Have an Ubuntu Server 20.10 system or newer installed on LPAR, z/VM or KVM 
that comes with elfutils 0.181 or 0.182.
   
   * Run the test script: 'run-backtrace-native-biarch.sh'
   
   * It either core dumps without the patch  in place - look for 
"/test-subr.sh: line 84: 376822 Aborted (core dumped)" or succeeds.
   
   [Where problems could occur]
   
   * If the translation is not done right (shift of the upper 4 bytes + down on 
big endian 64 bit targets) the situation is broken in the same way, and things 
stay the same.
   
   * But in worst case the changes in 'pid_memory_read' of 
/libdwfl/linux-pid-attach.c could have a negative impact even on architectures 
other than s390x, in case the check for the endiness is wrong.
   
   * But the changes are quite traceable and the additional code that fixes the 
endianess problem is really only active on a big endian architecture.
   
   [Other]
   
   * The fix is upstream accepted with elfutils > 0.182.
  __

  ---Problem Description---
  libdw unwinding fails for 32 bit binaries.

  Elfutils biarch test currently fails on s390x doing unwinding for a 32
  bit process.

  FAIL: run-backtrace-native-biarch.sh
  

  0x557e7000  0x557eb000  /root/elfutils/tests/backtrace-child-biarch
  0x7dba4000  0x7dd51000  /usr/lib/libc-2.32.so
  0x7dd53000  0x7dd7  /usr/lib/libpthread-2.32.so
  0x7dd7f000  0x7dda6000  /usr/lib/ld-2.32.so
  TID 376858:
  # 0 0x7dd6668a  raise
  # 1 0x7fd0ef60 - 1  
  /root/elfutils/tests/backtrace: dwfl_thread_getframes: No DWARF information 
found
  backtrace: backtrace.c:114: callback_verify: Assertion `symname != NULL && 
strcmp (symname, "sigusr2") == 0' failed.
  ./test-subr.sh: line 84: 376822 Aborted (core dumped) 
LD_LIBRARY_PATH="${built_library_path}${LD_LIBRARY_PATH:+:}$LD_LIBRARY_PATH" 
$VALGRIND_CMD "$@"
  backtrace-child-biarch: no main
  FAIL run-backtrace-native-biarch.sh (exit status: 1)

  Patch has already been posted and upstream committed:
  https://sourceware.org/pipermail/elfutils-devel/2020q4/003149.html

  Please pick up the following commit for the next release:
  commit e4d985a3c1c873f77d20fa0cd421458cc2824996
  Author: Andreas Krebbel 
  Date:   Thu Nov 19 20:32:24 2020 +0100

  IBM Z: Fix endianess problem in pid_memory_read

  The cached reads lack the big endian adjustments done in the fallback
  path.

  Signed-off-by: Andreas Krebbel 

  The patch applies cleanly ontop of elfutils_0.181-1.

  
  strace right now is not built with unwinding support for IBM Z although both 
variants should work - libdw and libunwind.

  Other distros use libdw from 

[Touch-packages] [Bug 1910636] Re: update icu-data which is bundled in tzdata to 2020f

2021-01-11 Thread Brian Murray
The verification passed for focal.

bdmurray@clean-focal-amd64:~$ python3 -c "from datetime import datetime; from 
icu import ICUtzinfo, TimeZone; tz = ICUtzinfo(TimeZone.create
TimeZone('Europe/Volgograd')); print(str(tz.utcoffset(datetime(2020, 12, 28"
4:00:00
bdmurray@clean-focal-amd64:~$ sudo apt-get install tzdata
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following packages will be upgraded:
  tzdata
1 upgraded, 0 newly installed, 0 to remove and 91 not upgraded.
Need to get 296 kB of archives.
After this operation, 6,144 B of additional disk space will be used.
Get:1 http://192.168.10.7/ubuntu focal-proposed/main amd64 tzdata all 
2020f-0ubuntu0.20.04.1 [296 kB]
Fetched 296 kB in 0s (6,181 kB/s)
Preconfiguring packages ...
(Reading database ... 223591 files and directories currently installed.)
Preparing to unpack .../tzdata_2020f-0ubuntu0.20.04.1_all.deb ...
Unpacking tzdata (2020f-0ubuntu0.20.04.1) over (2020d-0ubuntu0.20.04) ...
Setting up tzdata (2020f-0ubuntu0.20.04.1) ...

Current default time zone: 'America/Los_Angeles'
Local time is now:  Mon Jan 11 19:15:47 PST 2021.
Universal Time is now:  Tue Jan 12 03:15:47 UTC 2021.
Run 'dpkg-reconfigure tzdata' if you wish to change it.

bdmurray@clean-focal-amd64:~$ python3 -c "from datetime import datetime; from 
icu import ICUtzinfo, TimeZone; tz = ICUtzinfo(TimeZone.create
TimeZone('Europe/Volgograd')); print(str(tz.utcoffset(datetime(2020, 12, 28"
3:00:00

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

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

Title:
  update icu-data which is bundled in tzdata to 2020f

Status in tzdata package in Ubuntu:
  Fix Released
Status in tzdata source package in Focal:
  Fix Committed
Status in tzdata source package in Groovy:
  Fix Committed
Status in tzdata source package in Hirsute:
  Fix Released

Bug description:
  The 2020f upload of tzdata did not include an update of the ICU
  timezone data because it was not yet up to date. It has now been
  updated so we should update tzdata with that new information.

  tzdata (2020f-1ubuntu1) hirsute; urgency=medium

    * Merge from Debian unstable (LP: 1909698). Remaining changes:
  - Ship ICU timezone data files which are utilized by php and keep them
    at 2020d as they have not yet been updated.

  [Test Case]
  1) sudo apt-get install python3-icu
  2) python3 -c "from datetime import datetime; from icu import ICUtzinfo, 
TimeZone; tz = ICUtzinfo(TimeZone.creat
  eTimeZone('Europe/Volgograd')); print(str(tz.utcoffset(datetime(2020, 12, 
28"

  Before the SRU it will return 3:00:00, after the SRU it will return
  4:00:00.

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

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


[Touch-packages] [Bug 1910636] Re: update icu-data which is bundled in tzdata to 2020f

2021-01-11 Thread Brian Murray
The verification passed for groovy.

bdmurray@clean-groovy-amd64:~$ python3 -c "from datetime import datetime; from 
icu import ICUtzinfo, TimeZone; tz = ICUtzinfo(TimeZone.creat
eTimeZone('Europe/Volgograd')); print(str(tz.utcoffset(datetime(2020, 12, 
28"
4:00:00
bdmurray@clean-groovy-amd64:~$ sudo apt-get install tzdata
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following packages were automatically installed and are no longer required:
  ippusbxd libllvm10 libtepl-4-0 linux-headers-5.4.0-42 
linux-headers-5.4.0-42-generic linux-image-5.4.0-42-generic
  linux-modules-5.4.0-42-generic linux-modules-extra-5.4.0-42-generic
Use 'sudo apt autoremove' to remove them.
The following packages will be upgraded:
  tzdata
1 upgraded, 0 newly installed, 0 to remove and 180 not upgraded.
Need to get 294 kB of archives.
After this operation, 6,144 B of additional disk space will be used.
Get:1 http://192.168.10.7/ubuntu groovy-proposed/main amd64 tzdata all 
2020f-0ubuntu0.20.10.1 [294 kB]
Fetched 294 kB in 0s (5,658 kB/s)
Preconfiguring packages ...
(Reading database ... 228033 files and directories currently installed.)
Preparing to unpack .../tzdata_2020f-0ubuntu0.20.10.1_all.deb ...
Unpacking tzdata (2020f-0ubuntu0.20.10.1) over (2020d-1ubuntu1) ...
Setting up tzdata (2020f-0ubuntu0.20.10.1) ...

Current default time zone: 'America/Los_Angeles'
Local time is now:  Mon Jan 11 19:10:44 PST 2021.
Universal Time is now:  Tue Jan 12 03:10:44 UTC 2021.
Run 'dpkg-reconfigure tzdata' if you wish to change it.

bdmurray@clean-groovy-amd64:~$ python3 -c "from datetime import datetime; from 
icu import ICUtzinfo, TimeZone; tz = ICUtzinfo(TimeZone.creat
eTimeZone('Europe/Volgograd')); print(str(tz.utcoffset(datetime(2020, 12, 
28"
3:00:00

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

Title:
  update icu-data which is bundled in tzdata to 2020f

Status in tzdata package in Ubuntu:
  Fix Released
Status in tzdata source package in Focal:
  Fix Committed
Status in tzdata source package in Groovy:
  Fix Committed
Status in tzdata source package in Hirsute:
  Fix Released

Bug description:
  The 2020f upload of tzdata did not include an update of the ICU
  timezone data because it was not yet up to date. It has now been
  updated so we should update tzdata with that new information.

  tzdata (2020f-1ubuntu1) hirsute; urgency=medium

    * Merge from Debian unstable (LP: 1909698). Remaining changes:
  - Ship ICU timezone data files which are utilized by php and keep them
    at 2020d as they have not yet been updated.

  [Test Case]
  1) sudo apt-get install python3-icu
  2) python3 -c "from datetime import datetime; from icu import ICUtzinfo, 
TimeZone; tz = ICUtzinfo(TimeZone.creat
  eTimeZone('Europe/Volgograd')); print(str(tz.utcoffset(datetime(2020, 12, 
28"

  Before the SRU it will return 3:00:00, after the SRU it will return
  4:00:00.

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

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


[Touch-packages] [Bug 1907956] Re: ubiquity crash on whoopsie removal, Xubuntu 21.04 minimal install

2021-01-11 Thread Brian Murray
** Changed in: whoopsie (Ubuntu Hirsute)
   Importance: Undecided => High

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

Title:
  ubiquity crash on whoopsie removal, Xubuntu 21.04 minimal install

Status in ubiquity package in Ubuntu:
  New
Status in whoopsie package in Ubuntu:
  New
Status in ubiquity source package in Hirsute:
  New
Status in whoopsie source package in Hirsute:
  New

Bug description:
  Xubuntu hirsute 20201213 minimal install crashed on whoopsie removal
  but finished installing. This is 1907951 with hopefully more crash
  information.

  Related logs identified:
  Dec 13 12:37:05 xubuntu ubiquity: Purging configuration files for whoopsie 
(0.2.73) ...
  Dec 13 12:37:05 xubuntu ubiquity: #015
  Dec 13 12:37:05 xubuntu ubiquity: Running in chroot, ignoring command 
'daemon-reload'#015
  Dec 13 12:37:05 xubuntu ubiquity: message repeated 2 times: [ Running in 
chroot, ignoring command 'daemon-reload'#015]
  Dec 13 12:37:05 xubuntu ubiquity: rm:
  Dec 13 12:37:05 xubuntu ubiquity: cannot remove 
'/var/lib/whoopsie/whoopsie-id'
  Dec 13 12:37:05 xubuntu ubiquity: : No such file or directory
  Dec 13 12:37:05 xubuntu ubiquity: #015
  Dec 13 12:37:05 xubuntu ubiquity: dpkg: error processing package whoopsie 
(--purge):
  Dec 13 12:37:05 xubuntu ubiquity: #015
  Dec 13 12:37:05 xubuntu ubiquity:  installed whoopsie package post-removal 
script subprocess returned error exit status 1
  Dec 13 12:37:05 xubuntu ubiquity: #015

  Looks like it's a bug in the postrm script:
  #! /bin/sh

  set -e

  #DEBHELPER#

  if [ "$1" = "purge" ]; then
  deluser --quiet --system whoopsie > /dev/null || true
  chmod g-s /var/crash >/dev/null 2>&1
  chgrp root /var/crash >/dev/null 2>&1
  rm /var/lib/whoopsie/whoopsie-id >/dev/null
  fi

  exit 0

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: ubiquity 21.04.3
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu55
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.456
  Date: Sun Dec 13 07:40:33 2020
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/xubuntu.seed 
maybe-ubiquity quiet splash ---
  LiveMediaBuild: Xubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201213)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
  RebootRequiredPkgs:
   linux-image-5.8.0-25-generic
   linux-base
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1910636] Re: update icu-data which is bundled in tzdata to 2020f

2021-01-08 Thread Brian Murray
** Description changed:

  The 2020f upload of tzdata did not include an update of the ICU timezone
  data because it was not yet up to date. It has now been updated so we
  should update tzdata with that new information.
  
  tzdata (2020f-1ubuntu1) hirsute; urgency=medium
  
-   * Merge from Debian unstable (LP: 1909698). Remaining changes:
- - Ship ICU timezone data files which are utilized by php and keep them
-   at 2020d as they have not yet been updated.
+   * Merge from Debian unstable (LP: 1909698). Remaining changes:
+ - Ship ICU timezone data files which are utilized by php and keep them
+   at 2020d as they have not yet been updated.
+ 
+ [Test Case]
+ python3 -c "from datetime import datetime; from icu import ICUtzinfo, 
TimeZone; tz = ICUtzinfo(TimeZone.creat
+ eTimeZone('Europe/Volgograd')); print(str(tz.utcoffset(datetime(2020, 12, 
28"
+ 
+ Before the SRU it will return 3:00:00, after the SRU it will return
+ 4:00:00.

** Description changed:

  The 2020f upload of tzdata did not include an update of the ICU timezone
  data because it was not yet up to date. It has now been updated so we
  should update tzdata with that new information.
  
  tzdata (2020f-1ubuntu1) hirsute; urgency=medium
  
    * Merge from Debian unstable (LP: 1909698). Remaining changes:
  - Ship ICU timezone data files which are utilized by php and keep them
    at 2020d as they have not yet been updated.
  
  [Test Case]
- python3 -c "from datetime import datetime; from icu import ICUtzinfo, 
TimeZone; tz = ICUtzinfo(TimeZone.creat
+ 1) sudo apt-get install python3-icu
+ 2) python3 -c "from datetime import datetime; from icu import ICUtzinfo, 
TimeZone; tz = ICUtzinfo(TimeZone.creat
  eTimeZone('Europe/Volgograd')); print(str(tz.utcoffset(datetime(2020, 12, 
28"
  
  Before the SRU it will return 3:00:00, after the SRU it will return
  4:00:00.

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

Title:
  update icu-data which is bundled in tzdata to 2020f

Status in tzdata package in Ubuntu:
  In Progress
Status in tzdata source package in Focal:
  In Progress
Status in tzdata source package in Groovy:
  In Progress
Status in tzdata source package in Hirsute:
  In Progress

Bug description:
  The 2020f upload of tzdata did not include an update of the ICU
  timezone data because it was not yet up to date. It has now been
  updated so we should update tzdata with that new information.

  tzdata (2020f-1ubuntu1) hirsute; urgency=medium

    * Merge from Debian unstable (LP: 1909698). Remaining changes:
  - Ship ICU timezone data files which are utilized by php and keep them
    at 2020d as they have not yet been updated.

  [Test Case]
  1) sudo apt-get install python3-icu
  2) python3 -c "from datetime import datetime; from icu import ICUtzinfo, 
TimeZone; tz = ICUtzinfo(TimeZone.creat
  eTimeZone('Europe/Volgograd')); print(str(tz.utcoffset(datetime(2020, 12, 
28"

  Before the SRU it will return 3:00:00, after the SRU it will return
  4:00:00.

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

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


[Touch-packages] [Bug 1910604] Re: /usr/share/apport/apport:AttributeError:/usr/share/apport/apport@458:parse_arguments:print_usage:_print_message

2021-01-08 Thread Brian Murray
*** This bug is a duplicate of bug 1903567 ***
https://bugs.launchpad.net/bugs/1903567

** This bug has been marked a duplicate of bug 1903567
   
/usr/share/apport/apport:AttributeError:/usr/share/apport/apport@447:parse_arguments:print_usage:_print_message

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

Title:
  
/usr/share/apport/apport:AttributeError:/usr/share/apport/apport@458:parse_arguments:print_usage:_print_message

Status in apport package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.20.11-0ubuntu27.12, the problem page at 
https://errors.ubuntu.com/problem/9b24bfd33f42cf15ca4956317629b13c340448e4 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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


[Touch-packages] [Bug 1874381] Re: LVM device unavailable after 18.04 to 20.04 upgrade Timed out waiting for device /dev/mapper/s5lp8--v g-home

2021-01-08 Thread Brian Murray
** Changed in: lvm2 (Ubuntu Focal)
Milestone: ubuntu-20.04.1 => ubuntu-20.04.2

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

Title:
  LVM device unavailable after 18.04 to 20.04 upgrade Timed out waiting
  for device /dev/mapper/s5lp8--v g-home

Status in Ubuntu on IBM z Systems:
  Confirmed
Status in lvm2 package in Ubuntu:
  Confirmed
Status in lvm2 source package in Focal:
  Confirmed

Bug description:
  After upgrading an LPAR configured with LVM from 18.04 to 20.04 /home is no 
longer mounted.
  During boot the console shows Timed out waiting for device 
/dev/mapper/s5lp8--vg-home

  Please see the attached dist-upgrade logs and console output for more
  detail.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874381/+subscriptions

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


[Touch-packages] [Bug 1910584] Re: ifup is iterating over all vlan sub vlan interfaces for ens interfaces

2021-01-08 Thread Brian Murray
** Tags added: bionic

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

Title:
  ifup is iterating over all vlan sub vlan interfaces for ens interfaces

Status in ifupdown package in Ubuntu:
  New

Bug description:
  I expect that a single ifup call with just one vlan interface will NOT bring 
up all sub vlan interfaces too
  but on my ubuntu 18.04.02 I do see this

  root@dsr-router-1:~# ifup ens19.2023
  ens19.2023
  Set name-type for VLAN subsystem. Should be visible in /proc/net/vlan/config
  ens19.2023.4
  Set name-type for VLAN subsystem. Should be visible in /proc/net/vlan/config
  Added VLAN with VID == 4 to IF -:ens19.2023:-
  ens19.2023.4090
  Set name-type for VLAN subsystem. Should be visible in /proc/net/vlan/config
  Added VLAN with VID == 4090 to IF -:ens19.2023:-
  root@dsr-router-1:~# 

  more is written at> https://askubuntu.com/questions/1305801

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

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


[Touch-packages] [Bug 1910636] [NEW] update icu-data which is bundled in tzdata to 2020f

2021-01-07 Thread Brian Murray
Public bug reported:

The 2020f upload of tzdata did not include an update of the ICU timezone
data because it was not yet up to date. It has now been updated so we
should update tzdata with that new information.

tzdata (2020f-1ubuntu1) hirsute; urgency=medium

  * Merge from Debian unstable (LP: 1909698). Remaining changes:
- Ship ICU timezone data files which are utilized by php and keep them
  at 2020d as they have not yet been updated.

** Affects: tzdata (Ubuntu)
 Importance: Undecided
 Assignee: Brian Murray (brian-murray)
 Status: In Progress

** Affects: tzdata (Ubuntu Focal)
 Importance: Undecided
 Assignee: Brian Murray (brian-murray)
 Status: In Progress

** Affects: tzdata (Ubuntu Groovy)
 Importance: Undecided
 Assignee: Brian Murray (brian-murray)
 Status: In Progress

** Affects: tzdata (Ubuntu Hirsute)
 Importance: Undecided
 Assignee: Brian Murray (brian-murray)
 Status: In Progress

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

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

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

** Changed in: tzdata (Ubuntu Hirsute)
 Assignee: (unassigned) => Brian Murray (brian-murray)

** Changed in: tzdata (Ubuntu Groovy)
 Assignee: (unassigned) => Brian Murray (brian-murray)

** Changed in: tzdata (Ubuntu Focal)
 Assignee: (unassigned) => Brian Murray (brian-murray)

** Changed in: tzdata (Ubuntu Hirsute)
   Status: New => In Progress

** Changed in: tzdata (Ubuntu Groovy)
   Status: New => In Progress

** Changed in: tzdata (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 tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1910636

Title:
  update icu-data which is bundled in tzdata to 2020f

Status in tzdata package in Ubuntu:
  In Progress
Status in tzdata source package in Focal:
  In Progress
Status in tzdata source package in Groovy:
  In Progress
Status in tzdata source package in Hirsute:
  In Progress

Bug description:
  The 2020f upload of tzdata did not include an update of the ICU
  timezone data because it was not yet up to date. It has now been
  updated so we should update tzdata with that new information.

  tzdata (2020f-1ubuntu1) hirsute; urgency=medium

* Merge from Debian unstable (LP: 1909698). Remaining changes:
  - Ship ICU timezone data files which are utilized by php and keep them
at 2020d as they have not yet been updated.

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

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


[Touch-packages] [Bug 1910604] Re: /usr/share/apport/apport:AttributeError:/usr/share/apport/apport@458:parse_arguments:print_usage:_print_message

2021-01-07 Thread Brian Murray
** Tags added: rls-hh-incoming

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

Title:
  
/usr/share/apport/apport:AttributeError:/usr/share/apport/apport@458:parse_arguments:print_usage:_print_message

Status in apport package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.20.11-0ubuntu27.12, the problem page at 
https://errors.ubuntu.com/problem/9b24bfd33f42cf15ca4956317629b13c340448e4 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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


[Touch-packages] [Bug 1910604] Re: /usr/share/apport/apport:AttributeError:/usr/share/apport/apport@458:parse_arguments:print_usage:_print_message

2021-01-07 Thread Brian Murray
This is a variation of LP: #1899195 however in this case the executable
path has a space in the name e.g.

/usr/lib/plexmediaserver/Plex Media Server

which ends up being split into multiple arguments:

['/usr/share/apport/apport', '1700', '11', '0', '1', '1700',
'!usr!lib!plexmediaserver!Plex', 'Media', 'Server']

Which is more than apport expects.

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

Title:
  
/usr/share/apport/apport:AttributeError:/usr/share/apport/apport@458:parse_arguments:print_usage:_print_message

Status in apport package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.20.11-0ubuntu27.12, the problem page at 
https://errors.ubuntu.com/problem/9b24bfd33f42cf15ca4956317629b13c340448e4 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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


[Touch-packages] [Bug 1910604] Re: /usr/share/apport/apport:AttributeError:/usr/share/apport/apport@458:parse_arguments:print_usage:_print_message

2021-01-07 Thread Brian Murray
Here's the Traceback:

Traceback (most recent call last):
  File "/usr/share/apport/apport", line 458, in 
options = parse_arguments()
  File "/usr/share/apport/apport", line 404, in parse_arguments
parser.print_usage()
  File "/usr/lib/python3.6/argparse.py", line 2370, in print_usage
self._print_message(self.format_usage(), file)
  File "/usr/lib/python3.6/argparse.py", line 2381, in _print_message
file.write(message)
AttributeError: 'NoneType' object has no attribute 'write'

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

Title:
  
/usr/share/apport/apport:AttributeError:/usr/share/apport/apport@458:parse_arguments:print_usage:_print_message

Status in apport package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.20.11-0ubuntu27.12, the problem page at 
https://errors.ubuntu.com/problem/9b24bfd33f42cf15ca4956317629b13c340448e4 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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


[Touch-packages] [Bug 1867400] Re: apport crashed with AttributeError in _print_message(): 'NoneType' object has no attribute 'write'

2021-01-07 Thread Brian Murray
*** This bug is a duplicate of bug 1899195 ***
https://bugs.launchpad.net/bugs/1899195

** Information type changed from Private to Public

** This bug has been marked a duplicate of bug 1899195
   
/usr/share/apport/apport:AttributeError:/usr/share/apport/apport@451:parse_arguments:print_usage:_print_message

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

Title:
  apport crashed with AttributeError in _print_message(): 'NoneType'
  object has no attribute 'write'

Status in apport package in Ubuntu:
  New

Bug description:
  d

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: apport 2.20.11-0ubuntu20
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  CrashReports: 640:0:119:25768:2020-03-13 16:01:33.222412109 -0600:2020-03-13 
16:01:34.222412109 -0600:/var/crash/_usr_share_apport_apport.0.crash
  Date: Fri Mar 13 16:01:34 2020
  ExecutablePath: /usr/share/apport/apport
  InstallationDate: Installed on 2018-02-07 (765 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  InterpreterPath: /usr/bin/python3.8
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport 1383 11 0 1 1383 
!usr!bin!gnome-shell (deleted)
  ProcEnviron:
   
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu1
  PythonArgs: ['/usr/share/apport/apport', '1383', '11', '0', '1', '1383', 
'!usr!bin!gnome-shell', '(deleted)']
  PythonDetails: N/A
  SourcePackage: apport
  Title: apport crashed with AttributeError in _print_message(): 'NoneType' 
object has no attribute 'write'
  UpgradeStatus: Upgraded to focal on 2020-03-13 (0 days ago)
  UserGroups:

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

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


[Touch-packages] [Bug 1907850] Re: Cache not generated for all translations

2021-01-07 Thread Brian Murray
** Tags removed: rls-hh-incoming

** Also affects: apt (Ubuntu Hirsute)
   Importance: Undecided
   Status: Confirmed

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

Title:
  Cache not generated for all translations

Status in apt package in Ubuntu:
  Confirmed
Status in apt source package in Hirsute:
  Confirmed

Bug description:
  [Impact]
  In bug 1161743 we discovered that if a system is configured with multiple 
locales, only the locales of the user who generated the apt-cache will be 
available for translated descriptions.

  [Test case]

  # apt install locales-all # get the locale
  # export LANG=sv_SE.UTF-8
  # locale
  LANG=sv_SE.UTF-8
  LANGUAGE=
  LC_CTYPE="sv_SE.UTF-8"
  LC_NUMERIC="sv_SE.UTF-8"
  LC_TIME="sv_SE.UTF-8"
  LC_COLLATE="sv_SE.UTF-8"
  LC_MONETARY="sv_SE.UTF-8"
  LC_MESSAGES="sv_SE.UTF-8"
  LC_PAPER="sv_SE.UTF-8"
  LC_NAME="sv_SE.UTF-8"
  LC_ADDRESS="sv_SE.UTF-8"
  LC_TELEPHONE="sv_SE.UTF-8"
  LC_MEASUREMENT="sv_SE.UTF-8"
  LC_IDENTIFICATION="sv_SE.UTF-8"
  LC_ALL=
  # apt update
  # apt-cache show tasksel | grep Desc
  Description-sv: tool for selecting tasks for installation on Debian systems
  Description-md5: cbbb747708986d11ea77c80b9b038fec
  # apt-cache showpkg tasksel
  Package: tasksel
  Versions:
  3.34ubuntu16 
(/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_binary-amd64_Packages)
   Description Language:
   File: 
/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_binary-amd64_Packages
    MD5: cbbb747708986d11ea77c80b9b038fec
   Description Language: sv
   File: 
/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_i18n_Translation-sv
    MD5: cbbb747708986d11ea77c80b9b038fec
   Description Language: en
   File: 
/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_i18n_Translation-en
    MD5: cbbb747708986d11ea77c80b9b038fec
  [...]

  So far so good, but now assume the root user actually has C configured
  as locale, and e.g. runs apt-cache show (or apt-daily.service does an
  update):

  root@g:~# rm /var/cache/apt/*.bin
  root@g:~# LANG=C apt-cache  show tasksel
  [...]
  Description-en: tool for selecting tasks for installation on Debian systems
   This package provides 'tasksel', a simple interface for users who
   want to configure their system to perform a specific task.

  root@g:~# apt-cache  showpkg tasksel
  Package: tasksel
  Versions:
  3.34ubuntu16 
(/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_binary-amd64_Packages)
   Description Language:
   File: 
/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_binary-amd64_Packages
    MD5: cbbb747708986d11ea77c80b9b038fec
   Description Language: en
   File: 
/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_i18n_Translation-en
    MD5: cbbb747708986d11ea77c80b9b038fec

  This should show the sv locale as well given that it's still around
  (also we are still running with LANG=sv_SE.UTF-8), but it only
  generated the cache with the english language description in here.

  [Where problems could occur]
  Unknown so far, we've not investigated the cause or solution yet.

  [Other Info]
  N/A

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

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


[Touch-packages] [Bug 1907956] Re: ubiquity crash on whoopsie removal, Xubuntu 21.04 minimal install

2021-01-07 Thread Brian Murray
** Also affects: ubiquity (Ubuntu Hirsute)
   Importance: Undecided
   Status: New

** Also affects: whoopsie (Ubuntu Hirsute)
   Importance: Undecided
   Status: New

** Tags removed: rls-hh-incoming

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

Title:
  ubiquity crash on whoopsie removal, Xubuntu 21.04 minimal install

Status in ubiquity package in Ubuntu:
  New
Status in whoopsie package in Ubuntu:
  New
Status in ubiquity source package in Hirsute:
  New
Status in whoopsie source package in Hirsute:
  New

Bug description:
  Xubuntu hirsute 20201213 minimal install crashed on whoopsie removal
  but finished installing. This is 1907951 with hopefully more crash
  information.

  Related logs identified:
  Dec 13 12:37:05 xubuntu ubiquity: Purging configuration files for whoopsie 
(0.2.73) ...
  Dec 13 12:37:05 xubuntu ubiquity: #015
  Dec 13 12:37:05 xubuntu ubiquity: Running in chroot, ignoring command 
'daemon-reload'#015
  Dec 13 12:37:05 xubuntu ubiquity: message repeated 2 times: [ Running in 
chroot, ignoring command 'daemon-reload'#015]
  Dec 13 12:37:05 xubuntu ubiquity: rm:
  Dec 13 12:37:05 xubuntu ubiquity: cannot remove 
'/var/lib/whoopsie/whoopsie-id'
  Dec 13 12:37:05 xubuntu ubiquity: : No such file or directory
  Dec 13 12:37:05 xubuntu ubiquity: #015
  Dec 13 12:37:05 xubuntu ubiquity: dpkg: error processing package whoopsie 
(--purge):
  Dec 13 12:37:05 xubuntu ubiquity: #015
  Dec 13 12:37:05 xubuntu ubiquity:  installed whoopsie package post-removal 
script subprocess returned error exit status 1
  Dec 13 12:37:05 xubuntu ubiquity: #015

  Looks like it's a bug in the postrm script:
  #! /bin/sh

  set -e

  #DEBHELPER#

  if [ "$1" = "purge" ]; then
  deluser --quiet --system whoopsie > /dev/null || true
  chmod g-s /var/crash >/dev/null 2>&1
  chgrp root /var/crash >/dev/null 2>&1
  rm /var/lib/whoopsie/whoopsie-id >/dev/null
  fi

  exit 0

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: ubiquity 21.04.3
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu55
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.456
  Date: Sun Dec 13 07:40:33 2020
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/xubuntu.seed 
maybe-ubiquity quiet splash ---
  LiveMediaBuild: Xubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201213)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
  RebootRequiredPkgs:
   linux-image-5.8.0-25-generic
   linux-base
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1909698] Re: new upstream release 2020f

2021-01-06 Thread Brian Murray
Verified on xenial:

(xenial-amd64)root@impulse:~# apt-cache policy tzdata   
   
tzdata:
  Installed: 2020f-0ubuntu0.16.04
  Candidate: 2020f-0ubuntu0.16.04
  Version table:
 *** 2020f-0ubuntu0.16.04 500
500 http://archive.ubuntu.com//ubuntu xenial-proposed/main amd64 
Packages
100 /var/lib/dpkg/status
 2020d-0ubuntu0.16.04 500
500 http://ubuntu.osuosl.org/ubuntu xenial-updates/main amd64 Packages
500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
 2016d-0ubuntu0.16.04 500
500 http://ubuntu.osuosl.org/ubuntu xenial/main amd64 Packages
(xenial-amd64)root@impulse:~# zdump -v Europe/Volgograd | tail -n6
Europe/Volgograd  Sat Oct 27 22:59:59 2018 UT = Sun Oct 28 01:59:59 2018 +03 
isdst=0 gmtoff=10800
Europe/Volgograd  Sat Oct 27 23:00:00 2018 UT = Sun Oct 28 03:00:00 2018 +04 
isdst=0 gmtoff=14400
Europe/Volgograd  Sat Dec 26 21:59:59 2020 UT = Sun Dec 27 01:59:59 2020 +04 
isdst=0 gmtoff=14400
Europe/Volgograd  Sat Dec 26 22:00:00 2020 UT = Sun Dec 27 01:00:00 2020 +03 
isdst=0 gmtoff=10800
Europe/Volgograd  9223372036854689407 = NULL
Europe/Volgograd  9223372036854775807 = NULL
(xenial-amd64)root@impulse:~# diff <(zdump -v America/Phoenix | cut -d' ' -f2-) 
<(zdump -v SystemV/MST7 | cut -d' ' -f2-)


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

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

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

Title:
  new upstream release 2020f

Status in tzdata package in Ubuntu:
  In Progress
Status in tzdata source package in Xenial:
  Fix Committed
Status in tzdata source package in Bionic:
  Fix Committed
Status in tzdata source package in Focal:
  Fix Committed
Status in tzdata source package in Groovy:
  Fix Committed

Bug description:
  New upstream version, affecting the following timestamp:
    - Volgograd switches to Moscow time on 2020-12-27 at 02:00.

  The ICU timezone data has not yet been updated upstream so those
  changes will be included in a later SRU.

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

  $region/$timezone = Europe/Volgograd

  Additionally, an upstream update of tzdata removed the "old" SystemV
  timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS
  and earlier releases. Subsequently, these should be checked for using
  the following:

  diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v
  SystemV/MST7 | cut -d' ' -f2-)

  Nothing should be returned by the above command.

  [Original Description]
  https://www.iana.org/time-zones tzdata 2020f already exists, please update 
the package.

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

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


[Touch-packages] [Bug 1909698] Re: new upstream release 2020f

2021-01-06 Thread Brian Murray
There is also updated information in Focal for Volgograd.

(focal-amd64)root@impulse:~# zdump -v Europe/Volgograd | tail -n 6
Europe/Volgograd  Sat Oct 27 22:59:59 2018 UT = Sun Oct 28 01:59:59 2018 +03 
isdst=0 gmtoff=10800
Europe/Volgograd  Sat Oct 27 23:00:00 2018 UT = Sun Oct 28 03:00:00 2018 +04 
isdst=0 gmtoff=14400
Europe/Volgograd  Sat Dec 26 21:59:59 2020 UT = Sun Dec 27 01:59:59 2020 +04 
isdst=0 gmtoff=14400
Europe/Volgograd  Sat Dec 26 22:00:00 2020 UT = Sun Dec 27 01:00:00 2020 +03 
isdst=0 gmtoff=10800
Europe/Volgograd  9223372036854689407 = NULL
Europe/Volgograd  9223372036854775807 = NULL
(focal-amd64)root@impulse:~# apt-cache policy tzdata
tzdata:
  Installed: 2020f-0ubuntu0.20.04
  Candidate: 2020f-0ubuntu0.20.04
  Version table:
 *** 2020f-0ubuntu0.20.04 500
500 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages
100 /var/lib/dpkg/status
 2020d-0ubuntu0.20.04 500
500 http://192.168.10.7/ubuntu focal-updates/main amd64 Packages
500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages
 2019c-3ubuntu1 500
500 http://192.168.10.7/ubuntu focal/main amd64 Packages

And the SystemV timezones are still available.

focal-amd64)root@impulse:~# diff <(zdump -v America/Phoenix | cut -d' ' -f2-) 
<(zdump -v SystemV/MST7 | cut -d' ' -f2-)
nothing to see here

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

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

Title:
  new upstream release 2020f

Status in tzdata package in Ubuntu:
  In Progress
Status in tzdata source package in Xenial:
  Fix Committed
Status in tzdata source package in Bionic:
  Fix Committed
Status in tzdata source package in Focal:
  Fix Committed
Status in tzdata source package in Groovy:
  Fix Committed

Bug description:
  New upstream version, affecting the following timestamp:
    - Volgograd switches to Moscow time on 2020-12-27 at 02:00.

  The ICU timezone data has not yet been updated upstream so those
  changes will be included in a later SRU.

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

  $region/$timezone = Europe/Volgograd

  Additionally, an upstream update of tzdata removed the "old" SystemV
  timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS
  and earlier releases. Subsequently, these should be checked for using
  the following:

  diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v
  SystemV/MST7 | cut -d' ' -f2-)

  Nothing should be returned by the above command.

  [Original Description]
  https://www.iana.org/time-zones tzdata 2020f already exists, please update 
the package.

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

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


[Touch-packages] [Bug 1909698] Re: new upstream release 2020f

2021-01-06 Thread Brian Murray
Verified on bionic:

(bionic-amd64)root@impulse:~# apt-cache policy tzdata
tzdata:
  Installed: 2020f-0ubuntu0.18.04
  Candidate: 2020f-0ubuntu0.18.04
  Version table:
 *** 2020f-0ubuntu0.18.04 500
500 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 Packages
100 /var/lib/dpkg/status
 2020d-0ubuntu0.18.04 500
500 http://ubuntu.osuosl.org/ubuntu bionic-updates/main amd64 Packages
500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
 2018d-1 500
500 http://ubuntu.osuosl.org/ubuntu bionic/main amd64 Packages
(bionic-amd64)root@impulse:~# zdump -v Europe/Volgograd | tail -n 6
Europe/Volgograd  Sat Oct 27 22:59:59 2018 UT = Sun Oct 28 01:59:59 2018 +03 
isdst=0 gmtoff=10800
Europe/Volgograd  Sat Oct 27 23:00:00 2018 UT = Sun Oct 28 03:00:00 2018 +04 
isdst=0 gmtoff=14400
Europe/Volgograd  Sat Dec 26 21:59:59 2020 UT = Sun Dec 27 01:59:59 2020 +04 
isdst=0 gmtoff=14400
Europe/Volgograd  Sat Dec 26 22:00:00 2020 UT = Sun Dec 27 01:00:00 2020 +03 
isdst=0 gmtoff=10800
Europe/Volgograd  9223372036854689407 = NULL
Europe/Volgograd  9223372036854775807 = NULL

(bionic-amd64)root@impulse:~# diff <(zdump -v America/Phoenix | cut -d' ' -f2-) 
<(zdump -v SystemV/MST7 | cut -d' ' -f2-)
(bionic-amd64)root@impulse:~#

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

Title:
  new upstream release 2020f

Status in tzdata package in Ubuntu:
  In Progress
Status in tzdata source package in Xenial:
  Fix Committed
Status in tzdata source package in Bionic:
  Fix Committed
Status in tzdata source package in Focal:
  Fix Committed
Status in tzdata source package in Groovy:
  Fix Committed

Bug description:
  New upstream version, affecting the following timestamp:
    - Volgograd switches to Moscow time on 2020-12-27 at 02:00.

  The ICU timezone data has not yet been updated upstream so those
  changes will be included in a later SRU.

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

  $region/$timezone = Europe/Volgograd

  Additionally, an upstream update of tzdata removed the "old" SystemV
  timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS
  and earlier releases. Subsequently, these should be checked for using
  the following:

  diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v
  SystemV/MST7 | cut -d' ' -f2-)

  Nothing should be returned by the above command.

  [Original Description]
  https://www.iana.org/time-zones tzdata 2020f already exists, please update 
the package.

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

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


[Touch-packages] [Bug 1909698] Re: new upstream release 2020f

2021-01-06 Thread Brian Murray
We can see that there is updated information for Volgograd, so setting
to v-done for groovy.

(groovy-amd64)root@impulse:~# apt-cache policy tzdata
tzdata:
  Installed: 2020f-0ubuntu0.20.10
  Candidate: 2020f-0ubuntu0.20.10
  Version table:
 *** 2020f-0ubuntu0.20.10 500
500 http://archive.ubuntu.com/ubuntu groovy-proposed/main amd64 Packages
100 /var/lib/dpkg/status
 2020d-1ubuntu1 500
500 http://192.168.10.7/ubuntu groovy-updates/main amd64 Packages
500 http://192.168.10.7/ubuntu groovy-security/main amd64 Packages
 2020b-1ubuntu1 500
500 http://192.168.10.7/ubuntu groovy/main amd64 Packages
(groovy-amd64)root@impulse:~# zdump -v Europe/Volgograd | tail -n 6
Europe/Volgograd  Sat Oct 27 22:59:59 2018 UT = Sun Oct 28 01:59:59 2018 +03 
isdst=0 gmtoff=10800
Europe/Volgograd  Sat Oct 27 23:00:00 2018 UT = Sun Oct 28 03:00:00 2018 +04 
isdst=0 gmtoff=14400
Europe/Volgograd  Sat Dec 26 21:59:59 2020 UT = Sun Dec 27 01:59:59 2020 +04 
isdst=0 gmtoff=14400
Europe/Volgograd  Sat Dec 26 22:00:00 2020 UT = Sun Dec 27 01:00:00 2020 +03 
isdst=0 gmtoff=10800
Europe/Volgograd  9223372036854689407 = NULL
Europe/Volgograd  9223372036854775807 = NULL

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

Title:
  new upstream release 2020f

Status in tzdata package in Ubuntu:
  In Progress
Status in tzdata source package in Xenial:
  Fix Committed
Status in tzdata source package in Bionic:
  Fix Committed
Status in tzdata source package in Focal:
  Fix Committed
Status in tzdata source package in Groovy:
  Fix Committed

Bug description:
  New upstream version, affecting the following timestamp:
    - Volgograd switches to Moscow time on 2020-12-27 at 02:00.

  The ICU timezone data has not yet been updated upstream so those
  changes will be included in a later SRU.

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

  $region/$timezone = Europe/Volgograd

  Additionally, an upstream update of tzdata removed the "old" SystemV
  timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS
  and earlier releases. Subsequently, these should be checked for using
  the following:

  diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v
  SystemV/MST7 | cut -d' ' -f2-)

  Nothing should be returned by the above command.

  [Original Description]
  https://www.iana.org/time-zones tzdata 2020f already exists, please update 
the package.

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

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


[Touch-packages] [Bug 1909698] Re: new upstream release 2020f

2021-01-06 Thread Brian Murray
** Changed in: tzdata (Ubuntu Xenial)
 Assignee: (unassigned) => Brian Murray (brian-murray)

** Changed in: tzdata (Ubuntu Bionic)
 Assignee: (unassigned) => Brian Murray (brian-murray)

** Changed in: tzdata (Ubuntu Focal)
 Assignee: (unassigned) => Brian Murray (brian-murray)

** Changed in: tzdata (Ubuntu Groovy)
 Assignee: (unassigned) => Brian Murray (brian-murray)

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

Title:
  new upstream release 2020f

Status in tzdata package in Ubuntu:
  In Progress
Status in tzdata source package in Xenial:
  New
Status in tzdata source package in Bionic:
  New
Status in tzdata source package in Focal:
  New
Status in tzdata source package in Groovy:
  New

Bug description:
  New upstream version, affecting the following timestamp:
    - Volgograd switches to Moscow time on 2020-12-27 at 02:00.

  The ICU timezone data has not yet been updated upstream so those
  changes will be included in a later SRU.

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

  $region/$timezone = Europe/Volgograd

  Additionally, an upstream update of tzdata removed the "old" SystemV
  timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS
  and earlier releases. Subsequently, these should be checked for using
  the following:

  diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v
  SystemV/MST7 | cut -d' ' -f2-)

  Nothing should be returned by the above command.

  [Original Description]
  https://www.iana.org/time-zones tzdata 2020f already exists, please update 
the package.

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

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


[Touch-packages] [Bug 1909698] Re: new upstream release 2020f

2021-01-06 Thread Brian Murray
Here's a debdiff for Precise.

** Patch added: "precise.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1909698/+attachment/5449825/+files/precise.debdiff

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

Title:
  new upstream release 2020f

Status in tzdata package in Ubuntu:
  In Progress
Status in tzdata source package in Xenial:
  New
Status in tzdata source package in Bionic:
  New
Status in tzdata source package in Focal:
  New
Status in tzdata source package in Groovy:
  New

Bug description:
  New upstream version, affecting the following timestamp:
    - Volgograd switches to Moscow time on 2020-12-27 at 02:00.

  The ICU timezone data has not yet been updated upstream so those
  changes will be included in a later SRU.

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

  $region/$timezone = Europe/Volgograd

  Additionally, an upstream update of tzdata removed the "old" SystemV
  timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS
  and earlier releases. Subsequently, these should be checked for using
  the following:

  diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v
  SystemV/MST7 | cut -d' ' -f2-)

  Nothing should be returned by the above command.

  [Original Description]
  https://www.iana.org/time-zones tzdata 2020f already exists, please update 
the package.

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

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


[Touch-packages] [Bug 1909698] Re: new upstream release 2020f

2021-01-06 Thread Brian Murray
And here's a trusty debdiff with a bug reference.

** Patch added: "trusty.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1909698/+attachment/5449803/+files/trusty.debdiff

** Patch removed: "trusty.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1909698/+attachment/5449801/+files/trusty.debdiff

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

Title:
  new upstream release 2020f

Status in tzdata package in Ubuntu:
  In Progress
Status in tzdata source package in Xenial:
  New
Status in tzdata source package in Bionic:
  New
Status in tzdata source package in Focal:
  New
Status in tzdata source package in Groovy:
  New

Bug description:
  New upstream version, affecting the following timestamp:
    - Volgograd switches to Moscow time on 2020-12-27 at 02:00.

  The ICU timezone data has not yet been updated upstream so those
  changes will be included in a later SRU.

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

  $region/$timezone = Europe/Volgograd

  Additionally, an upstream update of tzdata removed the "old" SystemV
  timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS
  and earlier releases. Subsequently, these should be checked for using
  the following:

  diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v
  SystemV/MST7 | cut -d' ' -f2-)

  Nothing should be returned by the above command.

  [Original Description]
  https://www.iana.org/time-zones tzdata 2020f already exists, please update 
the package.

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

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


[Touch-packages] [Bug 1909698] Re: new upstream release 2020f

2021-01-06 Thread Brian Murray
Attached is a debdiff for Trusty.

** Patch added: "trusty.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1909698/+attachment/5449801/+files/trusty.debdiff

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

Title:
  new upstream release 2020f

Status in tzdata package in Ubuntu:
  In Progress
Status in tzdata source package in Xenial:
  New
Status in tzdata source package in Bionic:
  New
Status in tzdata source package in Focal:
  New
Status in tzdata source package in Groovy:
  New

Bug description:
  New upstream version, affecting the following timestamp:
    - Volgograd switches to Moscow time on 2020-12-27 at 02:00.

  The ICU timezone data has not yet been updated upstream so those
  changes will be included in a later SRU.

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

  $region/$timezone = Europe/Volgograd

  Additionally, an upstream update of tzdata removed the "old" SystemV
  timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS
  and earlier releases. Subsequently, these should be checked for using
  the following:

  diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v
  SystemV/MST7 | cut -d' ' -f2-)

  Nothing should be returned by the above command.

  [Original Description]
  https://www.iana.org/time-zones tzdata 2020f already exists, please update 
the package.

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

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


[Touch-packages] [Bug 1909698] Re: new upstream release 2020f

2021-01-05 Thread Brian Murray
** Description changed:

- New upstream version, affecting the following future timestamp:
-   - Volgograd switches to Moscow time on 2020-12-27 at 02:00.
+ New upstream version, affecting the following timestamp:
+   - Volgograd switches to Moscow time on 2020-12-27 at 02:00.
  
  The ICU timezone data has not yet been updated upstream so those changes
  will be included in a later SRU.
  
  Verification is done with 'zdump'. The first timezone that gets changed
  in the updated package is dumped with "zdump -v
  $region/$timezone_that_changed" (this needed to be greped for in
  /usr/share/zoneinfo/). [For example: "zdump -v Africa/Casablanca".] This
  is compared to the same output after the updated package got installed.
  If those are different the verification is considered done.
  
  $region/$timezone = Europe/Volgograd
  
- Additionally, previous SRU removed the "old" SystemV timezones, so we
- should ensure that they are kept. Subsequently, these should be checked
- for using the following:
+ Additionally, an upstream update of tzdata removed the "old" SystemV
+ timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS
+ and earlier releases. Subsequently, these should be checked for using
+ the following:
  
- zdump -v SystemV/MST7
- zdump -v America/Phoenix
+ diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v
+ SystemV/MST7 | cut -d' ' -f2-)
  
- The information returned by SystemV/MST7 should be included in
- America/Phoenix's output.
+ Nothing should be returned by the above command.
  
  [Original Description]
  https://www.iana.org/time-zones tzdata 2020f already exists, please update 
the package.

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

Title:
  new upstream release 2020f

Status in tzdata package in Ubuntu:
  In Progress
Status in tzdata source package in Xenial:
  New
Status in tzdata source package in Bionic:
  New
Status in tzdata source package in Focal:
  New
Status in tzdata source package in Groovy:
  New

Bug description:
  New upstream version, affecting the following timestamp:
    - Volgograd switches to Moscow time on 2020-12-27 at 02:00.

  The ICU timezone data has not yet been updated upstream so those
  changes will be included in a later SRU.

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

  $region/$timezone = Europe/Volgograd

  Additionally, an upstream update of tzdata removed the "old" SystemV
  timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS
  and earlier releases. Subsequently, these should be checked for using
  the following:

  diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v
  SystemV/MST7 | cut -d' ' -f2-)

  Nothing should be returned by the above command.

  [Original Description]
  https://www.iana.org/time-zones tzdata 2020f already exists, please update 
the package.

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

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


[Touch-packages] [Bug 1909698] Re: new upstream release 2020f

2021-01-05 Thread Brian Murray
** Description changed:

- https://www.iana.org/time-zones tzdata 2020f already exists, please
- update the package.
+ New upstream version, affecting the following future timestamp:
+   - Volgograd switches to Moscow time on 2020-12-27 at 02:00.
+ 
+ The ICU timezone data has not yet been updated upstream so those changes
+ will be included in a later SRU.
+ 
+ Verification is done with 'zdump'. The first timezone that gets changed
+ in the updated package is dumped with "zdump -v
+ $region/$timezone_that_changed" (this needed to be greped for in
+ /usr/share/zoneinfo/). [For example: "zdump -v Africa/Casablanca".] This
+ is compared to the same output after the updated package got installed.
+ If those are different the verification is considered done.
+ 
+ $region/$timezone = Europe/Volgograd
+ 
+ Additionally, previous SRU removed the "old" SystemV timezones, so we
+ should ensure that they are kept. Subsequently, these should be checked
+ for using the following:
+ 
+ zdump -v SystemV/MST7
+ zdump -v America/Phoenix
+ 
+ The information returned by SystemV/MST7 should be included in
+ America/Phoenix's output.
+ 
+ [Original Description]
+ https://www.iana.org/time-zones tzdata 2020f already exists, please update 
the package.

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

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

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

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

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

Title:
  new upstream release 2020f

Status in tzdata package in Ubuntu:
  In Progress
Status in tzdata source package in Xenial:
  New
Status in tzdata source package in Bionic:
  New
Status in tzdata source package in Focal:
  New
Status in tzdata source package in Groovy:
  New

Bug description:
  New upstream version, affecting the following future timestamp:
- Volgograd switches to Moscow time on 2020-12-27 at 02:00.

  The ICU timezone data has not yet been updated upstream so those
  changes will be included in a later SRU.

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

  $region/$timezone = Europe/Volgograd

  Additionally, previous SRU removed the "old" SystemV timezones, so we
  should ensure that they are kept. Subsequently, these should be
  checked for using the following:

  zdump -v SystemV/MST7
  zdump -v America/Phoenix

  The information returned by SystemV/MST7 should be included in
  America/Phoenix's output.

  [Original Description]
  https://www.iana.org/time-zones tzdata 2020f already exists, please update 
the package.

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

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


[Touch-packages] [Bug 1909698] Re: new upstream release 2020f

2021-01-05 Thread Brian Murray
** Summary changed:

- outdated tzdata in all releases
+ new upstream release 2020f

** Changed in: tzdata (Ubuntu)
 Assignee: (unassigned) => Brian Murray (brian-murray)

** Changed in: tzdata (Ubuntu)
   Status: New => In Progress

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

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

Title:
  new upstream release 2020f

Status in tzdata package in Ubuntu:
  In Progress

Bug description:
  https://www.iana.org/time-zones tzdata 2020f already exists, please
  update the package.

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

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


[Touch-packages] [Bug 1899857] Update Released

2021-01-04 Thread Brian Murray
The verification of the Stable Release Update for alsa-lib has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  [SRU] alsa-lib: support the enum value settings both in "" and in ''

Status in HWE Next:
  New
Status in alsa-lib package in Ubuntu:
  Fix Released
Status in alsa-lib source package in Focal:
  Fix Released
Status in alsa-lib source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  Recently the ucm added some amixer settings, like this one:
  cset "name='rt711 ADC 23 Mux' 'MIC2'"
  This setting is needed for Dell soundwire audio machines, and only
  this setting is set correctly, the headset-mic could work. And we
  already backported this ucm to focal. But the alsa-lib ctl parse
  doesn't support the enum value in the '' yet, so this amixer setting
  can't be set correctly under current focal and groovy, we need to
  backport a patch from alsa-lib master branch.

  [Fix]
  Backport a patch from upstream, this patch is not in the groovy
  yet (not in the alsa-lib v1.2.3.2), so both groovy and focal need this
  patch.

  [Test Case]
  On the Dell soundwire audio machine, run alsactl init, then check if
  the amixer "rt711 ADC 23 Mux" is set to "MIC2" or not, if it is set
  correctly, it means the alsalib enum ctl parse support both "" and ''
  now.

  
  [Regression Risk]
  This could introduce failure on setting enum amixer settings, users
  will experience the failure of audio device like the speaker can't output
  sound, the mic can't record sound. But this possibility is very low since
  we have tested this SRU on many LENOVO and Dell machines (with and without
  soundwire audio), all worked as fine as before.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1899857/+subscriptions

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


[Touch-packages] [Bug 1902244] Update Released

2021-01-04 Thread Brian Murray
The verification of the Stable Release Update for libclc has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Backport packages for 20.04.2 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in libglvnd package in Ubuntu:
  Invalid
Status in llvm-toolchain-11 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid
Status in libclc source package in Focal:
  Fix Released
Status in libdrm source package in Focal:
  Fix Committed
Status in libglvnd source package in Focal:
  Fix Committed
Status in llvm-toolchain-11 source package in Focal:
  Fix Committed
Status in mesa source package in Focal:
  Fix Committed
Status in xorg-server source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  These are needed for 20.04.2 images.

  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  [Regression potential]

  libdrm: very minimal chance for regressions

  llvm-11: a new package, no regression potential on it's own

  libclc: just a rebuild against the new llvm

  libglvnd: mostly just EGL headers sync from Khronos, needed by mesa

  mesa: a new major release, but we'll pull the final stable release of
  20.2.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new point-release

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

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


[Touch-packages] [Bug 1909698] Re: outdated tzdata in all releases

2020-12-30 Thread Brian Murray
** Summary changed:

- outdated tzdata  in 18.04
+ outdated tzdata in all releases

** Tags added: fr-1021

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

Title:
  outdated tzdata in all releases

Status in tzdata package in Ubuntu:
  New

Bug description:
  https://www.iana.org/time-zones tzdata 2020f already exists, please
  update the package.

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

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


[Touch-packages] [Bug 1899262] Update Released

2020-12-15 Thread Brian Murray
The verification of the Stable Release Update for wpa has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Broken dbus GetAll message to wpa supplicant interface properties

Status in wpa package in Ubuntu:
  Fix Released
Status in wpa source package in Bionic:
  Fix Released

Bug description:
  * Impact
  One of the distro patch is incorrect and create issues when trying to query 
dbus properties

  * Test Case

  $ sudo dbus-send --system --print-reply --dest=fi.w1.wpa_supplicant1
  /fi/w1/wpa_supplicant1/Interfaces/1
  org.freedesktop.DBus.Properties.GetAll
  string:fi.w1.wpa_supplicant1.Interface

  shouldn't error out

  (the /1 reflect the interface number and could be a different value,
  check with d-feet if needed)

  * Regression potential

  The fixes is in the dbus interface, check that communication with
  desktop clients (indicator, applet, settings) still works correctly,
  returning expected informations on the signal, etc

  -

  dbus-send is able to read the properties of interface using GetAll. Those 
information include interface name, status, encryption method, etc.
  The regression was introduced when someone try to have the Station attribute 
supported

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

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


[Touch-packages] [Bug 1899100] Re: whoopsie assert failure: double free or corruption (fasttop)

2020-12-14 Thread Brian Murray
Looking at the Error Tracker crash buckets linked to from the bug
description the version of the package from focal-proposed and bionic-
proposed does not appear. Additionally, I was unable to find any similar
looking crashes in the Error Tracker so there are no new "double free"
buckets with the version of the package from -proposed. Subsequently,
I'm setting the tags to verification-done.

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

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

Title:
  whoopsie assert failure: double free or corruption (fasttop)

Status in whoopsie package in Ubuntu:
  Fix Released
Status in whoopsie source package in Bionic:
  Fix Committed
Status in whoopsie source package in Focal:
  Fix Committed
Status in whoopsie source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  whoopsie is crashing somewhat regularly. There are a couple of crashes in the 
Error Tracker which look similar:

  https://errors.ubuntu.com/problem/5c1f68854a0f3bd5e263f1cd35e4dd944c9e90bd
  https://errors.ubuntu.com/problem/5d7e641dc46229c08389420fdd74a7473d2dec98

  As of yet (2020-11-22) neither crash is happening with whoopsie
  version 0.2.73.

  [Test Case]
  We don't have a manual test case for this crash report but given the number 
of crashes in the Error Tracker and the number of users of whoopsie the absence 
of the same crash occurring with the new version of whoopsie should be enough 
to consider this verified.

  [Regression Potential]
  Whoopsie will no longer upload crash reports with duplicate keys but this was 
not something it should have been doing in the first place. That being said we 
should also test whoopsie with a sample of crashes (apport-test-crashes) and 
ensure they are received by the staging version of the Ubuntu Error Tracker.

  Original Description
  
  Apport popped up saying whoopsie had crashed (I assume during a previous 
crash report upload?)

  ProblemType: CrashDistroRelease: Ubuntu 20.10
  Package: whoopsie 0.2.72
  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-0ubuntu49
  Architecture: amd64
  AssertionMessage: double free or corruption (fasttop)
  CasperMD5CheckResult: skip
  CrashCounter: 1
  Date: Fri Oct  9 08:08:56 2020
  ExecutablePath: /usr/bin/whoopsie
  InstallationDate: Installed on 2019-11-18 (325 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcCmdline: /usr/bin/whoopsie -f
  ProcEnviron:
   LANG=en_AU.UTF-8
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
  RelatedPackageVersions: apport-noui N/ASignal: 6SourcePackage: whoopsie
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f5982159128 
"%s\n") at ../sysdeps/posix/libc_fatal.c:155
   malloc_printerr (str=str@entry=0x7f598215b5d8 "double free or corruption 
(fasttop)") at malloc.c:5389
   _int_free (av=0x7f598218bba0 , p=0x55964a2bf3e0, have_lock=0) at 
malloc.c:4298
   () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_hash_table_remove_all () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: whoopsie assert failure: double free or corruption (fasttop)
  UpgradeStatus: Upgraded to groovy on 2020-10-06 (2 days ago)
  UserGroups: N/A
  separator:

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

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


[Touch-packages] [Bug 1907956] Re: ubiquity crash on whoopsie removal, Xubuntu 21.04 minimal install

2020-12-14 Thread Brian Murray
** Tags added: rls-hh-incoming

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

Title:
  ubiquity crash on whoopsie removal, Xubuntu 21.04 minimal install

Status in ubiquity package in Ubuntu:
  New
Status in whoopsie package in Ubuntu:
  New

Bug description:
  Xubuntu hirsute 20201213 minimal install crashed on whoopsie removal
  but finished installing. This is 1907951 with hopefully more crash
  information.

  Related logs identified:
  Dec 13 12:37:05 xubuntu ubiquity: Purging configuration files for whoopsie 
(0.2.73) ...
  Dec 13 12:37:05 xubuntu ubiquity: #015
  Dec 13 12:37:05 xubuntu ubiquity: Running in chroot, ignoring command 
'daemon-reload'#015
  Dec 13 12:37:05 xubuntu ubiquity: message repeated 2 times: [ Running in 
chroot, ignoring command 'daemon-reload'#015]
  Dec 13 12:37:05 xubuntu ubiquity: rm:
  Dec 13 12:37:05 xubuntu ubiquity: cannot remove 
'/var/lib/whoopsie/whoopsie-id'
  Dec 13 12:37:05 xubuntu ubiquity: : No such file or directory
  Dec 13 12:37:05 xubuntu ubiquity: #015
  Dec 13 12:37:05 xubuntu ubiquity: dpkg: error processing package whoopsie 
(--purge):
  Dec 13 12:37:05 xubuntu ubiquity: #015
  Dec 13 12:37:05 xubuntu ubiquity:  installed whoopsie package post-removal 
script subprocess returned error exit status 1
  Dec 13 12:37:05 xubuntu ubiquity: #015

  Looks like it's a bug in the postrm script:
  #! /bin/sh

  set -e

  #DEBHELPER#

  if [ "$1" = "purge" ]; then
  deluser --quiet --system whoopsie > /dev/null || true
  chmod g-s /var/crash >/dev/null 2>&1
  chgrp root /var/crash >/dev/null 2>&1
  rm /var/lib/whoopsie/whoopsie-id >/dev/null
  fi

  exit 0

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: ubiquity 21.04.3
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu55
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.456
  Date: Sun Dec 13 07:40:33 2020
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/xubuntu.seed 
maybe-ubiquity quiet splash ---
  LiveMediaBuild: Xubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201213)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
  RebootRequiredPkgs:
   linux-image-5.8.0-25-generic
   linux-base
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1833174] Re: Shadowing the vim-window results in vim-gtk3 crash

2020-12-09 Thread Brian Murray
** Changed in: vim (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 vim in Ubuntu.
https://bugs.launchpad.net/bugs/1833174

Title:
   Shadowing the vim-window results in vim-gtk3 crash

Status in vim:
  Unknown
Status in vim package in Ubuntu:
  Fix Released
Status in vim source package in Focal:
  Triaged
Status in vim source package in Groovy:
  Triaged

Bug description:
  With XFCE when I try to "shadow" the vim-gtk3 window (just to show only the 
title bar) it results in a vim crash and the window just disappears without any 
core dump neither .swp files on.
  The only message I get on the terminal is

  BadMatch (invalid parameter attributes)
  Vim: Got X error
  Vim: Finished.

  This behaviour started from Xubuntu 18.04.
  The vim-gtk package is not suffering from this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: vim-gtk3 2:8.1.0320-1ubuntu3.1
  ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
  Uname: Linux 5.0.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Jun 18 09:10:38 2019
  InstallationDate: Installed on 2019-04-23 (55 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: vim
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1906078] Re: Whoopsie sends bug reports automatically without consent

2020-12-09 Thread Brian Murray
I suspect what happened is the bug documented in bug 1906877, if the
control panel is set to automatic and then back to never the file which
enables automatic reporting is not removed. We are working to resolve
this bug in all affected releases of Ubuntu. Thanks for reporting this
issue and getting us to look into it.

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

Title:
  Whoopsie sends bug reports automatically without consent

Status in whoopsie package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  So, I just realized about an hour ago that whoopsie has been sending
  bug reports without my consent since May (2020-05-11 to be exact) from
  checking journalctl where I can see lines like these:

  Uploading /var/crash/[...]
  Sent; server replied with: No error
  Response code: 200
  Reported OOPS ID [...]

  I checked the "Diagnostics" GUI in the gnome-control-center and it
  does have "Send error reports to Canonical" set to "Never"... I tried
  switching it to "Manual" and back to "Never" and that did have an
  effect in /etc/, namelely when going from "Never" to "Manual":

    renamed:rc2.d/K01whoopsie -> rc2.d/S01whoopsie
    renamed:rc3.d/K01whoopsie -> rc3.d/S01whoopsie
    renamed:rc4.d/K01whoopsie -> rc4.d/S01whoopsie
    renamed:rc5.d/K01whoopsie -> rc5.d/S01whoopsie
    new file:   systemd/system/multi-user.target.wants/whoopsie.service

  and the opposite effect is achieved when switching back to "Never". So
  far so good, I guess...

  My /etc/ does have a "whoopsie" file (/etc/whoopsie) which doesn't
  seem to be present in clean installations of Ubuntu and which has the
  following contents:

  [General]
  report_metrics=true

  Switching from "true" to "false" does seem to disable whoopsie, so
  that's nice I guess... but what is this file doing here in the first
  place? To clarify, this was originally an Ubuntu 18.04 system which I
  recently upgraded to 20.04 but the unsolicited error report uploads
  have been going on since well before the upgrade so that's not the
  issue.

  I don't remember touching anything on my system relating to apport or
  whoopsie and my shell history doesn't contain anything about whoopsie
  or apport so this situation seems to have occurred on its own (perhaps
  after an update?).

  This is a pretty serious breach of privacy (and of the GDPR) and
  others might also be unknowingly affected like I was, so the team in
  charge of this might want to push an update that for instance resets
  the /etc/whoopsie file if present (if that truly is the problem).

  While I'm at it I would like all the error reports sent from my
  computer to be deleted. Where can I ask for that? I haven't seen an
  option for that anywhere, apart from contacting
  dataprotect...@canonical.com.

  Best regards.

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

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


[Touch-packages] [Bug 1906565] Re: traceback when running apport as non-root user

2020-12-04 Thread Brian Murray
I installed the version of apport from xenial-proposed and no longer
received a Traceback when running the test case.

Preparing to unpack .../python3-apport_2.20.1-0ubuntu2.28_all.deb ...
Unpacking python3-apport (2.20.1-0ubuntu2.28) over (2.20.1-0ubuntu2.27) ...
Preparing to unpack .../apport_2.20.1-0ubuntu2.28_all.deb ...
Unpacking apport (2.20.1-0ubuntu2.28) over (2.20.1-0ubuntu2.27) ...
Processing triggers for man-db (2.7.5-1) ...
Processing triggers for hicolor-icon-theme (0.15-0ubuntu1.1) ...
Processing triggers for systemd (229-4ubuntu21.29) ...
Processing triggers for ureadahead (0.100.0-19.1) ...
Setting up python3-apport (2.20.1-0ubuntu2.28) ...
Setting up apport (2.20.1-0ubuntu2.28) ...
bdmurray@clean-xenial-amd64:~$ python3 generate-sigsegv-crash.py cat
GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.5) 7.11.1
Copyright (C) 2016 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 "x86_64-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 cat...(no debugging symbols found)...done.
(gdb) Starting program: /bin/cat 

Program received signal SIGSEGV, Segmentation fault.
0x77b04320 in __read_nocancel () at 
../sysdeps/unix/syscall-template.S:84
84  ../sysdeps/unix/syscall-template.S: No such file or directory.
(gdb) Saved corefile /tmp/tmplo7od5en/my.core
(gdb) ERROR: apport (pid 2923) Fri Dec  4 15:48:31 2020: called for pid 2915, 
signal 11, core limit 0, dump mode 1
ERROR: apport (pid 2923) Fri Dec  4 15:48:31 2020: executable: /bin/cat 
(command line "/bin/cat")
ERROR: apport (pid 2923) Fri Dec  4 15:48:31 2020: is_closing_session(): no 
DBUS_SESSION_BUS_ADDRESS in environment
ERROR: apport (pid 2923) Fri Dec  4 15:48:31 2020: wrote report 
/tmp/tmplo7od5en/_bin_cat.1000.crash
(gdb) Kill the program being debugged? (y or n) [answered Y; input not from 
terminal]
(gdb) --- post-processing /tmp/tmplo7od5en/_bin_cat.1000.crash


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

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

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

Title:
  traceback when running apport as non-root user

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Xenial:
  Fix Committed
Status in apport source package in Bionic:
  Fix Committed
Status in apport source package in Focal:
  Fix Committed
Status in apport source package in Groovy:
  Fix Committed

Bug description:
  [Impact]
  The apport-test-crashes package, which is used to test the Error Tracker 
deployments, fails produce crash files for binary applications since "various 
security hardening fixes" were included in apport. The problematic change is 
the dropping of supplemental groups in data/apport. This results in a 
PermissionError as it is not the root user who is calling 
/usr/share/apport/apport.

  [Test Case]
  The least convulted test case involves using the generate-sigsegv-crash.py 
script from apport-test-crashes. This ends up using a command similar to 
'/usr/share/apport/apport -p 4077 -s 11 -E /usr/bin/gnome-calculator < 
/tmp/20.10-gnome-calculator.core' which then will encounter the Traceback.

  1) Comment out "check_lock()" in /usr/share/apport/apport (This is necessary 
as we are not running as root)
  2) Put a copy of generate-sigsegv-crash.py on disk.
  3) Run 'python3 /tmp/generate-sigsegv-crash.py cat'
  4) Observe the following Traceback:

  Traceback (most recent call last):
    File "/tmp/tmpvkt5d266/apport", line 599, in 
  drop_privileges(True)
    File "/tmp/tmpvkt5d266/apport", line 125, in drop_privileges
  os.setgroups([])
  PermissionError: [Errno 1] Operation not permitted

  With the version of apport from -proposed you'll receive no such
  Traceback.

  [Regression Potential]
  If there is an error in the python code we code see a new traceback for any 
and all crashes being generated, so ensure regular crash generation works too.

  apport-test-crashes code is here:
  
https://code.launchpad.net/~daisy-pluckers/error-tracker-deployment/test-crashes/

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

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

[Touch-packages] [Bug 1906565] Re: traceback when running apport as non-root user

2020-12-04 Thread Brian Murray
I installed the version of apport from bionic-proposed and no longer
received a Traceback when following the test case.

Setting up python3-apport (2.20.9-0ubuntu7.21) ...
Setting up apport (2.20.9-0ubuntu7.21) ...
apport-autoreport.service is a disabled or a static unit, not starting it.
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for ureadahead (0.100.0-21) ...
Processing triggers for systemd (237-3ubuntu10.43) ...
Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
bdmurray@clean-bionic-amd64:~$ python3 generate-sigsegv-crash.py cat
GNU gdb (Ubuntu 8.1.1-0ubuntu1) 8.1.1
Copyright (C) 2018 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 "x86_64-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 cat...(no debugging symbols found)...done.
(gdb) Starting program: /bin/cat 

Program received signal SIGSEGV, Segmentation fault.
0x77af2151 in __GI___libc_read (fd=0, buf=0x77fc2000, 
nbytes=131072) at ../sysdeps/unix/sysv/linux/read.c:27
27  ../sysdeps/unix/sysv/linux/read.c: No such file or directory.
(gdb) warning: Memory read failed for corefile section, 4096 bytes at 
0xff60.
Saved corefile /tmp/tmp1o0onv61/my.core
(gdb) ERROR: apport (pid 2623) Fri Dec  4 15:42:10 2020: called for pid 2615, 
signal 11, core limit 0, dump mode 1
ERROR: apport (pid 2623) Fri Dec  4 15:42:10 2020: executable: /bin/cat 
(command line "/bin/cat")
ERROR: apport (pid 2623) Fri Dec  4 15:42:10 2020: gdbus call error: Error: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name o
rg.gnome.SessionManager was not provided by any .service files

ERROR: apport (pid 2623) Fri Dec  4 15:42:10 2020: debug: session gdbus call: 
ERROR: apport (pid 2623) Fri Dec  4 15:42:11 2020: wrote report 
/tmp/tmp1o0onv61/_bin_cat.1000.crash
(gdb) Kill the program being debugged? (y or n) [answered Y; input not from 
terminal]
(gdb) --- post-processing /tmp/tmp1o0onv61/_bin_cat.1000.crash


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

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

Title:
  traceback when running apport as non-root user

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Xenial:
  Fix Committed
Status in apport source package in Bionic:
  Fix Committed
Status in apport source package in Focal:
  Fix Committed
Status in apport source package in Groovy:
  Fix Committed

Bug description:
  [Impact]
  The apport-test-crashes package, which is used to test the Error Tracker 
deployments, fails produce crash files for binary applications since "various 
security hardening fixes" were included in apport. The problematic change is 
the dropping of supplemental groups in data/apport. This results in a 
PermissionError as it is not the root user who is calling 
/usr/share/apport/apport.

  [Test Case]
  The least convulted test case involves using the generate-sigsegv-crash.py 
script from apport-test-crashes. This ends up using a command similar to 
'/usr/share/apport/apport -p 4077 -s 11 -E /usr/bin/gnome-calculator < 
/tmp/20.10-gnome-calculator.core' which then will encounter the Traceback.

  1) Comment out "check_lock()" in /usr/share/apport/apport (This is necessary 
as we are not running as root)
  2) Put a copy of generate-sigsegv-crash.py on disk.
  3) Run 'python3 /tmp/generate-sigsegv-crash.py cat'
  4) Observe the following Traceback:

  Traceback (most recent call last):
    File "/tmp/tmpvkt5d266/apport", line 599, in 
  drop_privileges(True)
    File "/tmp/tmpvkt5d266/apport", line 125, in drop_privileges
  os.setgroups([])
  PermissionError: [Errno 1] Operation not permitted

  With the version of apport from -proposed you'll receive no such
  Traceback.

  [Regression Potential]
  If there is an error in the python code we code see a new traceback for any 
and all crashes being generated, so ensure regular crash generation works too.

  apport-test-crashes code is here:
  
https://code.launchpad.net/~daisy-pluckers/error-tracker-deployment/test-crashes/

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

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

[Touch-packages] [Bug 1906565] Re: traceback when running apport as non-root user

2020-12-04 Thread Brian Murray
I installed the version of apport from focal-proposed and no longer
received a Traceback when running the traceback.

Unpacking apport (2.20.11-0ubuntu27.14) over (2.20.11-0ubuntu27.12) ...
Setting up python3-apport (2.20.11-0ubuntu27.14) ...
Setting up apport (2.20.11-0ubuntu27.14) ...
apport-autoreport.service is a disabled or a static unit, not starting it.
Processing triggers for systemd (245.4-4ubuntu3.3) ...
Processing triggers for man-db (2.9.1-1) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
bdmurray@clean-focal-amd64:~$ python3 generate-sigsegv-crash.py cat
GNU gdb (Ubuntu 9.2-0ubuntu1~20.04) 9.2
Copyright (C) 2020 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 "x86_64-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 cat...
(No debugging symbols found in cat)
(gdb) Starting program: /usr/bin/cat 

Program received signal SIGSEGV, Segmentation fault.
0x77ed7142 in __GI___libc_read (fd=0, buf=0x77835000, 
nbytes=131072) at ../sysdeps/unix/sysv/linux/read.c:26
26  ../sysdeps/unix/sysv/linux/read.c: No such file or directory.
(gdb) warning: Memory read failed for corefile section, 4096 bytes at 
0xff60.
Saved corefile /tmp/tmp3m7fnzeq/my.core
(gdb) ERROR: apport (pid 3180) Fri Dec  4 15:33:28 2020: called for pid 3172, 
signal 11, core limit 0, dump mode 1
ERROR: apport (pid 3180) Fri Dec  4 15:33:28 2020: executable: /usr/bin/cat 
(command line "/usr/bin/cat")
ERROR: apport (pid 3180) Fri Dec  4 15:33:28 2020: gdbus call error: Error: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name o
rg.gnome.SessionManager was not provided by any .service files

ERROR: apport (pid 3180) Fri Dec  4 15:33:28 2020: debug: session gdbus call: 
ERROR: apport (pid 3180) Fri Dec  4 15:33:28 2020: wrote report 
/tmp/tmp3m7fnzeq/_usr_bin_cat.1000.crash
(gdb) Kill the program being debugged? (y or n) [answered Y; input not from 
terminal]
[Inferior 1 (process 3172) killed]
(gdb) --- post-processing /tmp/tmp3m7fnzeq/_usr_bin_cat.1000.crash


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

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

Title:
  traceback when running apport as non-root user

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Xenial:
  Fix Committed
Status in apport source package in Bionic:
  Fix Committed
Status in apport source package in Focal:
  Fix Committed
Status in apport source package in Groovy:
  Fix Committed

Bug description:
  [Impact]
  The apport-test-crashes package, which is used to test the Error Tracker 
deployments, fails produce crash files for binary applications since "various 
security hardening fixes" were included in apport. The problematic change is 
the dropping of supplemental groups in data/apport. This results in a 
PermissionError as it is not the root user who is calling 
/usr/share/apport/apport.

  [Test Case]
  The least convulted test case involves using the generate-sigsegv-crash.py 
script from apport-test-crashes. This ends up using a command similar to 
'/usr/share/apport/apport -p 4077 -s 11 -E /usr/bin/gnome-calculator < 
/tmp/20.10-gnome-calculator.core' which then will encounter the Traceback.

  1) Comment out "check_lock()" in /usr/share/apport/apport (This is necessary 
as we are not running as root)
  2) Put a copy of generate-sigsegv-crash.py on disk.
  3) Run 'python3 /tmp/generate-sigsegv-crash.py cat'
  4) Observe the following Traceback:

  Traceback (most recent call last):
    File "/tmp/tmpvkt5d266/apport", line 599, in 
  drop_privileges(True)
    File "/tmp/tmpvkt5d266/apport", line 125, in drop_privileges
  os.setgroups([])
  PermissionError: [Errno 1] Operation not permitted

  With the version of apport from -proposed you'll receive no such
  Traceback.

  [Regression Potential]
  If there is an error in the python code we code see a new traceback for any 
and all crashes being generated, so ensure regular crash generation works too.

  apport-test-crashes code is here:
  
https://code.launchpad.net/~daisy-pluckers/error-tracker-deployment/test-crashes/

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

-- 
Mailing list: 

[Touch-packages] [Bug 1906565] Re: traceback when running apport as non-root user

2020-12-04 Thread Brian Murray
I installed the version of apport from groovy-proposed and there is no
longer a Traceback when running the test case.

Setting up python3-apport (2.20.11-0ubuntu50.3) ...
Setting up apport (2.20.11-0ubuntu50.3) ...
apport-autoreport.service is a disabled or a static unit, not starting it.
Processing triggers for systemd (246.6-1ubuntu1) ...
Processing triggers for man-db (2.9.3-2) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
bdmurray@clean-groovy-amd64:~$ python3 generate-sigsegv-crash.py cat
GNU gdb (Ubuntu 9.2-0ubuntu2) 9.2
Copyright (C) 2020 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 "x86_64-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 cat...
(No debugging symbols found in cat)
(gdb) Starting program: /usr/bin/cat 

Program received signal SIGSEGV, Segmentation fault.
0x77ed3cb2 in __GI___libc_read (fd=0, buf=0x77837000, 
nbytes=131072) at ../sysdeps/unix/sysv/linux/read.c:26
26  ../sysdeps/unix/sysv/linux/read.c: No such file or directory.
(gdb) warning: Memory read failed for corefile section, 4096 bytes at 
0xff60.
Saved corefile /tmp/tmpehzet8ma/my.core
(gdb) ERROR: apport (pid 3639) Fri Dec  4 15:25:32 2020: called for pid 3631, 
signal 11, core limit 0, dump mode 1
ERROR: apport (pid 3639) Fri Dec  4 15:25:32 2020: executable: /usr/bin/cat 
(command line "/usr/bin/cat")
ERROR: apport (pid 3639) Fri Dec  4 15:25:32 2020: gdbus call error: Error: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name o
rg.gnome.SessionManager was not provided by any .service files

ERROR: apport (pid 3639) Fri Dec  4 15:25:32 2020: debug: session gdbus call: 
ERROR: apport (pid 3639) Fri Dec  4 15:25:32 2020: wrote report 
/tmp/tmpehzet8ma/_usr_bin_cat.1000.crash
(gdb) Kill the program being debugged? (y or n) [answered Y; input not from 
terminal]
[Inferior 1 (process 3631) killed]
(gdb) --- post-processing /tmp/tmpehzet8ma/_usr_bin_cat.1000.crash


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

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

Title:
  traceback when running apport as non-root user

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Xenial:
  Fix Committed
Status in apport source package in Bionic:
  Fix Committed
Status in apport source package in Focal:
  Fix Committed
Status in apport source package in Groovy:
  Fix Committed

Bug description:
  [Impact]
  The apport-test-crashes package, which is used to test the Error Tracker 
deployments, fails produce crash files for binary applications since "various 
security hardening fixes" were included in apport. The problematic change is 
the dropping of supplemental groups in data/apport. This results in a 
PermissionError as it is not the root user who is calling 
/usr/share/apport/apport.

  [Test Case]
  The least convulted test case involves using the generate-sigsegv-crash.py 
script from apport-test-crashes. This ends up using a command similar to 
'/usr/share/apport/apport -p 4077 -s 11 -E /usr/bin/gnome-calculator < 
/tmp/20.10-gnome-calculator.core' which then will encounter the Traceback.

  1) Comment out "check_lock()" in /usr/share/apport/apport (This is necessary 
as we are not running as root)
  2) Put a copy of generate-sigsegv-crash.py on disk.
  3) Run 'python3 /tmp/generate-sigsegv-crash.py cat'
  4) Observe the following Traceback:

  Traceback (most recent call last):
    File "/tmp/tmpvkt5d266/apport", line 599, in 
  drop_privileges(True)
    File "/tmp/tmpvkt5d266/apport", line 125, in drop_privileges
  os.setgroups([])
  PermissionError: [Errno 1] Operation not permitted

  With the version of apport from -proposed you'll receive no such
  Traceback.

  [Regression Potential]
  If there is an error in the python code we code see a new traceback for any 
and all crashes being generated, so ensure regular crash generation works too.

  apport-test-crashes code is here:
  
https://code.launchpad.net/~daisy-pluckers/error-tracker-deployment/test-crashes/

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

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

[Touch-packages] [Bug 1906078] Re: Whoopsie sends bug reports automatically without consent

2020-12-04 Thread Brian Murray
Do you happen to have the apport-noui package installed?

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

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

Title:
  Whoopsie sends bug reports automatically without consent

Status in whoopsie package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  So, I just realized about an hour ago that whoopsie has been sending
  bug reports without my consent since May (2020-05-11 to be exact) from
  checking journalctl where I can see lines like these:

  Uploading /var/crash/[...]
  Sent; server replied with: No error
  Response code: 200
  Reported OOPS ID [...]

  I checked the "Diagnostics" GUI in the gnome-control-center and it
  does have "Send error reports to Canonical" set to "Never"... I tried
  switching it to "Manual" and back to "Never" and that did have an
  effect in /etc/, namelely when going from "Never" to "Manual":

    renamed:rc2.d/K01whoopsie -> rc2.d/S01whoopsie
    renamed:rc3.d/K01whoopsie -> rc3.d/S01whoopsie
    renamed:rc4.d/K01whoopsie -> rc4.d/S01whoopsie
    renamed:rc5.d/K01whoopsie -> rc5.d/S01whoopsie
    new file:   systemd/system/multi-user.target.wants/whoopsie.service

  and the opposite effect is achieved when switching back to "Never". So
  far so good, I guess...

  My /etc/ does have a "whoopsie" file (/etc/whoopsie) which doesn't
  seem to be present in clean installations of Ubuntu and which has the
  following contents:

  [General]
  report_metrics=true

  Switching from "true" to "false" does seem to disable whoopsie, so
  that's nice I guess... but what is this file doing here in the first
  place? To clarify, this was originally an Ubuntu 18.04 system which I
  recently upgraded to 20.04 but the unsolicited error report uploads
  have been going on since well before the upgrade so that's not the
  issue.

  I don't remember touching anything on my system relating to apport or
  whoopsie and my shell history doesn't contain anything about whoopsie
  or apport so this situation seems to have occurred on its own (perhaps
  after an update?).

  This is a pretty serious breach of privacy (and of the GDPR) and
  others might also be unknowingly affected like I was, so the team in
  charge of this might want to push an update that for instance resets
  the /etc/whoopsie file if present (if that truly is the problem).

  While I'm at it I would like all the error reports sent from my
  computer to be deleted. Where can I ask for that? I haven't seen an
  option for that anywhere, apart from contacting
  dataprotect...@canonical.com.

  Best regards.

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

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


[Touch-packages] [Bug 1903849] Re: vim ftbfs

2020-12-04 Thread Brian Murray
** Changed in: vim (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  vim ftbfs

Status in vim package in Ubuntu:
  Fix Released

Bug description:
  see
  https://launchpad.net/ubuntu/+source/vim/2:8.2.1913-1ubuntu1

  blocking the perl transition

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

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


[Touch-packages] [Bug 1906565] Re: traceback when running apport as non-root user

2020-12-03 Thread Brian Murray
** Changed in: apport (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: apport (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: apport (Ubuntu Focal)
   Status: New => In Progress

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

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

Title:
  traceback when running apport as non-root user

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Xenial:
  In Progress
Status in apport source package in Bionic:
  In Progress
Status in apport source package in Focal:
  In Progress
Status in apport source package in Groovy:
  Incomplete

Bug description:
  [Impact]
  The apport-test-crashes package, which is used to test the Error Tracker 
deployments, fails produce crash files for binary applications since "various 
security hardening fixes" were included in apport. The problematic change is 
the dropping of supplemental groups in data/apport. This results in a 
PermissionError as it is not the root user who is calling 
/usr/share/apport/apport.

  [Test Case]
  The least convulted test case involves using the generate-sigsegv-crash.py 
script from apport-test-crashes. This ends up using a command similar to 
'/usr/share/apport/apport -p 4077 -s 11 -E /usr/bin/gnome-calculator < 
/tmp/20.10-gnome-calculator.core' which then will encounter the Traceback.

  1) Comment out "check_lock()" in /usr/share/apport/apport (This is necessary 
as we are not running as root)
  2) Put a copy of generate-sigsegv-crash.py on disk.
  3) Run 'python3 /tmp/generate-sigsegv-crash.py cat'
  4) Observe the following Traceback:

  Traceback (most recent call last):
    File "/tmp/tmpvkt5d266/apport", line 599, in 
  drop_privileges(True)
    File "/tmp/tmpvkt5d266/apport", line 125, in drop_privileges
  os.setgroups([])
  PermissionError: [Errno 1] Operation not permitted

  With the version of apport from -proposed you'll receive no such
  Traceback.

  [Regression Potential]
  If there is an error in the python code we code see a new traceback for any 
and all crashes being generated, so ensure regular crash generation works too.

  apport-test-crashes code is here:
  
https://code.launchpad.net/~daisy-pluckers/error-tracker-deployment/test-crashes/

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

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


[Touch-packages] [Bug 1906565] Re: traceback when running apport as non-root user

2020-12-03 Thread Brian Murray
apport (2.20.11-0ubuntu55) hirsute; urgency=medium

  * data/apport: only drop supplemental groups if the user is root.

 -- Brian Murray   Wed, 02 Dec 2020 14:40:29 -0800

** Changed in: apport (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  traceback when running apport as non-root user

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Xenial:
  New
Status in apport source package in Bionic:
  New
Status in apport source package in Focal:
  New
Status in apport source package in Groovy:
  New

Bug description:
  [Impact]
  The apport-test-crashes package, which is used to test the Error Tracker 
deployments, fails produce crash files for binary applications since "various 
security hardening fixes" were included in apport. The problematic change is 
the dropping of supplemental groups in data/apport. This results in a 
PermissionError as it is not the root user who is calling 
/usr/share/apport/apport.

  [Test Case]
  The least convulted test case involves using the generate-sigsegv-crash.py 
script from apport-test-crashes. This ends up using a command similar to 
'/usr/share/apport/apport -p 4077 -s 11 -E /usr/bin/gnome-calculator < 
/tmp/20.10-gnome-calculator.core' which then will encounter the Traceback.

  1) Comment out "check_lock()" in /usr/share/apport/apport (This is necessary 
as we are not running as root)
  2) Put a copy of generate-sigsegv-crash.py on disk.
  3) Run 'python3 /tmp/generate-sigsegv-crash.py cat'
  4) Observe the following Traceback:

  Traceback (most recent call last):
    File "/tmp/tmpvkt5d266/apport", line 599, in 
  drop_privileges(True)
    File "/tmp/tmpvkt5d266/apport", line 125, in drop_privileges
  os.setgroups([])
  PermissionError: [Errno 1] Operation not permitted

  With the version of apport from -proposed you'll receive no such
  Traceback.

  [Regression Potential]
  If there is an error in the python code we code see a new traceback for any 
and all crashes being generated, so ensure regular crash generation works too.

  apport-test-crashes code is here:
  
https://code.launchpad.net/~daisy-pluckers/error-tracker-deployment/test-crashes/

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

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


[Touch-packages] [Bug 1906565] Re: traceback when running apport as non-root user

2020-12-02 Thread Brian Murray
** Description changed:

  [Impact]
  The apport-test-crashes package, which is used to test the Error Tracker 
deployments, fails produce crash files for binary applications since "various 
security hardening fixes" were included in apport. The problematic change is 
the dropping of supplemental groups in data/apport. This results in a 
PermissionError as it is not the root user who is calling 
/usr/share/apport/apport.
  
  [Test Case]
  The least convulted test case involves using the generate-sigsegv-crash.py 
script from apport-test-crashes. This ends up using a command similar to 
'/usr/share/apport/apport -p 4077 -s 11 -E /usr/bin/gnome-calculator < 
/tmp/20.10-gnome-calculator.core' which then will encounter the Traceback.
  
  1) Comment out "check_lock()" in /usr/share/apport/apport (This is necessary 
as we are not running as root)
  2) Put a copy of generate-sigsegv-crash.py on disk.
  3) Run 'python3 /tmp/generate-sigsegv-crash.py cat'
  4) Observe the following Traceback:
  
  Traceback (most recent call last):
-   File "/tmp/tmpvkt5d266/apport", line 599, in 
- drop_privileges(True)
-   File "/tmp/tmpvkt5d266/apport", line 125, in drop_privileges
- os.setgroups([])
+   File "/tmp/tmpvkt5d266/apport", line 599, in 
+ drop_privileges(True)
+   File "/tmp/tmpvkt5d266/apport", line 125, in drop_privileges
+ os.setgroups([])
  PermissionError: [Errno 1] Operation not permitted
  
  With the version of apport from -proposed you'll receive no such
  Traceback.
  
  [Regression Potential]
  If there is an error in the python code we code see a new traceback for any 
and all crashes being generated, so ensure regular crash generation works too.
+ 
+ apport-test-crashes code is here:
+ 
https://code.launchpad.net/~daisy-pluckers/error-tracker-deployment/test-crashes/

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

Title:
  traceback when running apport as non-root user

Status in apport package in Ubuntu:
  In Progress
Status in apport source package in Xenial:
  New
Status in apport source package in Bionic:
  New
Status in apport source package in Focal:
  New
Status in apport source package in Groovy:
  New

Bug description:
  [Impact]
  The apport-test-crashes package, which is used to test the Error Tracker 
deployments, fails produce crash files for binary applications since "various 
security hardening fixes" were included in apport. The problematic change is 
the dropping of supplemental groups in data/apport. This results in a 
PermissionError as it is not the root user who is calling 
/usr/share/apport/apport.

  [Test Case]
  The least convulted test case involves using the generate-sigsegv-crash.py 
script from apport-test-crashes. This ends up using a command similar to 
'/usr/share/apport/apport -p 4077 -s 11 -E /usr/bin/gnome-calculator < 
/tmp/20.10-gnome-calculator.core' which then will encounter the Traceback.

  1) Comment out "check_lock()" in /usr/share/apport/apport (This is necessary 
as we are not running as root)
  2) Put a copy of generate-sigsegv-crash.py on disk.
  3) Run 'python3 /tmp/generate-sigsegv-crash.py cat'
  4) Observe the following Traceback:

  Traceback (most recent call last):
    File "/tmp/tmpvkt5d266/apport", line 599, in 
  drop_privileges(True)
    File "/tmp/tmpvkt5d266/apport", line 125, in drop_privileges
  os.setgroups([])
  PermissionError: [Errno 1] Operation not permitted

  With the version of apport from -proposed you'll receive no such
  Traceback.

  [Regression Potential]
  If there is an error in the python code we code see a new traceback for any 
and all crashes being generated, so ensure regular crash generation works too.

  apport-test-crashes code is here:
  
https://code.launchpad.net/~daisy-pluckers/error-tracker-deployment/test-crashes/

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

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


[Touch-packages] [Bug 1906565] Re: traceback when running apport as non-root user

2020-12-02 Thread Brian Murray
** Also affects: apport (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: apport (Ubuntu Groovy)
   Importance: Undecided
   Status: New

** Also affects: apport (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: apport (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Tags added: fr-978

** Changed in: apport (Ubuntu)
 Assignee: (unassigned) => Brian Murray (brian-murray)

** Changed in: apport (Ubuntu)
   Status: New => In Progress

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

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

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

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

** Changed in: apport (Ubuntu Bionic)
 Assignee: (unassigned) => Brian Murray (brian-murray)

** Changed in: apport (Ubuntu Focal)
 Assignee: (unassigned) => Brian Murray (brian-murray)

** Changed in: apport (Ubuntu Groovy)
 Assignee: (unassigned) => Brian Murray (brian-murray)

** Changed in: apport (Ubuntu Xenial)
 Assignee: (unassigned) => Brian Murray (brian-murray)

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

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

Title:
  traceback when running apport as non-root user

Status in apport package in Ubuntu:
  In Progress
Status in apport source package in Xenial:
  New
Status in apport source package in Bionic:
  New
Status in apport source package in Focal:
  New
Status in apport source package in Groovy:
  New

Bug description:
  [Impact]
  The apport-test-crashes package, which is used to test the Error Tracker 
deployments, fails produce crash files for binary applications since "various 
security hardening fixes" were included in apport. The problematic change is 
the dropping of supplemental groups in data/apport. This results in a 
PermissionError as it is not the root user who is calling 
/usr/share/apport/apport.

  [Test Case]
  The least convulted test case involves using the generate-sigsegv-crash.py 
script from apport-test-crashes. This ends up using a command similar to 
'/usr/share/apport/apport -p 4077 -s 11 -E /usr/bin/gnome-calculator < 
/tmp/20.10-gnome-calculator.core' which then will encounter the Traceback.

  1) Comment out "check_lock()" in /usr/share/apport/apport (This is necessary 
as we are not running as root)
  2) Put a copy of generate-sigsegv-crash.py on disk.
  3) Run 'python3 /tmp/generate-sigsegv-crash.py cat'
  4) Observe the following Traceback:

  Traceback (most recent call last):
File "/tmp/tmpvkt5d266/apport", line 599, in 
  drop_privileges(True)
File "/tmp/tmpvkt5d266/apport", line 125, in drop_privileges
  os.setgroups([])
  PermissionError: [Errno 1] Operation not permitted

  With the version of apport from -proposed you'll receive no such
  Traceback.

  [Regression Potential]
  If there is an error in the python code we code see a new traceback for any 
and all crashes being generated, so ensure regular crash generation works too.

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

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


[Touch-packages] [Bug 1906565] [NEW] traceback when running apport as non-root user

2020-12-02 Thread Brian Murray
Public bug reported:

[Impact]
The apport-test-crashes package, which is used to test the Error Tracker 
deployments, fails produce crash files for binary applications since "various 
security hardening fixes" were included in apport. The problematic change is 
the dropping of supplemental groups in data/apport. This results in a 
PermissionError as it is not the root user who is calling 
/usr/share/apport/apport.

[Test Case]
The least convulted test case involves using the generate-sigsegv-crash.py 
script from apport-test-crashes. This ends up using a command similar to 
'/usr/share/apport/apport -p 4077 -s 11 -E /usr/bin/gnome-calculator < 
/tmp/20.10-gnome-calculator.core' which then will encounter the Traceback.

1) Comment out "check_lock()" in /usr/share/apport/apport (This is necessary as 
we are not running as root)
2) Put a copy of generate-sigsegv-crash.py on disk.
3) Run 'python3 /tmp/generate-sigsegv-crash.py cat'
4) Observe the following Traceback:

Traceback (most recent call last):
  File "/tmp/tmpvkt5d266/apport", line 599, in 
drop_privileges(True)
  File "/tmp/tmpvkt5d266/apport", line 125, in drop_privileges
os.setgroups([])
PermissionError: [Errno 1] Operation not permitted

With the version of apport from -proposed you'll receive no such
Traceback.

[Regression Potential]
If there is an error in the python code we code see a new traceback for any and 
all crashes being generated, so ensure regular crash generation works too.

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

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

Title:
  traceback when running apport as non-root user

Status in apport package in Ubuntu:
  New

Bug description:
  [Impact]
  The apport-test-crashes package, which is used to test the Error Tracker 
deployments, fails produce crash files for binary applications since "various 
security hardening fixes" were included in apport. The problematic change is 
the dropping of supplemental groups in data/apport. This results in a 
PermissionError as it is not the root user who is calling 
/usr/share/apport/apport.

  [Test Case]
  The least convulted test case involves using the generate-sigsegv-crash.py 
script from apport-test-crashes. This ends up using a command similar to 
'/usr/share/apport/apport -p 4077 -s 11 -E /usr/bin/gnome-calculator < 
/tmp/20.10-gnome-calculator.core' which then will encounter the Traceback.

  1) Comment out "check_lock()" in /usr/share/apport/apport (This is necessary 
as we are not running as root)
  2) Put a copy of generate-sigsegv-crash.py on disk.
  3) Run 'python3 /tmp/generate-sigsegv-crash.py cat'
  4) Observe the following Traceback:

  Traceback (most recent call last):
File "/tmp/tmpvkt5d266/apport", line 599, in 
  drop_privileges(True)
File "/tmp/tmpvkt5d266/apport", line 125, in drop_privileges
  os.setgroups([])
  PermissionError: [Errno 1] Operation not permitted

  With the version of apport from -proposed you'll receive no such
  Traceback.

  [Regression Potential]
  If there is an error in the python code we code see a new traceback for any 
and all crashes being generated, so ensure regular crash generation works too.

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

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


[Touch-packages] [Bug 1899100] Re: whoopsie assert failure: double free or corruption (fasttop)

2020-12-02 Thread Brian Murray
Setting to verification-done for Groovy given that the buckets linked to
in the bug description do not contain whoopsie version number 0.2.72.1
and there are no new buckets with similar signatures.

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

** Changed in: whoopsie (Ubuntu Bionic)
 Assignee: (unassigned) => Brian Murray (brian-murray)

** Changed in: whoopsie (Ubuntu Focal)
 Assignee: (unassigned) => Brian Murray (brian-murray)

** Changed in: whoopsie (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: whoopsie (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 whoopsie in Ubuntu.
https://bugs.launchpad.net/bugs/1899100

Title:
  whoopsie assert failure: double free or corruption (fasttop)

Status in whoopsie package in Ubuntu:
  Fix Released
Status in whoopsie source package in Bionic:
  In Progress
Status in whoopsie source package in Focal:
  In Progress
Status in whoopsie source package in Groovy:
  Fix Committed

Bug description:
  [Impact]
  whoopsie is crashing somewhat regularly. There are a couple of crashes in the 
Error Tracker which look similar:

  https://errors.ubuntu.com/problem/5c1f68854a0f3bd5e263f1cd35e4dd944c9e90bd
  https://errors.ubuntu.com/problem/5d7e641dc46229c08389420fdd74a7473d2dec98

  As of yet (2020-11-22) neither crash is happening with whoopsie
  version 0.2.73.

  [Test Case]
  We don't have a manual test case for this crash report but given the number 
of crashes in the Error Tracker and the number of users of whoopsie the absence 
of the same crash occurring with the new version of whoopsie should be enough 
to consider this verified.

  [Regression Potential]
  Whoopsie will no longer upload crash reports with duplicate keys but this was 
not something it should have been doing in the first place. That being said we 
should also test whoopsie with a sample of crashes (apport-test-crashes) and 
ensure they are received by the staging version of the Ubuntu Error Tracker.

  Original Description
  
  Apport popped up saying whoopsie had crashed (I assume during a previous 
crash report upload?)

  ProblemType: CrashDistroRelease: Ubuntu 20.10
  Package: whoopsie 0.2.72
  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-0ubuntu49
  Architecture: amd64
  AssertionMessage: double free or corruption (fasttop)
  CasperMD5CheckResult: skip
  CrashCounter: 1
  Date: Fri Oct  9 08:08:56 2020
  ExecutablePath: /usr/bin/whoopsie
  InstallationDate: Installed on 2019-11-18 (325 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcCmdline: /usr/bin/whoopsie -f
  ProcEnviron:
   LANG=en_AU.UTF-8
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
  RelatedPackageVersions: apport-noui N/ASignal: 6SourcePackage: whoopsie
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f5982159128 
"%s\n") at ../sysdeps/posix/libc_fatal.c:155
   malloc_printerr (str=str@entry=0x7f598215b5d8 "double free or corruption 
(fasttop)") at malloc.c:5389
   _int_free (av=0x7f598218bba0 , p=0x55964a2bf3e0, have_lock=0) at 
malloc.c:4298
   () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_hash_table_remove_all () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: whoopsie assert failure: double free or corruption (fasttop)
  UpgradeStatus: Upgraded to groovy on 2020-10-06 (2 days ago)
  UserGroups: N/A
  separator:

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

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


[Touch-packages] [Bug 1899288] Re: Python3 can't co-exist with Oracle's VirtualBox on 20.10

2020-12-01 Thread Brian Murray
I'm sorry but I'm not following along with the issue you are describing.
Could you please provide instructions so I can recreate the problem you
are seeing? Additionally, are you using virtualbox from the official
Ubuntu archive?

Additionally, python-is-python3 only depends on python3 and not dh-
python as you've described.

** Changed in: what-is-python (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  Python3 can't co-exist with Oracle's VirtualBox on 20.10

Status in dh-python package in Ubuntu:
  Confirmed
Status in what-is-python package in Ubuntu:
  Incomplete

Bug description:
  Sorry I couldn't file this bug against the correct packages. The form
  told me there are no such packages as python-is-python3 and dh-python
  in Ubuntu...

  Release: Groovy Gorilla (Ubuntu 20.10).

  Package versions: 
  python-is-python3 3.8.2-4
  dh-python 4.20200925

  The release of Ubuntu 20.10 is less than two weeks out, so I'd like to
  draw attention to a problem I've run into. It seems that 20.10
  defaults to python3 and wants to install python-is-python3, which
  pulls in the latest version of dh-python, which in turn can't co-exist
  with Oracle's Virtualbox-6.1 and wants to uninstall it.

  I don't mind having _both_ python2 (apparently a requirement of
  VirtualBox) and python3 installed. But as of right now I can have
  either python-is-python3, and not be able to do a complete upgrade
  since virtualbox-6.1 will be uninstalled, or python-is-python2, in
  which case I cripple 20.10's python3 install, since I won't get dh-
  python and python-six.

  Ia there something the python packagers do about this?

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

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


[Touch-packages] [Bug 1905735] Re: ubuntu-image autopkgtests failing since python-debian 0.1.38

2020-12-01 Thread Brian Murray
** Tags added: rls-hh-incoming

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

Title:
  ubuntu-image autopkgtests failing since python-debian 0.1.38

Status in python-debian package in Ubuntu:
  Triaged
Status in ubuntu-image package in Ubuntu:
  Fix Committed
Status in python-debian package in Debian:
  Unknown

Bug description:
  In the tests it seems that since some - yet to be found - change ~20th
  Nov the tests of ubuntu-image fail.

  Tests all list those three sub-tests as failing:
   unittests.sh FAIL non-zero exit status 1
   qa   FAIL non-zero exit status 1
   coverage.sh  FAIL non-zero exit status 1

  Fails all seem to be related to some python/pytest/py* change that
  might have slipped in without gating on this test.

  Ubuntu-image itself also isn't new - still the same as in groovy
   ubuntu-image | 1.10+20.10ubuntu2 | groovy | source, all
   ubuntu-image | 1.10+20.10ubuntu2 | hirsute| source, all

  == log start 
===
  Obtaining file:///tmp/autopkgtest.ZuL7Da/build.chY/src
  ERROR: Command errored out with exit status 1:
   command: 
/tmp/autopkgtest.ZuL7Da/build.chY/src/.tox/py38-nocov/bin/python -c 'import 
sys, setuptools, tokenize; sys.argv[0] = 
'"'"'/tmp/autopkgtest.ZuL7Da/build.chY/src/setup.py'"'"'; 
__file__='"'"'/tmp/autopkgtest.ZuL7Da/build.chY/src/setup.py'"'"';f=getattr(tokenize,
 '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', 
'"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' egg_info 
--egg-base /tmp/pip-pip-egg-info-yaplrymq
   cwd: /tmp/autopkgtest.ZuL7Da/build.chY/src/
  Complete output (5 lines):
  Traceback (most recent call last):
    File "", line 1, in 
    File "/tmp/autopkgtest.ZuL7Da/build.chY/src/setup.py", line 49, in 

  __version__ = str(Changelog(infp).get_version())
  AttributeError: 'Changelog' object has no attribute 'get_version'
  
  ERROR: Command errored out with exit status 1: python setup.py egg_info Check 
the logs for full command output.
  === log end 


  The issue reproducible in local KVM-autopkgtest against hirsute-proposed and 
hirsute-release for me (I mistyped before).
  Example:
   sudo ~/work/autopkgtest/autopkgtest/runner/autopkgtest --no-built-binaries 
--apt-upgrade --apt-pocket=proposed --shell-fail 
ubuntu-image_1.10+20.10ubuntu2.dsc --testname=qa -- qemu --qemu-options='-cpu 
host' --ram-size=1536 --cpus 2 ~/work/autopkgtest-hirsute-amd64.img

  
  In terms of similar bug signatures I found
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973227
  Fixed by:
  
https://gitlab.kitware.com/debian/dh-cmake/-/commit/3337c8e0e9ebd109490d3c40f0bd5c1e367bedc8

  Looking for the same issue in ubuntu-image has shown an entry in setup.py
    setup.py:49:__version__ = str(Changelog(infp).get_version())

  And now that we know all that we see
  https://launchpad.net/ubuntu/+source/python-debian/+publishinghistory

  New version in since
  2020-11-20 02:23:27 CET

  That is a perfect match to our bug.


  $ diff -Naur python-debian-0.1.3[78]/lib/debian/changelog.py
  ...
  -def get_version(self):
  -# type: () -> Version
  +def _get_version(self):
  +# type: () -> Optional[Version]
   """Return a Version object for the last version"""
  -return self._blocks[0].version
  +return self._blocks[0].version   # type: ignore
  ...

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

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


[Touch-packages] [Bug 1903329] Please test proposed package

2020-12-01 Thread Brian Murray
Hello Salim, or anyone else affected,

Accepted librsvg into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/librsvg/2.48.9-1ubuntu0.20.04.1 in
a few hours, and then in the -proposed repository.

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

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

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

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

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

Title:
  SRU the current 2.48.9 stable update

Status in librsvg package in Ubuntu:
  Fix Released
Status in librsvg source package in Focal:
  Fix Committed

Bug description:
  * Impact

  That's the current GNOME stable update, which fixes a number of
  issues, including a regression[1] since librsvg 2.40.x which was
  shipped in Ubuntu 16.04. The NEWS file[2] summarizes the relevant
  changes between Ubuntu 20.04's current librsvg 2.48.7 (that version
  was also introduced by an SRU back in July[3]) and the current version
  2.48.9. The complete list of changes is available on GNOME GitLab[4].

  * Test case

  The update is part of GNOME stable updates[5].

  Smoke testing by opening SVG images with eog or importing them with
  gimp can be performed to ensure there are no regressions.

  * Regression potential

  This is a bugfix-only stable micro-release, however librsvg is a core
  component with a number of reverse dependencies. A combination of
  autopkgtests and manual smoke testing to try and detect SVG rendering
  issues should be performed.

  * Notes about this report

  This is my first SRU request (and at the same time my first launchpad
  bug report). I'm not really familiar with the whole SRU process which
  is why I first asked about it on Ubuntu's official discourse forum[6].
  Canonical's Sebastien Bacher encouraged me to open this ticket. I've
  copied over some parts of the last librsvg SRU ticket[3]. I hope this
  is fine.

  Thanks for considering this SRU.

  [1]: https://gitlab.gnome.org/GNOME/librsvg/-/issues/642

  [2]: https://gitlab.gnome.org/GNOME/librsvg/-/blob/librsvg-2.48/NEWS

  [3]: https://bugs.launchpad.net/bugs/1884326

  [4]: https://gitlab.gnome.org/GNOME/librsvg/-/compare/2.48.7...2.48.9

  [5]: https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  [6]: https://discourse.ubuntu.com/t/most-straight-forward-way-to-get-
  librsvg2-microrelease-update-into-focal-updates/19238

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

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


[Touch-packages] [Bug 1903329] Re: SRU the current 2.48.9 stable update

2020-12-01 Thread Brian Murray
Should groovy also get the fix for upstream issue 642?

** Changed in: librsvg (Ubuntu Focal)
   Status: In Progress => Fix Committed

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

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

Title:
  SRU the current 2.48.9 stable update

Status in librsvg package in Ubuntu:
  Fix Released
Status in librsvg source package in Focal:
  Fix Committed

Bug description:
  * Impact

  That's the current GNOME stable update, which fixes a number of
  issues, including a regression[1] since librsvg 2.40.x which was
  shipped in Ubuntu 16.04. The NEWS file[2] summarizes the relevant
  changes between Ubuntu 20.04's current librsvg 2.48.7 (that version
  was also introduced by an SRU back in July[3]) and the current version
  2.48.9. The complete list of changes is available on GNOME GitLab[4].

  * Test case

  The update is part of GNOME stable updates[5].

  Smoke testing by opening SVG images with eog or importing them with
  gimp can be performed to ensure there are no regressions.

  * Regression potential

  This is a bugfix-only stable micro-release, however librsvg is a core
  component with a number of reverse dependencies. A combination of
  autopkgtests and manual smoke testing to try and detect SVG rendering
  issues should be performed.

  * Notes about this report

  This is my first SRU request (and at the same time my first launchpad
  bug report). I'm not really familiar with the whole SRU process which
  is why I first asked about it on Ubuntu's official discourse forum[6].
  Canonical's Sebastien Bacher encouraged me to open this ticket. I've
  copied over some parts of the last librsvg SRU ticket[3]. I hope this
  is fine.

  Thanks for considering this SRU.

  [1]: https://gitlab.gnome.org/GNOME/librsvg/-/issues/642

  [2]: https://gitlab.gnome.org/GNOME/librsvg/-/blob/librsvg-2.48/NEWS

  [3]: https://bugs.launchpad.net/bugs/1884326

  [4]: https://gitlab.gnome.org/GNOME/librsvg/-/compare/2.48.7...2.48.9

  [5]: https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  [6]: https://discourse.ubuntu.com/t/most-straight-forward-way-to-get-
  librsvg2-microrelease-update-into-focal-updates/19238

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

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


[Touch-packages] [Bug 1905775] Re: Uninstalling python3-apporrt should not uninstall xorg packages

2020-12-01 Thread Brian Murray
This does not have to do with apport's dependencies, rather it is an
xorg package which depends on apport and the removal of python3-apport
causing the xorg package to have missing dependencies.

bdmurray@clean-focal-amd64:~$ apt-cache show xserver-xorg
Package: xserver-xorg
Architecture: amd64
Version: 1:7.7+19ubuntu14
Priority: optional
Section: x11
Source: xorg
Origin: Ubuntu
Maintainer: Ubuntu X-SWAT 
Original-Maintainer: Debian X Strike Force 
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 411
Provides: xserver
Depends: xserver-xorg-core (>= 2:1.17.2-2), xserver-xorg-input-all | 
xorg-driver-input, xkb-data (>= 1.4), x11-xkb-utils, python3-apport
Recommends: libgl1-mesa-dri, mesa-vulkan-drivers, xserver-xorg-legacy, 
xserver-xorg-video-all
Breaks: xdiagnose (<< 3.8.8)
Replaces: xdiagnose (<< 3.8.8)
Filename: pool/main/x/xorg/xserver-xorg_7.7+19ubuntu14_amd64.deb
Size: 65176
MD5sum: 3ed74cae9268cf378a6fc2e8a77f53ed
SHA1: 6cffe8eb38acffed33937ae7fc37d3e04973e33d
SHA256: 7b2380dbdc991497443b57dba4fe4335234e53a125d0b18f1b9b5ef3c492eab5
Homepage: http://www.x.org/
Description-en: X.Org X server
 This package depends on the full suite of the server and drivers for the
 X.Org X server.  It does not provide the actual server itself.
Description-md5: 3d8c1d268e8af6b69f54d86fbd5a3939
Task: ubuntu-desktop-minimal, ubuntu-desktop, kubuntu-desktop, xubuntu-core, 
xubuntu-desktop, lubuntu-desktop, ubuntustudio-desktop-core, 
ubuntustudio-desktop, ubuntukylin-desktop, ubuntu-mate-core, 
ubuntu-mate-desktop, ubuntu-budgie-deskt
op

If you are looking to disable apport you should adjust the following
file:

bdmurray@clean-focal-amd64:~$ cat /etc/default/apport 
# set this to 0 to disable apport, or to 1 to enable it
# you can temporarily override this with
# sudo service apport start force_start=1
enabled=1

** Project changed: apport => xorg (Ubuntu)

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

Title:
  Uninstalling python3-apporrt should not uninstall xorg packages

Status in xorg package in Ubuntu:
  New

Bug description:
  ```
  sudo apt purge python3-apport 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages were automatically installed and are no longer 
required:
libglu1-mesa libxfont2 python3-certifi python3-chardet python3-idna 
python3-problem-report python3-requests
python3-requests-unixsocket python3-urllib3 x11-apps x11-session-utils 
xinit xinput xserver-common
xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-libinput
  Use 'sudo apt autoremove' to remove them.
  The following packages will be REMOVED:
python3-apport* xorg* xserver-xorg*
  0 upgraded, 0 newly installed, 3 to remove and 61 not upgraded.
  After this operation, 1,070 kB disk space will be freed.
  Do you want to continue? [Y/n] ^C
  ```

  so, apparently dependencies aren't correctly set, because I don't want
  to send no problem reports but still want to use xorg subsystem

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

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


[Touch-packages] [Bug 1906078] Re: Whoopsie sends bug reports automatically without consent

2020-11-30 Thread Brian Murray
** Tags added: rls-hh-incoming

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

Title:
  Whoopsie sends bug reports automatically without consent

Status in whoopsie package in Ubuntu:
  New

Bug description:
  Hello,

  So, I just realized about an hour ago that whoopsie has been sending
  bug reports without my consent since May (2020-05-11 to be exact) from
  checking journalctl where I can see lines like these:

  Uploading /var/crash/[...]
  Sent; server replied with: No error
  Response code: 200
  Reported OOPS ID [...]

  I checked the "Diagnostics" GUI in the gnome-control-center and it
  does have "Send error reports to Canonical" set to "Never"... I tried
  switching it to "Manual" and back to "Never" and that did have an
  effect in /etc/, namelely when going from "Never" to "Manual":

    renamed:rc2.d/K01whoopsie -> rc2.d/S01whoopsie
    renamed:rc3.d/K01whoopsie -> rc3.d/S01whoopsie
    renamed:rc4.d/K01whoopsie -> rc4.d/S01whoopsie
    renamed:rc5.d/K01whoopsie -> rc5.d/S01whoopsie
    new file:   systemd/system/multi-user.target.wants/whoopsie.service

  and the opposite effect is achieved when switching back to "Never". So
  far so good, I guess...

  My /etc/ does have a "whoopsie" file (/etc/whoopsie) which doesn't
  seem to be present in clean installations of Ubuntu and which has the
  following contents:

  [General]
  report_metrics=true

  Switching from "true" to "false" does seem to disable whoopsie, so
  that's nice I guess... but what is this file doing here in the first
  place? To clarify, this was originally an Ubuntu 18.04 system which I
  recently upgraded to 20.04 but the unsolicited error report uploads
  have been going on since well before the upgrade so that's not the
  issue.

  I don't remember touching anything on my system relating to apport or
  whoopsie and my shell history doesn't contain anything about whoopsie
  or apport so this situation seems to have occurred on its own (perhaps
  after an update?).

  This is a pretty serious breach of privacy (and of the GDPR) and
  others might also be unknowingly affected like I was, so the team in
  charge of this might want to push an update that for instance resets
  the /etc/whoopsie file if present (if that truly is the problem).

  While I'm at it I would like all the error reports sent from my
  computer to be deleted. Where can I ask for that? I haven't seen an
  option for that anywhere, apart from contacting
  dataprotect...@canonical.com.

  Best regards.

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

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


[Touch-packages] [Bug 1833174] Re: Shadowing the vim-window results in vim-gtk3 crash

2020-11-25 Thread Brian Murray
** Changed in: vim (Ubuntu)
   Status: Triaged => Fix Committed

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

Title:
   Shadowing the vim-window results in vim-gtk3 crash

Status in vim:
  Unknown
Status in vim package in Ubuntu:
  Fix Committed
Status in vim source package in Focal:
  Triaged
Status in vim source package in Groovy:
  Triaged

Bug description:
  With XFCE when I try to "shadow" the vim-gtk3 window (just to show only the 
title bar) it results in a vim crash and the window just disappears without any 
core dump neither .swp files on.
  The only message I get on the terminal is

  BadMatch (invalid parameter attributes)
  Vim: Got X error
  Vim: Finished.

  This behaviour started from Xubuntu 18.04.
  The vim-gtk package is not suffering from this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: vim-gtk3 2:8.1.0320-1ubuntu3.1
  ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
  Uname: Linux 5.0.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Jun 18 09:10:38 2019
  InstallationDate: Installed on 2019-04-23 (55 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: vim
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1899100] Re: whoopsie assert failure: double free or corruption (fasttop)

2020-11-24 Thread Brian Murray
** Also affects: whoopsie (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: whoopsie (Ubuntu Groovy)
   Importance: Undecided
   Status: New

** Also affects: whoopsie (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: whoopsie (Ubuntu Groovy)
   Status: New => In Progress

** Changed in: whoopsie (Ubuntu Groovy)
 Assignee: (unassigned) => Brian Murray (brian-murray)

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

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

Title:
  whoopsie assert failure: double free or corruption (fasttop)

Status in whoopsie package in Ubuntu:
  Fix Released
Status in whoopsie source package in Bionic:
  New
Status in whoopsie source package in Focal:
  New
Status in whoopsie source package in Groovy:
  In Progress

Bug description:
  [Impact]
  whoopsie is crashing somewhat regularly. There are a couple of crashes in the 
Error Tracker which look similar:

  https://errors.ubuntu.com/problem/5c1f68854a0f3bd5e263f1cd35e4dd944c9e90bd
  https://errors.ubuntu.com/problem/5d7e641dc46229c08389420fdd74a7473d2dec98

  As of yet (2020-11-22) neither crash is happening with whoopsie
  version 0.2.73.

  [Test Case]
  We don't have a manual test case for this crash report but given the number 
of crashes in the Error Tracker and the number of users of whoopsie the absence 
of the same crash occurring with the new version of whoopsie should be enough 
to consider this verified.

  [Regression Potential]
  Whoopsie will no longer upload crash reports with duplicate keys but this was 
not something it should have been doing in the first place. That being said we 
should also test whoopsie with a sample of crashes (apport-test-crashes) and 
ensure they are received by the staging version of the Ubuntu Error Tracker.

  Original Description
  
  Apport popped up saying whoopsie had crashed (I assume during a previous 
crash report upload?)

  ProblemType: CrashDistroRelease: Ubuntu 20.10
  Package: whoopsie 0.2.72
  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-0ubuntu49
  Architecture: amd64
  AssertionMessage: double free or corruption (fasttop)
  CasperMD5CheckResult: skip
  CrashCounter: 1
  Date: Fri Oct  9 08:08:56 2020
  ExecutablePath: /usr/bin/whoopsie
  InstallationDate: Installed on 2019-11-18 (325 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcCmdline: /usr/bin/whoopsie -f
  ProcEnviron:
   LANG=en_AU.UTF-8
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
  RelatedPackageVersions: apport-noui N/ASignal: 6SourcePackage: whoopsie
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f5982159128 
"%s\n") at ../sysdeps/posix/libc_fatal.c:155
   malloc_printerr (str=str@entry=0x7f598215b5d8 "double free or corruption 
(fasttop)") at malloc.c:5389
   _int_free (av=0x7f598218bba0 , p=0x55964a2bf3e0, have_lock=0) at 
malloc.c:4298
   () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_hash_table_remove_all () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: whoopsie assert failure: double free or corruption (fasttop)
  UpgradeStatus: Upgraded to groovy on 2020-10-06 (2 days ago)
  UserGroups: N/A
  separator:

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

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


[Touch-packages] [Bug 1899100] Re: whoopsie assert failure: double free or corruption (fasttop)

2020-11-24 Thread Brian Murray
** Description changed:

  [Impact]
  whoopsie is crashing somewhat regularly. There are a couple of crashes in the 
Error Tracker which look similar:
  
  https://errors.ubuntu.com/problem/5c1f68854a0f3bd5e263f1cd35e4dd944c9e90bd
  https://errors.ubuntu.com/problem/5d7e641dc46229c08389420fdd74a7473d2dec98
  
  As of yet (2020-11-22) neither crash is happening with whoopsie version
  0.2.73.
  
+ [Test Case]
+ We don't have a manual test case for this crash report but given the number 
of crashes in the Error Tracker and the number of users of whoopsie the absence 
of the same crash occurring with the new version of whoopsie should be enough 
to consider this verified.
  
+ [Regression Potential]
+ Whoopsie will no longer upload crash reports with duplicate keys but this was 
not something it should have been doing in the first place. That being said we 
should also test whoopsie with a sample of crashes (apport-test-crashes) and 
ensure they are received by the staging version of the Ubuntu Error Tracker.
+ 
+ Original Description
+ 
  Apport popped up saying whoopsie had crashed (I assume during a previous 
crash report upload?)
  
  ProblemType: CrashDistroRelease: Ubuntu 20.10
  Package: whoopsie 0.2.72
  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-0ubuntu49
  Architecture: amd64
  AssertionMessage: double free or corruption (fasttop)
  CasperMD5CheckResult: skip
  CrashCounter: 1
  Date: Fri Oct  9 08:08:56 2020
  ExecutablePath: /usr/bin/whoopsie
  InstallationDate: Installed on 2019-11-18 (325 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcCmdline: /usr/bin/whoopsie -f
  ProcEnviron:
   LANG=en_AU.UTF-8
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
- RelatedPackageVersions: apport-noui N/A
- Signal: 6SourcePackage: whoopsie
+ RelatedPackageVersions: apport-noui N/ASignal: 6SourcePackage: whoopsie
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f5982159128 
"%s\n") at ../sysdeps/posix/libc_fatal.c:155
   malloc_printerr (str=str@entry=0x7f598215b5d8 "double free or corruption 
(fasttop)") at malloc.c:5389
   _int_free (av=0x7f598218bba0 , p=0x55964a2bf3e0, have_lock=0) at 
malloc.c:4298
   () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_hash_table_remove_all () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: whoopsie assert failure: double free or corruption (fasttop)
  UpgradeStatus: Upgraded to groovy on 2020-10-06 (2 days ago)
  UserGroups: N/A
  separator:

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

Title:
  whoopsie assert failure: double free or corruption (fasttop)

Status in whoopsie package in Ubuntu:
  Fix Released
Status in whoopsie source package in Bionic:
  New
Status in whoopsie source package in Focal:
  New
Status in whoopsie source package in Groovy:
  In Progress

Bug description:
  [Impact]
  whoopsie is crashing somewhat regularly. There are a couple of crashes in the 
Error Tracker which look similar:

  https://errors.ubuntu.com/problem/5c1f68854a0f3bd5e263f1cd35e4dd944c9e90bd
  https://errors.ubuntu.com/problem/5d7e641dc46229c08389420fdd74a7473d2dec98

  As of yet (2020-11-22) neither crash is happening with whoopsie
  version 0.2.73.

  [Test Case]
  We don't have a manual test case for this crash report but given the number 
of crashes in the Error Tracker and the number of users of whoopsie the absence 
of the same crash occurring with the new version of whoopsie should be enough 
to consider this verified.

  [Regression Potential]
  Whoopsie will no longer upload crash reports with duplicate keys but this was 
not something it should have been doing in the first place. That being said we 
should also test whoopsie with a sample of crashes (apport-test-crashes) and 
ensure they are received by the staging version of the Ubuntu Error Tracker.

  Original Description
  
  Apport popped up saying whoopsie had crashed (I assume during a previous 
crash report upload?)

  ProblemType: CrashDistroRelease: Ubuntu 20.10
  Package: whoopsie 0.2.72
  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-0ubuntu49
  Architecture: amd64
  AssertionMessage: double free or corruption (fasttop)
  CasperMD5CheckResult: skip
  CrashCounter: 1
  Date: Fri Oct  9 08:08:56 2020
  ExecutablePath: /usr/bin/whoopsie
  InstallationDate: Installed on 2019-11-18 (325 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcCmdline: /usr/bin/whoopsie -f
  ProcEnviron:
   LANG=en_AU.UTF-8
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
  

[Touch-packages] [Bug 1904671] Re: After a certain amount of time after the session is launched, mouse clicks are no longer accepted

2020-11-24 Thread Brian Murray
** Package changed: ubuntu-release-upgrader (Ubuntu) => xorg (Ubuntu)

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

Title:
  After a certain amount of time after the session is launched, mouse
  clicks are no longer accepted

Status in xorg package in Ubuntu:
  New

Bug description:
  X11, Wayland, the Gnome Desktop does not recognize mouse clicks and
  drags after several tens of minutes after launching. However, it does
  recognize the movement of the mouse cursor.

  [How To Reploduce]

  1. login in a Gnome session.
  2. launch some applications.
  3. use it for a few dozen minutes.
  4. attempt to click and drag with a mouse or other pointing device.

  [Actual Result]

  I can no longer select mouse click application windows, activity
  buttons, dashes, etc.

  [Expect Result]

  I will accept mouse clicks until the end of the session, and possibly
  hope that the event is executed when the click is made.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: ubuntu-release-upgrader-core 1:20.10.13
  ProcVersionSignature: Ubuntu 5.8.0-28.30-lowlatency 5.8.14
  Uname: Linux 5.8.0-28-lowlatency x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu50.1
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 18 13:29:28 2020
  InstallationDate: Installed on 2018-05-20 (913 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ja_JP.UTF-8
   SHELL=/usr/bin/fish
  RebootRequiredPkgs:
   gnome-shell
   linux-image-5.8.0-29-lowlatency
   linux-base
   linux-image-5.8.0-29-generic
   linux-base
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to groovy on 2020-10-25 (23 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
126: Error executing command as another user: Request dismissed
  VarLogDistupgradeApttermlog: Error: [Errno 13] 許可がありません: 
'/var/log/dist-upgrade/apt-term.log'
  VarLogDistupgradeTermlog:

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

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


[Touch-packages] [Bug 1899100] Re: whoopsie assert failure: double free or corruption (fasttop)

2020-11-24 Thread Brian Murray
Bug 1892713 seems to be a duplicate of this one or will be fixed by the
same changes that went into whoopsie 0.2.73.

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

Title:
  whoopsie assert failure: double free or corruption (fasttop)

Status in whoopsie package in Ubuntu:
  Fix Released

Bug description:
  [Impact]
  whoopsie is crashing somewhat regularly. There are a couple of crashes in the 
Error Tracker which look similar:

  https://errors.ubuntu.com/problem/5c1f68854a0f3bd5e263f1cd35e4dd944c9e90bd
  https://errors.ubuntu.com/problem/5d7e641dc46229c08389420fdd74a7473d2dec98

  As of yet (2020-11-22) neither crash is happening with whoopsie
  version 0.2.73.

  
  Apport popped up saying whoopsie had crashed (I assume during a previous 
crash report upload?)

  ProblemType: CrashDistroRelease: Ubuntu 20.10
  Package: whoopsie 0.2.72
  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-0ubuntu49
  Architecture: amd64
  AssertionMessage: double free or corruption (fasttop)
  CasperMD5CheckResult: skip
  CrashCounter: 1
  Date: Fri Oct  9 08:08:56 2020
  ExecutablePath: /usr/bin/whoopsie
  InstallationDate: Installed on 2019-11-18 (325 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcCmdline: /usr/bin/whoopsie -f
  ProcEnviron:
   LANG=en_AU.UTF-8
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
  RelatedPackageVersions: apport-noui N/A
  Signal: 6SourcePackage: whoopsie
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f5982159128 
"%s\n") at ../sysdeps/posix/libc_fatal.c:155
   malloc_printerr (str=str@entry=0x7f598215b5d8 "double free or corruption 
(fasttop)") at malloc.c:5389
   _int_free (av=0x7f598218bba0 , p=0x55964a2bf3e0, have_lock=0) at 
malloc.c:4298
   () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_hash_table_remove_all () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: whoopsie assert failure: double free or corruption (fasttop)
  UpgradeStatus: Upgraded to groovy on 2020-10-06 (2 days ago)
  UserGroups: N/A
  separator:

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

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


[Touch-packages] [Bug 1892713] Re: whoopsie assert failure: free(): double free detected in tcache 2

2020-11-24 Thread Brian Murray
** Information type changed from Private to Public

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

Title:
  whoopsie assert failure: free(): double free detected in tcache 2

Status in whoopsie package in Ubuntu:
  Confirmed

Bug description:
  whoopsie failed to assert its dominance and threw a hissy fit crashing
  and taking the entire system with it.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: whoopsie 0.2.69ubuntu0.1
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  AssertionMessage: free(): double free detected in tcache 2
  CasperMD5CheckResult: skip
  CrashCounter: 1
  Date: Mon Aug 24 07:07:00 2020
  ExecutablePath: /usr/bin/whoopsie
  InstallationDate: Installed on 2020-05-23 (92 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcCmdline: /usr/bin/whoopsie -f
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  RelatedPackageVersions: apport-noui N/A
  Signal: 6
  SourcePackage: whoopsie
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7fa0d09bf285 
"%s\n") at ../sysdeps/posix/libc_fatal.c:155
   malloc_printerr (str=str@entry=0x7fa0d09c15d0 "free(): double free detected 
in tcache 2") at malloc.c:5347
   _int_free (av=0x7fa0d09f0b80 , p=0x55a170599750, have_lock=0) at 
malloc.c:4201
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: whoopsie assert failure: free(): double free detected in tcache 2
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  mtime.conffile..etc.apport.crashdb.conf: 2020-07-14T21:26:34.707473
  separator:

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

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


[Touch-packages] [Bug 1899100] Re: whoopsie assert failure: double free or corruption (fasttop)

2020-11-23 Thread Brian Murray
** Description changed:

- Apport popped up saying whoopsie had crashed (I assume during a previous
- crash report upload?)
+ [Impact]
+ whoopsie is crashing somewhat regularly. There are a couple of crashes in the 
Error Tracker which look similar:
  
- ProblemType: Crash
- DistroRelease: Ubuntu 20.10
+ https://errors.ubuntu.com/problem/5c1f68854a0f3bd5e263f1cd35e4dd944c9e90bd
+ https://errors.ubuntu.com/problem/5d7e641dc46229c08389420fdd74a7473d2dec98
+ 
+ As of yet (2020-11-22) neither crash is happening with whoopsie version
+ 0.2.73.
+ 
+ 
+ Apport popped up saying whoopsie had crashed (I assume during a previous 
crash report upload?)
+ 
+ ProblemType: CrashDistroRelease: Ubuntu 20.10
  Package: whoopsie 0.2.72
  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-0ubuntu49
  Architecture: amd64
  AssertionMessage: double free or corruption (fasttop)
  CasperMD5CheckResult: skip
  CrashCounter: 1
  Date: Fri Oct  9 08:08:56 2020
  ExecutablePath: /usr/bin/whoopsie
  InstallationDate: Installed on 2019-11-18 (325 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcCmdline: /usr/bin/whoopsie -f
  ProcEnviron:
-  LANG=en_AU.UTF-8
-  LANGUAGE=en_AU:en
-  PATH=(custom, no user)
+  LANG=en_AU.UTF-8
+  LANGUAGE=en_AU:en
+  PATH=(custom, no user)
  RelatedPackageVersions: apport-noui N/A
- Signal: 6
- SourcePackage: whoopsie
+ Signal: 6SourcePackage: whoopsie
  StacktraceTop:
-  __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f5982159128 
"%s\n") at ../sysdeps/posix/libc_fatal.c:155
-  malloc_printerr (str=str@entry=0x7f598215b5d8 "double free or corruption 
(fasttop)") at malloc.c:5389
-  _int_free (av=0x7f598218bba0 , p=0x55964a2bf3e0, have_lock=0) at 
malloc.c:4298
-  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
-  g_hash_table_remove_all () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
+  __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f5982159128 
"%s\n") at ../sysdeps/posix/libc_fatal.c:155
+  malloc_printerr (str=str@entry=0x7f598215b5d8 "double free or corruption 
(fasttop)") at malloc.c:5389
+  _int_free (av=0x7f598218bba0 , p=0x55964a2bf3e0, have_lock=0) at 
malloc.c:4298
+  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
+  g_hash_table_remove_all () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: whoopsie assert failure: double free or corruption (fasttop)
  UpgradeStatus: Upgraded to groovy on 2020-10-06 (2 days ago)
  UserGroups: N/A
  separator:

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

Title:
  whoopsie assert failure: double free or corruption (fasttop)

Status in whoopsie package in Ubuntu:
  Fix Released

Bug description:
  [Impact]
  whoopsie is crashing somewhat regularly. There are a couple of crashes in the 
Error Tracker which look similar:

  https://errors.ubuntu.com/problem/5c1f68854a0f3bd5e263f1cd35e4dd944c9e90bd
  https://errors.ubuntu.com/problem/5d7e641dc46229c08389420fdd74a7473d2dec98

  As of yet (2020-11-22) neither crash is happening with whoopsie
  version 0.2.73.

  
  Apport popped up saying whoopsie had crashed (I assume during a previous 
crash report upload?)

  ProblemType: CrashDistroRelease: Ubuntu 20.10
  Package: whoopsie 0.2.72
  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-0ubuntu49
  Architecture: amd64
  AssertionMessage: double free or corruption (fasttop)
  CasperMD5CheckResult: skip
  CrashCounter: 1
  Date: Fri Oct  9 08:08:56 2020
  ExecutablePath: /usr/bin/whoopsie
  InstallationDate: Installed on 2019-11-18 (325 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcCmdline: /usr/bin/whoopsie -f
  ProcEnviron:
   LANG=en_AU.UTF-8
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
  RelatedPackageVersions: apport-noui N/A
  Signal: 6SourcePackage: whoopsie
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f5982159128 
"%s\n") at ../sysdeps/posix/libc_fatal.c:155
   malloc_printerr (str=str@entry=0x7f598215b5d8 "double free or corruption 
(fasttop)") at malloc.c:5389
   _int_free (av=0x7f598218bba0 , p=0x55964a2bf3e0, have_lock=0) at 
malloc.c:4298
   () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_hash_table_remove_all () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: whoopsie assert failure: double free or corruption (fasttop)
  UpgradeStatus: Upgraded to groovy on 2020-10-06 (2 days ago)
  UserGroups: N/A
  separator:

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

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

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

2020-11-19 Thread Brian Murray
** Tags removed: champagne

-- 
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]: [WARN]Terminating ...
  Apr 08 06:09:19 Keschdeichel avahi-daemon[1204]: Got SIGTERM, quitting.
  Apr 08 06:09:19 Keschdeichel systemd[1]: udisks2.service: Unexpected error 
response from GetNameOwner(): Connection terminated
  Apr 08 06:09:19 Keschdeichel ModemManager[1308]:   Caught signal, 
shutting down...
  Apr 08 06:09:19 Keschdeichel systemd[1]: switcheroo-control.service: 
Unexpected error 

[Touch-packages] [Bug 1899262] Re: Broken dbus GetAll message to wpa supplicant interface properties

2020-11-17 Thread Brian Murray
Hello Michael, or anyone else affected,

Accepted wpa into bionic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/wpa/2:2.6-15ubuntu2.6
in a few hours, and then in the -proposed repository.

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

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

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

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

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

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

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

Title:
  Broken dbus GetAll message to wpa supplicant interface properties

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

Bug description:
  * Impact
  One of the distro patch is incorrect and create issues when trying to query 
dbus properties

  * Test Case

  $ sudo dbus-send --system --print-reply --dest=fi.w1.wpa_supplicant1
  /fi/w1/wpa_supplicant1/Interfaces/1
  org.freedesktop.DBus.Properties.GetAll
  string:fi.w1.wpa_supplicant1.Interface

  shouldn't error out

  (the /1 reflect the interface number and could be a different value,
  check with d-feet if needed)

  * Regression potential

  The fixes is in the dbus interface, check that communication with
  desktop clients (indicator, applet, settings) still works correctly,
  returning expected informations on the signal, etc

  -

  dbus-send is able to read the properties of interface using GetAll. Those 
information include interface name, status, encryption method, etc.
  The regression was introduced when someone try to have the Station attribute 
supported

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

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


[Touch-packages] [Bug 1870060] Re: systemd ProtectSystem/mount namespace makes apport fail (impact most of our default system services)

2020-11-17 Thread Brian Murray
I tested groovy again, but this time I installed apport and
python3-apport in one step instead of two and it passed without needing
to reboot.

The verification on Focal also passed with no rebooting required.

bdmurray@clean-focal-amd64:~$ apt list apport
Listing... Done
apport/focal-proposed,focal-proposed,now 2.20.11-0ubuntu27.13 all [installed]
N: There are 2 additional versions. Please use the '-a' switch to see them.
bdmurray@clean-focal-amd64:~$ sudo pkill -11 upowerd
bdmurray@clean-focal-amd64:~$ ls /var/crash/
_usr_lib_upower_upowerd.0.crash


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

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

Title:
  systemd ProtectSystem/mount namespace makes apport fail (impact most
  of our default system services)

Status in apport package in Ubuntu:
  Fix Released
Status in bluez package in Ubuntu:
  Invalid
Status in apport source package in Focal:
  Fix Committed
Status in bluez source package in Focal:
  Invalid
Status in apport source package in Groovy:
  Fix Committed
Status in bluez source package in Groovy:
  Invalid
Status in apport source package in Hirsute:
  Fix Released
Status in bluez source package in Hirsute:
  Invalid

Bug description:
  [Impact]
  apport is not creating crash files for multiple system services that use 
ProtectSystem since Ubuntu 20.04 LTS.

  [Test Case]
  On an Ubuntu desktop system perform the following step
  1) sudo pkill -11 upowerd

  With the current version of apport there will not be a crash file for
  upowerd in /var/crash/. With the version of apport in -proposed there
  will be a crash file for upowerd in /var/crash/.

  [Regression Potential]
  In the event that the changes to /usr/share/apport/apport are bad then apport 
itself would crash thereby preventing us from getting any crash reports. So in 
addition to killing upowerd we should also test a regular application like 
xeyes.

  [Original Description]
  bluetoothd never leaves dumps/crash files when it crashes

  And it seems this is true for everyone. Only supplementary binaries' crash 
reports are shown:
  https://errors.ubuntu.com/?release=Ubuntu%2020.04=bluez=year

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

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


[Touch-packages] [Bug 1870060] Re: systemd ProtectSystem/mount namespace makes apport fail (impact most of our default system services)

2020-11-17 Thread Brian Murray
I had to reboot for the verification to pass, but it did.

bdmurray@clean-groovy-amd64:~$ apt list apport
Listing... Done
apport/groovy-proposed,groovy-proposed,now 2.20.11-0ubuntu50.2 all 
[installed,automatic]
N: There are 2 additional versions. Please use the '-a' switch to see them.
bdmurray@clean-groovy-amd64:~$ sudo pkill -11 upowerd
bdmurray@clean-groovy-amd64:~$ ls /var/crash/
_usr_libexec_upowerd.0.crash

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

Title:
  systemd ProtectSystem/mount namespace makes apport fail (impact most
  of our default system services)

Status in apport package in Ubuntu:
  Fix Released
Status in bluez package in Ubuntu:
  Invalid
Status in apport source package in Focal:
  Fix Committed
Status in bluez source package in Focal:
  Invalid
Status in apport source package in Groovy:
  Fix Committed
Status in bluez source package in Groovy:
  Invalid
Status in apport source package in Hirsute:
  Fix Released
Status in bluez source package in Hirsute:
  Invalid

Bug description:
  [Impact]
  apport is not creating crash files for multiple system services that use 
ProtectSystem since Ubuntu 20.04 LTS.

  [Test Case]
  On an Ubuntu desktop system perform the following step
  1) sudo pkill -11 upowerd

  With the current version of apport there will not be a crash file for
  upowerd in /var/crash/. With the version of apport in -proposed there
  will be a crash file for upowerd in /var/crash/.

  [Regression Potential]
  In the event that the changes to /usr/share/apport/apport are bad then apport 
itself would crash thereby preventing us from getting any crash reports. So in 
addition to killing upowerd we should also test a regular application like 
xeyes.

  [Original Description]
  bluetoothd never leaves dumps/crash files when it crashes

  And it seems this is true for everyone. Only supplementary binaries' crash 
reports are shown:
  https://errors.ubuntu.com/?release=Ubuntu%2020.04=bluez=year

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

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


[Touch-packages] [Bug 1902710] Update Released

2020-11-17 Thread Brian Murray
The verification of the Stable Release Update for software-properties
has completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  [SRU] Enable support for Wallaby Cloud Archive

Status in software-properties package in Ubuntu:
  Fix Committed
Status in software-properties source package in Focal:
  Fix Released
Status in software-properties source package in Hirsute:
  Fix Committed

Bug description:
  Please add support for:

 cloud-archive:wallaby
 cloud-archive:wallaby-proposed

  This will also need to be SRU'd back to focal.

  [Impact]
  End users have to manually enable the wallaby cloud archive pockets.

  [Test case]
  sudo add-apt-repository cloud-archive:wallaby
  sudo add-apt-repository cloud-archive:wallaby-proposed

  [Regression potential]
  Limited - just a data item addition

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

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


[Touch-packages] [Bug 1903048] Re: [SRU] Bluetooth won't activate on the pi 400

2020-11-17 Thread Brian Murray
Hello Dave, or anyone else affected,

Accepted bluez into groovy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/bluez/5.55-0ubuntu1.1
in a few hours, and then in the -proposed repository.

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

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

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

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

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

** Tags added: verification-needed verification-needed-groovy

** Description changed:

  [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
+ * Enable the -proposed repository for the release (groovy)
  * 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 
+ * 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.

-- 
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 Groovy:
  Fix Committed
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
  * Enable the -proposed repository for the release (groovy)
  * 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 

[Touch-packages] [Bug 1904470] Re: 100Hz monitor fails to wake after lock

2020-11-17 Thread Brian Murray
** Package changed: ubuntu => xorg (Ubuntu)

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

Title:
  100Hz monitor fails to wake after lock

Status in xorg package in Ubuntu:
  New

Bug description:
  When set to 100Hz the monitor will work without issues until the
  machine is locked. When i want to unlock it the scrren does not wake
  up. The only way to wake up the screen is to unplug the HDMI cable
  from the GPU and plug it in again.

  This issue does not happen on 60Hz.

  This issue is present on both 20.04.1 LTS and 20.10.

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

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


[Touch-packages] [Bug 1891479] [pycurl/focal] verification still needed

2020-11-14 Thread Brian Murray
The fix for this bug has been awaiting testing feedback in the -proposed
repository for focal for more than 90 days.  Please test this fix and
update the bug appropriately with the results.  In the event that the
fix for this bug is still not verified 15 days from now, the package
will be removed from the -proposed repository.

** Tags added: removal-candidate

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

Title:
  pycurl ftbfs in focal (wait-deps)

Status in pycurl package in Ubuntu:
  Confirmed
Status in pycurl source package in Focal:
  Fix Committed

Bug description:
  [SRU Justification]
  This package is unbuildable due to unsatisfiable build-dependencies, as seen 
in a focal test rebuild:
  
https://launchpad.net/ubuntu/+archive/test-rebuild-20200810-focal/+build/19799602

  Missing build dependencies: python-sphinx

  This makes the package unsupportable in the event a security update
  needs to be applied.

  [Test case]
  1. let the package attempt to build in focal
  2. check if it succeeds.

  [Regression potential]
  Because the missing build-dependency is python-sphinx, which is only used for 
building the package documentation, the risk of regression is confined to a 
misbuild of the documentation.  Regardless, this package will be held in 
-proposed because the runtime impact of a FTBFS is non-existent.

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

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


[Touch-packages] [Bug 1818918] Re: gdb doesn't search in debug-file-directory for .gnu_debugaltlink

2020-11-13 Thread Brian Murray
This is still an issue with hirsute afaict.

(hirsute-amd64)root@impulse:/tmp# gdb --ex 'set debug-file-directory 
/tmp/dbgsym/usr/lib/debug:/usr/lib/debug' --ex 'file /bin/cat' --ex 'cor
e-file /tmp/cat.core'
GNU gdb (Ubuntu 10.1-0ubuntu1) 10.1
Copyright (C) 2020 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 "x86_64-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 /bin/cat...
Reading symbols from 
/tmp/dbgsym/usr/lib/debug/.build-id/bc/06d3bee37b8c7e67b31cb2689cb351102ae73b.debug...
could not find '.gnu_debugaltlink' file for 
/tmp/dbgsym/usr/lib/debug/.build-id/bc/06d3bee37b8c7e67b31cb2689cb351102ae73b.debug
(No debugging symbols found in 
/tmp/dbgsym/usr/lib/debug/.build-id/bc/06d3bee37b8c7e67b31cb2689cb351102ae73b.debug)
[New LWP 1146067]
Core was generated by `/bin/cat'.
Program terminated with signal SIGTSTP, Stopped (user).
#0  0x77edca92 in read () from /lib/x86_64-linux-gnu/libc.so.6

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

Title:
  gdb doesn't search in debug-file-directory for .gnu_debugaltlink

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  New
Status in gdb package in Ubuntu:
  Confirmed

Bug description:
  As far as I can tell gdb version 8.2.90 isn't searching the debug-
  file-directory, which I set, for the '.gnu_debugaltlink' which is in
  the debug symbols. Here's the error I'm seeing:

  Type "apropos word" to search for commands related to "word".
  Reading symbols from /srv/vms/apport-sandbox-dir/Ubuntu 
19.04/amd64/report-sandbox//usr/bin/gnome-calculator...
  Reading symbols from /srv/vms/apport-sandbox-dir/Ubuntu 
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug...
  could not find '.gnu_debugaltlink' file for 
/srv/vms/apport-sandbox-dir/Ubuntu 
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug
  (No debugging symbols found in /srv/vms/apport-sandbox-dir/Ubuntu 
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug)

  Here's part of an strace of what's going on behind the scenes:

  lstat("/srv/vms/apport-sandbox-dir/Ubuntu 
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug",
 {st_mode=S_IFREG|0644, st_size=839744, ...}) = 0 
  openat(AT_FDCWD, 
"/usr/lib/debug/.dwz/x86_64-linux-gnu/gnome-calculator.debug", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)

  This is the only time "/usr/lib/debug" is searched, generally
  "/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-
  sandbox/usr/lib/debug/" is used. I'll attach the full strace though.

  For completeness here's the gdb command I'm using:

  Calling gdb command: '/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64
  /report-sandbox/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2' '/srv/vms
  /apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/usr/bin/gdb'
  --ex 'set debug-file-directory /srv/vms/apport-sandbox-dir/Ubuntu
  19.04/amd64/report-sandbox/usr/lib/debug' --ex 'set solib-absolute-
  prefix /srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox'
  --ex 'add-auto-load-safe-path /srv/vms/apport-sandbox-dir/Ubuntu
  19.04/amd64/report-sandbox' --ex 'set solib-search-path /srv/vms
  /apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/lib/x86_64
  -linux-gnu' --ex 'set data-directory /srv/vms/apport-sandbox-
  dir/Ubuntu 19.04/amd64/report-sandbox/usr/share/gdb' --ex 'file
  "/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-
  sandbox//usr/bin/gnome-calculator"' --ex 'core-file
  /tmp/apport_core_1b6dn6np'

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

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


[Touch-packages] [Bug 1818918] Re: gdb doesn't search in debug-file-directory for .gnu_debugaltlink

2020-11-13 Thread Brian Murray
Ah, thanks for pointing that out but there is still an issue with the
test case in comment #12 as the .gnu_debugaltlink file is still not
loaded.

Reading symbols from /bin/cat...
Reading symbols from 
/tmp/dbgsym/usr/lib/debug/.build-id/fb/a7cee6aca864b8f79dfaa8a267855333b445c1.debug...
could not find '.gnu_debugaltlink' file for 
/tmp/dbgsym/usr/lib/debug/.build-id/fb/a7cee6aca864b8f79dfaa8a267855333b445c1.debug
(No debugging symbols found in 
/tmp/dbgsym/usr/lib/debug/.build-id/fb/a7cee6aca864b8f79dfaa8a267855333b445c1.debug)
[New LWP 302900]
Core was generated by `/bin/cat'.
Program terminated with signal SIGTSTP, Stopped (user).

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

Title:
  gdb doesn't search in debug-file-directory for .gnu_debugaltlink

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  New
Status in gdb package in Ubuntu:
  Confirmed

Bug description:
  As far as I can tell gdb version 8.2.90 isn't searching the debug-
  file-directory, which I set, for the '.gnu_debugaltlink' which is in
  the debug symbols. Here's the error I'm seeing:

  Type "apropos word" to search for commands related to "word".
  Reading symbols from /srv/vms/apport-sandbox-dir/Ubuntu 
19.04/amd64/report-sandbox//usr/bin/gnome-calculator...
  Reading symbols from /srv/vms/apport-sandbox-dir/Ubuntu 
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug...
  could not find '.gnu_debugaltlink' file for 
/srv/vms/apport-sandbox-dir/Ubuntu 
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug
  (No debugging symbols found in /srv/vms/apport-sandbox-dir/Ubuntu 
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug)

  Here's part of an strace of what's going on behind the scenes:

  lstat("/srv/vms/apport-sandbox-dir/Ubuntu 
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug",
 {st_mode=S_IFREG|0644, st_size=839744, ...}) = 0 
  openat(AT_FDCWD, 
"/usr/lib/debug/.dwz/x86_64-linux-gnu/gnome-calculator.debug", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)

  This is the only time "/usr/lib/debug" is searched, generally
  "/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-
  sandbox/usr/lib/debug/" is used. I'll attach the full strace though.

  For completeness here's the gdb command I'm using:

  Calling gdb command: '/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64
  /report-sandbox/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2' '/srv/vms
  /apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/usr/bin/gdb'
  --ex 'set debug-file-directory /srv/vms/apport-sandbox-dir/Ubuntu
  19.04/amd64/report-sandbox/usr/lib/debug' --ex 'set solib-absolute-
  prefix /srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox'
  --ex 'add-auto-load-safe-path /srv/vms/apport-sandbox-dir/Ubuntu
  19.04/amd64/report-sandbox' --ex 'set solib-search-path /srv/vms
  /apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/lib/x86_64
  -linux-gnu' --ex 'set data-directory /srv/vms/apport-sandbox-
  dir/Ubuntu 19.04/amd64/report-sandbox/usr/share/gdb' --ex 'file
  "/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-
  sandbox//usr/bin/gnome-calculator"' --ex 'core-file
  /tmp/apport_core_1b6dn6np'

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

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


[Touch-packages] [Bug 1818918] Re: gdb doesn't search in debug-file-directory for .gnu_debugaltlink

2020-11-12 Thread Brian Murray
This is also true with gdb 10.1 from hirsute-proposed.

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

Title:
  gdb doesn't search in debug-file-directory for .gnu_debugaltlink

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  New
Status in gdb package in Ubuntu:
  Confirmed

Bug description:
  As far as I can tell gdb version 8.2.90 isn't searching the debug-
  file-directory, which I set, for the '.gnu_debugaltlink' which is in
  the debug symbols. Here's the error I'm seeing:

  Type "apropos word" to search for commands related to "word".
  Reading symbols from /srv/vms/apport-sandbox-dir/Ubuntu 
19.04/amd64/report-sandbox//usr/bin/gnome-calculator...
  Reading symbols from /srv/vms/apport-sandbox-dir/Ubuntu 
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug...
  could not find '.gnu_debugaltlink' file for 
/srv/vms/apport-sandbox-dir/Ubuntu 
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug
  (No debugging symbols found in /srv/vms/apport-sandbox-dir/Ubuntu 
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug)

  Here's part of an strace of what's going on behind the scenes:

  lstat("/srv/vms/apport-sandbox-dir/Ubuntu 
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug",
 {st_mode=S_IFREG|0644, st_size=839744, ...}) = 0 
  openat(AT_FDCWD, 
"/usr/lib/debug/.dwz/x86_64-linux-gnu/gnome-calculator.debug", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)

  This is the only time "/usr/lib/debug" is searched, generally
  "/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-
  sandbox/usr/lib/debug/" is used. I'll attach the full strace though.

  For completeness here's the gdb command I'm using:

  Calling gdb command: '/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64
  /report-sandbox/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2' '/srv/vms
  /apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/usr/bin/gdb'
  --ex 'set debug-file-directory /srv/vms/apport-sandbox-dir/Ubuntu
  19.04/amd64/report-sandbox/usr/lib/debug' --ex 'set solib-absolute-
  prefix /srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox'
  --ex 'add-auto-load-safe-path /srv/vms/apport-sandbox-dir/Ubuntu
  19.04/amd64/report-sandbox' --ex 'set solib-search-path /srv/vms
  /apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/lib/x86_64
  -linux-gnu' --ex 'set data-directory /srv/vms/apport-sandbox-
  dir/Ubuntu 19.04/amd64/report-sandbox/usr/share/gdb' --ex 'file
  "/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-
  sandbox//usr/bin/gnome-calculator"' --ex 'core-file
  /tmp/apport_core_1b6dn6np'

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

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


[Touch-packages] [Bug 1903351] Re: ignore_eacces and ignore_erofs patches don't work properly

2020-11-12 Thread Brian Murray
** Tags removed: rls-gg-incoming

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

Title:
  ignore_eacces and ignore_erofs patches don't work properly

Status in procps package in Ubuntu:
  Confirmed

Bug description:
  The patches used to ignore errors in containers no longer work as of
  3.3.16 due to upstream commit https://gitlab.com/procps-
  ng/procps/-/commit/7af88da373bb4d515a98ec2f0f5d56c63904f932

  The ignore_eacces patch was fuzzed and gets applied to ReadSetting, not 
WriteSetting
  Both patches ignore the change that rc is no longer propagated up and instead 
everything is trapped by:

  if (!ignore_failure && errno != ENOENT)
  rc = -1;

  
  Versions affected: focal+

  
  root@bfee89058713:/tmp# cat /etc/os-release 
  NAME="Ubuntu"
  VERSION="20.10 (Groovy Gorilla)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 20.10"
  VERSION_ID="20.10"
  HOME_URL="https://www.ubuntu.com/;
  SUPPORT_URL="https://help.ubuntu.com/;
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
  VERSION_CODENAME=groovy
  UBUNTU_CODENAME=groovy

  
  root@bfee89058713:/# dpkg -l procps
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name   Version   Architecture Description
  
+++-==-=--=
  ii  procps 2:3.3.16-5ubuntu2 amd64/proc file system utilities

  
  root@bfee89058713:/# echo "kernel.shmmax = 17179869184" > shmmax.conf
  root@bfee89058713:/# sysctl -e -p shmmax.conf; echo $?
  sysctl: setting key "kernel.shmmax": Read-only file system
  255
  root@bfee89058713:/# echo "-kernel.shmmax = 17179869184" > shmmax.conf
  root@bfee89058713:/# sysctl -e -p shmmax.conf; echo $?
  sysctl: setting key "kernel.shmmax": Read-only file system
  0

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

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


[Touch-packages] [Bug 1902760] Re: Please merge linker bugfix into Ubuntu 20.04 LTS

2020-11-12 Thread Brian Murray
>From #ubuntu-meeting on 2020-11-12

08:26 < doko> that binutils fix is not yet on the 2.34 
  branch


** Tags removed: rls-ff-incoming

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

Title:
  Please merge linker bugfix into Ubuntu 20.04 LTS

Status in binutils:
  Fix Released
Status in intel:
  New
Status in binutils package in Ubuntu:
  New

Bug description:
  Binutils bug https://sourceware.org/bugzilla/show_bug.cgi?id=26262
  fixes a problem that Intel Fortran is running into when using the -ipo
  option to request link time optimization. Please merge the fix into
  Ubuntu 20.04 LTS

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

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


[Touch-packages] [Bug 1903567] Re: /usr/share/apport/apport:AttributeError:/usr/share/apport/apport@447:parse_arguments:print_usage:_print_message

2020-11-12 Thread Brian Murray
** Tags removed: rls-hh-incoming

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

Title:
  
/usr/share/apport/apport:AttributeError:/usr/share/apport/apport@447:parse_arguments:print_usage:_print_message

Status in apport package in Ubuntu:
  Confirmed
Status in apport source package in Xenial:
  Confirmed
Status in apport source package in Bionic:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.20.1-0ubuntu2.26, the problem page at 
https://errors.ubuntu.com/problem/c39b4b2ced24aa71d85b0995a56bd3813a39 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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


[Touch-packages] [Bug 1899100] Re: whoopsie assert failure: double free or corruption (fasttop)

2020-11-10 Thread Brian Murray
I've uploaded this for Hirsute - thanks!

** Tags added: fr-914

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

Title:
  whoopsie assert failure: double free or corruption (fasttop)

Status in whoopsie package in Ubuntu:
  Confirmed

Bug description:
  Apport popped up saying whoopsie had crashed (I assume during a
  previous crash report upload?)

  ProblemType: Crash
  DistroRelease: Ubuntu 20.10
  Package: whoopsie 0.2.72
  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-0ubuntu49
  Architecture: amd64
  AssertionMessage: double free or corruption (fasttop)
  CasperMD5CheckResult: skip
  CrashCounter: 1
  Date: Fri Oct  9 08:08:56 2020
  ExecutablePath: /usr/bin/whoopsie
  InstallationDate: Installed on 2019-11-18 (325 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcCmdline: /usr/bin/whoopsie -f
  ProcEnviron:
   LANG=en_AU.UTF-8
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
  RelatedPackageVersions: apport-noui N/A
  Signal: 6
  SourcePackage: whoopsie
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f5982159128 
"%s\n") at ../sysdeps/posix/libc_fatal.c:155
   malloc_printerr (str=str@entry=0x7f598215b5d8 "double free or corruption 
(fasttop)") at malloc.c:5389
   _int_free (av=0x7f598218bba0 , p=0x55964a2bf3e0, have_lock=0) at 
malloc.c:4298
   () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_hash_table_remove_all () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: whoopsie assert failure: double free or corruption (fasttop)
  UpgradeStatus: Upgraded to groovy on 2020-10-06 (2 days ago)
  UserGroups: N/A
  separator:

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

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


[Touch-packages] [Bug 1903351] Re: ignore_eacces and ignore_erofs patches don't work properly

2020-11-10 Thread Brian Murray
** Tags added: rls-gg-incoming

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

Title:
  ignore_eacces and ignore_erofs patches don't work properly

Status in procps package in Ubuntu:
  Confirmed

Bug description:
  The patches used to ignore errors in containers no longer work as of
  3.3.16 due to upstream commit https://gitlab.com/procps-
  ng/procps/-/commit/7af88da373bb4d515a98ec2f0f5d56c63904f932

  The ignore_eacces patch was fuzzed and gets applied to ReadSetting, not 
WriteSetting
  Both patches ignore the change that rc is no longer propagated up and instead 
everything is trapped by:

  if (!ignore_failure && errno != ENOENT)
  rc = -1;

  
  Versions affected: focal+

  
  root@bfee89058713:/tmp# cat /etc/os-release 
  NAME="Ubuntu"
  VERSION="20.10 (Groovy Gorilla)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 20.10"
  VERSION_ID="20.10"
  HOME_URL="https://www.ubuntu.com/;
  SUPPORT_URL="https://help.ubuntu.com/;
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
  VERSION_CODENAME=groovy
  UBUNTU_CODENAME=groovy

  
  root@bfee89058713:/# dpkg -l procps
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name   Version   Architecture Description
  
+++-==-=--=
  ii  procps 2:3.3.16-5ubuntu2 amd64/proc file system utilities

  
  root@bfee89058713:/# echo "kernel.shmmax = 17179869184" > shmmax.conf
  root@bfee89058713:/# sysctl -e -p shmmax.conf; echo $?
  sysctl: setting key "kernel.shmmax": Read-only file system
  255
  root@bfee89058713:/# echo "-kernel.shmmax = 17179869184" > shmmax.conf
  root@bfee89058713:/# sysctl -e -p shmmax.conf; echo $?
  sysctl: setting key "kernel.shmmax": Read-only file system
  0

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

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


[Touch-packages] [Bug 1903567] Re: /usr/share/apport/apport:AttributeError:/usr/share/apport/apport@447:parse_arguments:print_usage:_print_message

2020-11-09 Thread Brian Murray
** Also affects: apport (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: apport (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

** Changed in: apport (Ubuntu Xenial)
   Status: New => Confirmed

** Changed in: apport (Ubuntu Bionic)
   Status: New => Confirmed

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

Title:
  
/usr/share/apport/apport:AttributeError:/usr/share/apport/apport@447:parse_arguments:print_usage:_print_message

Status in apport package in Ubuntu:
  Confirmed
Status in apport source package in Xenial:
  Confirmed
Status in apport source package in Bionic:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.20.1-0ubuntu2.26, the problem page at 
https://errors.ubuntu.com/problem/c39b4b2ced24aa71d85b0995a56bd3813a39 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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


[Touch-packages] [Bug 1903567] Re: /usr/share/apport/apport:AttributeError:/usr/share/apport/apport@447:parse_arguments:print_usage:_print_message

2020-11-09 Thread Brian Murray
** Tags added: rls-hh-incoming

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

Title:
  
/usr/share/apport/apport:AttributeError:/usr/share/apport/apport@447:parse_arguments:print_usage:_print_message

Status in apport package in Ubuntu:
  Confirmed
Status in apport source package in Xenial:
  New
Status in apport source package in Bionic:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.20.1-0ubuntu2.26, the problem page at 
https://errors.ubuntu.com/problem/c39b4b2ced24aa71d85b0995a56bd3813a39 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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


[Touch-packages] [Bug 1903567] Re: /usr/share/apport/apport:AttributeError:/usr/share/apport/apport@447:parse_arguments:print_usage:_print_message

2020-11-09 Thread Brian Murray
Traceback (most recent call last):
  File "/usr/share/apport/apport", line 447, in 
options = parse_arguments()
  File "/usr/share/apport/apport", line 393, in parse_arguments
parser.print_usage()
  File "/usr/lib/python3.5/argparse.py", line 2362, in print_usage
self._print_message(self.format_usage(), file)
  File "/usr/lib/python3.5/argparse.py", line 2373, in _print_message
file.write(message)
AttributeError: 'NoneType' object has no attribute 'write'

This can happen if the path to the executable has a space in it e.g.:

bdmurray@clean-xenial-amd64:~$ /usr/bin/python3 /usr/share/apport/apport 14055 
11 0 1 14055 /usr/lib/plexmediaserver/Plex Media Server
usage: apport [-h] [-p PID] [-s SIGNAL_NUMBER] [-c CORE_ULIMIT] [-d DUMP_MODE]
  [-P [GLOBAL_PID]] [-E [EXECUTABLE_PATH]]

Somehow apport needs to be modified to handle arguments where the
executable path has a space in the name.

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

Title:
  
/usr/share/apport/apport:AttributeError:/usr/share/apport/apport@447:parse_arguments:print_usage:_print_message

Status in apport package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.20.1-0ubuntu2.26, the problem page at 
https://errors.ubuntu.com/problem/c39b4b2ced24aa71d85b0995a56bd3813a39 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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


[Touch-packages] [Bug 1818918] Re: gdb doesn't search in debug-file-directory for .gnu_debugaltlink

2020-11-06 Thread Brian Murray
Here's the full strace for the /bin/cat test case.

** Attachment added: "gdb-bin-cat.trace"
   
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1818918/+attachment/5431989/+files/gdb-bin-cat.trace

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

Title:
  gdb doesn't search in debug-file-directory for .gnu_debugaltlink

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  New
Status in gdb package in Ubuntu:
  Confirmed

Bug description:
  As far as I can tell gdb version 8.2.90 isn't searching the debug-
  file-directory, which I set, for the '.gnu_debugaltlink' which is in
  the debug symbols. Here's the error I'm seeing:

  Type "apropos word" to search for commands related to "word".
  Reading symbols from /srv/vms/apport-sandbox-dir/Ubuntu 
19.04/amd64/report-sandbox//usr/bin/gnome-calculator...
  Reading symbols from /srv/vms/apport-sandbox-dir/Ubuntu 
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug...
  could not find '.gnu_debugaltlink' file for 
/srv/vms/apport-sandbox-dir/Ubuntu 
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug
  (No debugging symbols found in /srv/vms/apport-sandbox-dir/Ubuntu 
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug)

  Here's part of an strace of what's going on behind the scenes:

  lstat("/srv/vms/apport-sandbox-dir/Ubuntu 
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug",
 {st_mode=S_IFREG|0644, st_size=839744, ...}) = 0 
  openat(AT_FDCWD, 
"/usr/lib/debug/.dwz/x86_64-linux-gnu/gnome-calculator.debug", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)

  This is the only time "/usr/lib/debug" is searched, generally
  "/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-
  sandbox/usr/lib/debug/" is used. I'll attach the full strace though.

  For completeness here's the gdb command I'm using:

  Calling gdb command: '/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64
  /report-sandbox/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2' '/srv/vms
  /apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/usr/bin/gdb'
  --ex 'set debug-file-directory /srv/vms/apport-sandbox-dir/Ubuntu
  19.04/amd64/report-sandbox/usr/lib/debug' --ex 'set solib-absolute-
  prefix /srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox'
  --ex 'add-auto-load-safe-path /srv/vms/apport-sandbox-dir/Ubuntu
  19.04/amd64/report-sandbox' --ex 'set solib-search-path /srv/vms
  /apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/lib/x86_64
  -linux-gnu' --ex 'set data-directory /srv/vms/apport-sandbox-
  dir/Ubuntu 19.04/amd64/report-sandbox/usr/share/gdb' --ex 'file
  "/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-
  sandbox//usr/bin/gnome-calculator"' --ex 'core-file
  /tmp/apport_core_1b6dn6np'

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

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


[Touch-packages] [Bug 1818918] Re: gdb doesn't search in debug-file-directory for .gnu_debugaltlink

2020-11-06 Thread Brian Murray
Oh and using either of '/tmp/dbgsym' or /tmp/dbgsym/usr/lib/debug' for
the debug-file-directory works.

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

Title:
  gdb doesn't search in debug-file-directory for .gnu_debugaltlink

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  New
Status in gdb package in Ubuntu:
  Confirmed

Bug description:
  As far as I can tell gdb version 8.2.90 isn't searching the debug-
  file-directory, which I set, for the '.gnu_debugaltlink' which is in
  the debug symbols. Here's the error I'm seeing:

  Type "apropos word" to search for commands related to "word".
  Reading symbols from /srv/vms/apport-sandbox-dir/Ubuntu 
19.04/amd64/report-sandbox//usr/bin/gnome-calculator...
  Reading symbols from /srv/vms/apport-sandbox-dir/Ubuntu 
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug...
  could not find '.gnu_debugaltlink' file for 
/srv/vms/apport-sandbox-dir/Ubuntu 
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug
  (No debugging symbols found in /srv/vms/apport-sandbox-dir/Ubuntu 
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug)

  Here's part of an strace of what's going on behind the scenes:

  lstat("/srv/vms/apport-sandbox-dir/Ubuntu 
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug",
 {st_mode=S_IFREG|0644, st_size=839744, ...}) = 0 
  openat(AT_FDCWD, 
"/usr/lib/debug/.dwz/x86_64-linux-gnu/gnome-calculator.debug", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)

  This is the only time "/usr/lib/debug" is searched, generally
  "/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-
  sandbox/usr/lib/debug/" is used. I'll attach the full strace though.

  For completeness here's the gdb command I'm using:

  Calling gdb command: '/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64
  /report-sandbox/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2' '/srv/vms
  /apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/usr/bin/gdb'
  --ex 'set debug-file-directory /srv/vms/apport-sandbox-dir/Ubuntu
  19.04/amd64/report-sandbox/usr/lib/debug' --ex 'set solib-absolute-
  prefix /srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox'
  --ex 'add-auto-load-safe-path /srv/vms/apport-sandbox-dir/Ubuntu
  19.04/amd64/report-sandbox' --ex 'set solib-search-path /srv/vms
  /apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/lib/x86_64
  -linux-gnu' --ex 'set data-directory /srv/vms/apport-sandbox-
  dir/Ubuntu 19.04/amd64/report-sandbox/usr/share/gdb' --ex 'file
  "/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-
  sandbox//usr/bin/gnome-calculator"' --ex 'core-file
  /tmp/apport_core_1b6dn6np'

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

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


[Touch-packages] [Bug 1818918] Re: gdb doesn't search in debug-file-directory for .gnu_debugaltlink

2020-11-06 Thread Brian Murray
I've come up with a simpler test case on an Ubuntu 20.10 system which
follows:

1) Execute 'gdb --args cat'
2) in gdb type 'run'
3) press Ctrl-Z
4) in gdb type 'generate-core-file /tmp/cat.core'
5) download the dbgsym for coreutils
6) Extract them 'dbg-deb -x coreutils-dbgsym_8.32-3ubuntu1_amd64.ddeb 
/tmp/dbgsym'
7) Execute "gdb --ex 'file /bin/cat' --ex 'core-file /tmp/cat.core' --ex 'set 
debug-file-directory /tmp/dbgsym/usr/lib/debug'"

In gdb you'll see the following error message:

Reading symbols from /bin/cat...
(No debugging symbols found in /bin/cat)

Running "objdump -g /bin/cat" we can see the location for the separate
debug info:

Contents of the .gnu_debugaltlink section (loaded from /bin/cat):

  Separate debug info file: /usr/lib/debug/.dwz/x86_64-linux-gnu/coreutils.debug
  Build-ID (0x14 bytes):
 cb 5b e4 8a 6d b2 52 6e 9c 80 8d 64 ec 4b 1f b7 7f 0c ca 9e

Contents of the .gnu_debuglink section (loaded from /bin/cat):

  Separate debug info file: a7cee6aca864b8f79dfaa8a267855333b445c1.debug
  CRC value: 0x5e28a31d

The separate debug info file exists in /tmp/dbgsym:

[ 11:07AM 10857 ]  [ bdmurray@impulse:/tmp/dbgsym ]
 $ find . -name a7cee\*.debug
./usr/lib/debug/.build-id/fb/a7cee6aca864b8f79dfaa8a267855333b445c1.debug

However despite setting debug-file-directory an strace reveals that
/tmp/dbgsym is not searched:

 $ grep a7cee /tmp/gdb-bin-cat.trace
access("/usr/lib/debug/.build-id/fb/a7cee6aca864b8f79dfaa8a267855333b445c1.debug",
 F_OK) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/bin/a7cee6aca864b8f79dfaa8a267855333b445c1.debug", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/bin/.debug/a7cee6aca864b8f79dfaa8a267855333b445c1.debug", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, 
"/usr/lib/debug//bin/a7cee6aca864b8f79dfaa8a267855333b445c1.debug", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)

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

Title:
  gdb doesn't search in debug-file-directory for .gnu_debugaltlink

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  New
Status in gdb package in Ubuntu:
  Confirmed

Bug description:
  As far as I can tell gdb version 8.2.90 isn't searching the debug-
  file-directory, which I set, for the '.gnu_debugaltlink' which is in
  the debug symbols. Here's the error I'm seeing:

  Type "apropos word" to search for commands related to "word".
  Reading symbols from /srv/vms/apport-sandbox-dir/Ubuntu 
19.04/amd64/report-sandbox//usr/bin/gnome-calculator...
  Reading symbols from /srv/vms/apport-sandbox-dir/Ubuntu 
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug...
  could not find '.gnu_debugaltlink' file for 
/srv/vms/apport-sandbox-dir/Ubuntu 
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug
  (No debugging symbols found in /srv/vms/apport-sandbox-dir/Ubuntu 
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug)

  Here's part of an strace of what's going on behind the scenes:

  lstat("/srv/vms/apport-sandbox-dir/Ubuntu 
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug",
 {st_mode=S_IFREG|0644, st_size=839744, ...}) = 0 
  openat(AT_FDCWD, 
"/usr/lib/debug/.dwz/x86_64-linux-gnu/gnome-calculator.debug", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)

  This is the only time "/usr/lib/debug" is searched, generally
  "/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-
  sandbox/usr/lib/debug/" is used. I'll attach the full strace though.

  For completeness here's the gdb command I'm using:

  Calling gdb command: '/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64
  /report-sandbox/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2' '/srv/vms
  /apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/usr/bin/gdb'
  --ex 'set debug-file-directory /srv/vms/apport-sandbox-dir/Ubuntu
  19.04/amd64/report-sandbox/usr/lib/debug' --ex 'set solib-absolute-
  prefix /srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox'
  --ex 'add-auto-load-safe-path /srv/vms/apport-sandbox-dir/Ubuntu
  19.04/amd64/report-sandbox' --ex 'set solib-search-path /srv/vms
  /apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/lib/x86_64
  -linux-gnu' --ex 'set data-directory /srv/vms/apport-sandbox-
  dir/Ubuntu 19.04/amd64/report-sandbox/usr/share/gdb' --ex 'file
  "/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-
  sandbox//usr/bin/gnome-calculator"' --ex 'core-file
  /tmp/apport_core_1b6dn6np'

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

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

[Touch-packages] [Bug 1787480] Re: bugpattern checking not working for a ubiquity bug report

2020-11-06 Thread Brian Murray
** Changed in: apport (Ubuntu)
   Importance: High => Low

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

Title:
  bugpattern checking not working for a ubiquity bug report

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  Phillip Susi wrote a bug pattern for ubiquity / grub-installer at
  https://bazaar.launchpad.net/~ubuntu-bugcontrol/apport/ubuntu-
  bugpatterns/revision/584. While the bug pattern works, tested with
  test-local and search-bugs from that branch new bug reports are still
  appearing in Launchpad.

  I confirmed that the pattern exists in https://people.canonical.com
  /~ubuntu-archive/bugpatterns/bugpatterns.xml and that using that url
  instead of a local file in test-local works. So it seems to be
  something with apport's ui.py or report.py when the bug report is
  being filed.

  The best way to test this would be a Live CD where the bug will
  actually occur.

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

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


[Touch-packages] [Bug 1853383] Re: autopkgtest regression in test_add_proc_info

2020-11-05 Thread Brian Murray
The tests are passing now for Xenial and Bionic.

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

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

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

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

Title:
  autopkgtest regression in test_add_proc_info

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Xenial:
  Fix Released
Status in apport source package in Bionic:
  Fix Released
Status in apport source package in Disco:
  Won't Fix
Status in apport source package in Eoan:
  Won't Fix

Bug description:
  The security uploads for apport (2.20.11-0ubuntu8.2 for eoan,
  2.20.10-0ubuntu27.2 for disco, and 2.20.9-0ubuntu7.8 for bionic - and
  maybe those for older releases as well) have caused the
  test_add_proc_info test to start failing[1]. The pattern changed after
  the subsequent uploads to fix a regression, but it still fails[2].

  [1]
  ==
  ERROR: test_add_proc_info (__main__.T)
  add_proc_info().
  --
  Traceback (most recent call last):
    File "./test_report.py", line 100, in test_add_proc_info
  pr.add_proc_info(extraenv=['PWD'])
    File "/usr/lib/python3/dist-packages/apport/report.py", line 550, in 
add_proc_info
  self.add_proc_environ(pid, extraenv)
    File "/usr/lib/python3/dist-packages/apport/report.py", line 619, in 
add_proc_environ
  env = _read_file('environ', dir_fd=proc_pid_fd).replace('\n', '\\n')
    File "/usr/lib/python3/dist-packages/apport/report.py", line 73, in 
_read_file
  with open(path, 'rb', opener=lambda path, mode: os.open(path, mode, 
dir_fd=dir_fd)) as fd:
    File "/usr/lib/python3/dist-packages/apport/report.py", line 73, in 
  with open(path, 'rb', opener=lambda path, mode: os.open(path, mode, 
dir_fd=dir_fd)) as fd:
  TypeError: argument should be integer or None, not list

  [2]
  ==
  ERROR: test_add_proc_info (__main__.T)
  add_proc_info().
  --
  Traceback (most recent call last):
    File "./test_report.py", line 210, in test_add_proc_info
  self.assertRaises(ValueError, pr.add_proc_info, p.pid)
    File "/usr/lib/python3.7/unittest/case.py", line 743, in assertRaises
  return context.handle('assertRaises', args, kwargs)
    File "/usr/lib/python3.7/unittest/case.py", line 178, in handle
  callable_obj(*args, **kwargs)
    File "/usr/lib/python3/dist-packages/apport/report.py", line 544, in 
add_proc_info
  proc_pid_fd = os.open('/proc/%s' % pid, os.O_RDONLY | os.O_PATH | 
os.O_DIRECTORY)
  FileNotFoundError: [Errno 2] No such file or directory: '/proc/1899'

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

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


[Touch-packages] [Bug 1870060] Re: systemd ProtectSystem/mount namespace makes apport fail (impact most of our default system services)

2020-11-04 Thread Brian Murray
** Also affects: apport (Ubuntu Groovy)
   Importance: Undecided
   Status: New

** Also affects: bluez (Ubuntu Groovy)
   Importance: Undecided
   Status: New

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

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

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

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

Title:
  systemd ProtectSystem/mount namespace makes apport fail (impact most
  of our default system services)

Status in apport package in Ubuntu:
  In Progress
Status in bluez package in Ubuntu:
  Invalid
Status in apport source package in Focal:
  Triaged
Status in bluez source package in Focal:
  Invalid
Status in apport source package in Groovy:
  Triaged
Status in bluez source package in Groovy:
  New

Bug description:
  [Impact]
  apport is not creating crash files for multiple system services that use 
ProtectSystem since Ubuntu 20.04 LTS.

  [Test Case]
  On an Ubuntu desktop system perform the following step
  1) sudo pkill -11 upowerd

  With the current version of apport there will not be a crash file for
  upowerd in /var/crash/. With the version of apport in -proposed there
  will be a crash file for upowerd in /var/crash/.

  [Regression Potential]
  In the event that the changes to /usr/share/apport/apport are bad then apport 
itself would crash thereby preventing us from getting any crash reports. So in 
addition to killing upowerd we should also test a regular application like 
xeyes.

  [Original Description]
  bluetoothd never leaves dumps/crash files when it crashes

  And it seems this is true for everyone. Only supplementary binaries' crash 
reports are shown:
  https://errors.ubuntu.com/?release=Ubuntu%2020.04=bluez=year

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

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


[Touch-packages] [Bug 1870060] Re: systemd ProtectSystem/mount namespace makes apport fail (impact most of our default system services)

2020-11-04 Thread Brian Murray
** Description changed:

+ [Impact]
+ apport is not creating crash files for multiple system services that use 
ProtectSystem since Ubuntu 20.04 LTS.
+ 
+ [Test Case]
+ On an Ubuntu desktop system perform the following step
+ 1) sudo pkill -11 upowerd
+ 
+ With the current version of apport there will not be a crash file for
+ upowerd in /var/crash/. With the version of apport in -proposed there
+ will be a crash file for upowerd in /var/crash/.
+ 
+ [Regression Potential]
+ In the event that the changes to /usr/share/apport/apport are bad then apport 
itself would crash thereby preventing us from getting any crash reports. So in 
addition to killing upowerd we should also test a regular application like 
xeyes.
+ 
+ [Original Description]
  bluetoothd never leaves dumps/crash files when it crashes
  
  And it seems this is true for everyone. Only supplementary binaries' crash 
reports are shown:
  https://errors.ubuntu.com/?release=Ubuntu%2020.04=bluez=year

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

Title:
  systemd ProtectSystem/mount namespace makes apport fail (impact most
  of our default system services)

Status in apport package in Ubuntu:
  In Progress
Status in bluez package in Ubuntu:
  Invalid
Status in apport source package in Focal:
  Confirmed
Status in bluez source package in Focal:
  Invalid

Bug description:
  [Impact]
  apport is not creating crash files for multiple system services that use 
ProtectSystem since Ubuntu 20.04 LTS.

  [Test Case]
  On an Ubuntu desktop system perform the following step
  1) sudo pkill -11 upowerd

  With the current version of apport there will not be a crash file for
  upowerd in /var/crash/. With the version of apport in -proposed there
  will be a crash file for upowerd in /var/crash/.

  [Regression Potential]
  In the event that the changes to /usr/share/apport/apport are bad then apport 
itself would crash thereby preventing us from getting any crash reports. So in 
addition to killing upowerd we should also test a regular application like 
xeyes.

  [Original Description]
  bluetoothd never leaves dumps/crash files when it crashes

  And it seems this is true for everyone. Only supplementary binaries' crash 
reports are shown:
  https://errors.ubuntu.com/?release=Ubuntu%2020.04=bluez=year

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

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


[Touch-packages] [Bug 1902760] Re: Please merge linker bugfix into Ubuntu 20.04 LTS

2020-11-04 Thread Brian Murray
** Tags added: rls-ff-incoming

** Tags added: focal

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

Title:
  Please merge linker bugfix into Ubuntu 20.04 LTS

Status in binutils:
  Fix Released
Status in binutils package in Ubuntu:
  New

Bug description:
  Binutils bug https://sourceware.org/bugzilla/show_bug.cgi?id=26262
  fixes a problem that Intel Fortran is running into when using the -ipo
  option to request link time optimization. Please merge the fix into
  Ubuntu 20.04 LTS

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

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


[Touch-packages] [Bug 1901026] Please test proposed package

2020-11-03 Thread Brian Murray
Hello Luis, or anyone else affected,

Accepted gdb into bionic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/gdb/8.1.1-0ubuntu1 in
a few hours, and then in the -proposed repository.

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

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

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

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

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

Title:
  [GDB] No socket file connection support

Status in gdb package in Ubuntu:
  New
Status in gdb source package in Bionic:
  Fix Committed

Bug description:
  GDB on Ubuntu 18.04 (GNU gdb (Ubuntu 8.1-0ubuntu3.2)
  8.1.0.20180409-git) does not support connecting to a remote target via
  a socket file.

  This is the error we get:

  (gdb) target remote /run/user/1000/at-spi2-QTZBS0/socket
  /run/user/1000/at-spi2-QTZBS0/socket: No such device or address.

  Commit c1168a2f66553cd4730931cf59e3be8378a1a03f enables this in GDB.
  It would be nice to have it backported.

  Here's the commit link: https://sourceware.org/git/?p=binutils-
  gdb.git;a=commit;h=c1168a2f66553cd4730931cf59e3be8378a1a03f

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

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


[Touch-packages] [Bug 1901026] Re: [GDB] No socket file connection support

2020-11-03 Thread Brian Murray
It would be better to have a documented test case here, but it seems
pretty straight-forward given the manual changes in the diff.

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

** Changed in: gdb (Ubuntu Bionic)
   Status: Incomplete => Fix Committed

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

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

Title:
  [GDB] No socket file connection support

Status in gdb package in Ubuntu:
  New
Status in gdb source package in Bionic:
  Fix Committed

Bug description:
  GDB on Ubuntu 18.04 (GNU gdb (Ubuntu 8.1-0ubuntu3.2)
  8.1.0.20180409-git) does not support connecting to a remote target via
  a socket file.

  This is the error we get:

  (gdb) target remote /run/user/1000/at-spi2-QTZBS0/socket
  /run/user/1000/at-spi2-QTZBS0/socket: No such device or address.

  Commit c1168a2f66553cd4730931cf59e3be8378a1a03f enables this in GDB.
  It would be nice to have it backported.

  Here's the commit link: https://sourceware.org/git/?p=binutils-
  gdb.git;a=commit;h=c1168a2f66553cd4730931cf59e3be8378a1a03f

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

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


[Touch-packages] [Bug 1902225] Re: SRU: update gdb 8.1.1 for 18.04 LTS

2020-11-03 Thread Brian Murray
Hello Matthias, or anyone else affected,

Accepted gdb into bionic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/gdb/8.1.1-0ubuntu1 in
a few hours, and then in the -proposed repository.

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

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

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

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

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

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

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

Title:
  SRU: update gdb 8.1.1 for 18.04 LTS

Status in gdb package in Ubuntu:
  New
Status in gdb source package in Bionic:
  Fix Committed

Bug description:
  gdb 8.1.1 is a minor bug fix release for 8.1. Some of the issues fixed
  in 8.1.1 are already fixed in the branch update in 8.1-0ubuntu3:

   * gdb 8.1.1 release.
  This is a minor corrective release over GDB 8.1, fixing following issues:
  - PR gdb/23028 (inconsistent disassemble of vcvtpd2dq)
  - PR gdb/23053 (Fix -D_GLIBCXX_DEBUG gdb-add-index regression)
  - PR gdb/23127 ([AArch64] GDB cannot be used for debugging software that
uses high Virtual Addresses)
  - PR server/23158 (gdbserver no longer functional on Windows)
  - PR breakpoints/23210 ([8.1/8.2 Regression] Bogus Breakpoint address
adjusted from 0xf7fe7dd3 to 0xf7fe7dd3)
  Already fixed in 8.1-0ubuntu3:
  - PR gdb/22824 (misleading description of new rbreak Python function in
GDB 8.1 NEWS file)
  - PR gdb/22849 (ctrl-c doesn't work in extended-remote)
  - PR gdb/22907 ([Regression] gdbserver doesn't work with filename-only
binaries).
* Allow remote debugging over a Unix local domain socket. LP: #1901026.

  This minor version update fixes four upstream issues (not counting the
  Windows specific issue), plus allows remote debugging over a Unix
  local domain socket., a patch taken from the 8.2 development.

  Validation: The tests run during build time are passing, and the
  remote debugging is checked to be working (no automated test case).

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

-- 
Mailing list: https://launchpad.net/~touch-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-11-03 Thread Brian Murray
Hello Leon, or anyone else affected,

Accepted network-manager into focal-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/network-
manager/1.22.10-1ubuntu2.2 in a few hours, and then in the -proposed
repository.

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

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

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

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

** Changed in: network-manager (Ubuntu Focal)
   Status: In Progress => Fix Committed

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

-- 
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:
  Fix Committed

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.

   The killer 500s Wi-Fi does not want the network-manger to manager the
  wake-on-LAN so the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set.
  (The driver will manager itself.) When the network-manager managers
  the wake-on-LAN, all of the Wi-Fi functions will be lost after the OS
  resumed from suspend.

  [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 function 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]

   * This patch modifies the wake on lan parameters, please test that
  the corresponding feature still works fine with the different
  configuration values.

   1. Magic packet test:
    Set Wake on Wireless to off
    Send magic packet to the system
    Ensure it does not wake up

    Set Wake on Wirless to on
    Send magic packet to the system
    Ensure it does wake up

   2. Wi-Fi function test after resumed from suspend:
    After resume from suspend, the Wi-Fi should work normally.
    Scan APs.
    Connect to an AP.

  [Other Info]

   * platform: add the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE status
  check (!597) · Merge Requests · NetworkManager / NetworkManager ·
  GitLab -
  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/597#note_588639

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


  1   2   3   4   5   6   7   8   9   10   >