[Touch-packages] [Bug 1861177] Re: seccomp_rule_add is very slow

2020-08-01 Thread Mathew Hodson
** Project changed: snapd => ubuntu-translations

** No longer affects: ubuntu-translations

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

Title:
  seccomp_rule_add is very slow

Status in libseccomp package in Ubuntu:
  Fix Released
Status in libseccomp source package in Xenial:
  Fix Released
Status in libseccomp source package in Bionic:
  Fix Released
Status in libseccomp source package in Eoan:
  Won't Fix
Status in libseccomp source package in Focal:
  Fix Released
Status in libseccomp source package in Groovy:
  Fix Released

Bug description:
  [IMPACT]
  There is a known and patched issue with version 2.4 of libseccomp where 
certain operations have a large performance regression. This is causing some 
packages that use libseccomp such as container orchestration systems to 
occasionally time out or otherwise fail under certain workloads.

  Please consider porting the patch into the various Ubuntu versions
  that have version 2.4 of libseccomp and into the backports. The
  performance patch from version 2.5 (yet to be released) applies
  cleanly on top of the 2.4 branch of libseccomp.

  For more information, and for a copy of the patch (which can also be
  cherry picked from the upstream libseccomp repos) see the similar
  Debian issue: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943913

  Upstream issue : https://github.com/seccomp/libseccomp/issues/153
  Upstream fix : https://github.com/seccomp/libseccomp/pull/180/

  [Test Case]

  For this test case we use Docker on Ubuntu Groovy (20.10) :

  --> Current libseccomp version
  #dpkg -l | grep libseccomp
  ii  libseccomp2:amd64  2.4.3-1ubuntu3 
 amd64high level interface to Linux seccomp filter

  ## pull ubuntu image
  # docker pull ubuntu
  ## create a container
  # docker run --name test_seccomp -it 74435f89ab78 /bin/bash

  ## run test case
  # for i in `seq 1 40`; do (time sudo docker exec test_seccomp true &); done
  ...
  MAX TIME :
  real  0m10,319s
  user  0m0,018s
  sys   0m0,033s

  
  --> Patched libseccomp version

  # dpkg -l | grep libseccomp
  ii  libseccomp2:amd64  2.4.3-1ubuntu4 
 amd64high level interface to Linux seccomp filter

  # docker start test_seccomp
  ## run test case
  # for i in `seq 1 40`; do (time sudo docker exec test_seccomp true &); done
  ...
  MAX TIME :
  real  0m3,650s
  user  0m0,025s
  sys   0m0,028s

  [Regression Potential]

  The first of the 2 patches cleans up the code that adds rules to a
  single filter without changing the logic of the code. The second patch
  introduces the idea of shadow transactions. On a successful
  transaction commit the old transaction checkpoint is preserved and is
  brought up to date with the current filter. The next time a new
  transaction starts, it checks is the a shadow transaction exist and if
  so the shadow is used instead of creating a new checkpoint from
  scratch [1]. This is the patch that mitigates the performance
  regression. Any potential regression will involve the parts of the
  code that add rules to filters and/or the code that creates and checks
  the shadow transactions.

  
  [Other]

  Affected releases : Groovy, Focal, Eoan, Bionic, Xenial.

  [1]
  
https://github.com/seccomp/libseccomp/pull/180/commits/bc3a6c0453b0350ee43e4925482f705a2fbf5a4d

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

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


[Touch-packages] [Bug 1889297] Re: Bionic: debian-installer FTBFS because udev-udeb depends on libkmod2 not libkmod2-udeb

2020-08-01 Thread Mathew Hodson
** No longer affects: kmod (Ubuntu)

** No longer affects: systemd (Ubuntu)

** Tags added: ftbfs regression-update

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

Title:
  Bionic: debian-installer FTBFS because udev-udeb depends on libkmod2
  not libkmod2-udeb

Status in kmod source package in Bionic:
  Fix Committed
Status in systemd source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

   * debian-installer currently FTBFS on Bionic because
 udev-udeb depends on libkmod2 not on libkmod2-udeb.
 
   * This regression has been introduced in kmod 24-1ubuntu3.3,
 and it propagated into udev-udeb in systemd 237-3ubuntu10.40.

   * See the '[Details]' section for the details. :)

  [Fix]

   * That kmod change fixes a FTBFS with newer debhelper on Eoan and later,
 but it is not required with older debhelper on Bionic. Just revert it.

   * There is no need to "fix" this in Eoan and later (debhelper >= 12.3)
   
   * No-change rebuild of systemd (for udev-udeb to pick up libkmod2-udeb.)

  [Test Case]

   * Try to build debian-installer on Bionic; it FTBFS:
 
The following packages have unmet dependencies:
 udev-udeb : Depends: libkmod2 but it is not installable
E: Unable to correct problems, you have held broken packages.

   * Check if libkmod2's shlibs file contains an udeb line:
   
 $ dpkg-deb --control libkmod2__.deb dir
 $ cat dir/shlibs
 libkmod 2 libkmod2
 udeb: libkmod 2 libkmod2-udeb  # this is good.

  [Regression Potential]

   * The fix only changes the libkmod2's shlibs file to include
 an udeb line (so udebs that depend on that library package
 should depend on the -udeb package.)

 Thus the regression potential is limited to the installer,
 and the udeb packages which depend on libkmod2 (udev-udeb
 only, probably.)

 Regressions could be seen as failures to load libkmod2.so
 and/or not finding its dynamic symbols.

   * There is a no-change rebuild of systemd involved/required,
 so some dependency updates may potentially impact systemd.
 
  [Details]

  debian-installer currently FTBFS on Bionic because
  udev-udeb depends on libkmod2 not on libkmod2-udeb:

The following packages have unmet dependencies:
 udev-udeb : Depends: libkmod2 but it is not installable
E: Unable to correct problems, you have held broken packages.

  This regression has been introduced in kmod 24-1ubuntu3.3,
  and it propagated into udev-udeb in systemd 237-3ubuntu10.40.

kmod (24-1ubuntu3.3) bionic; urgency=medium
<...>
  * Removed --add-udeb from dh_makeshlibs, since libkmod2-udeb does not
actually contain a library. (Closes: #939779)
<...>

  From dh_makeshlibs(1):

--add-udeb=udeb
   Create an additional line for udebs in the shlibs file
   and use udeb as the package name for udebs to depend on
   instead of the regular library package.

  Before:

  $ dpkg-deb --control libkmod2_24-1ubuntu3.2_amd64.deb
  libkmod2-u32-control

$ cat libkmod2-u32-control/shlibs 
libkmod 2 libkmod2
udeb: libkmod 2 libkmod2-udeb

$ dpkg-deb --info udev-udeb_237-3ubuntu10.39_amd64.udeb | grep Depends:
 Depends: ..., libkmod2-udeb, ...

  After:

  $ dpkg-deb --control libkmod2_24-1ubuntu3.3_amd64.deb
  libkmod2-u33-control

$ cat libkmod2-u33-control/shlibs 
libkmod 2 libkmod2

$ dpkg-deb --info udev-udeb_237-3ubuntu10.40_amd64.udeb | grep Depends:
 Depends: ..., libkmod2, ...

  
  That kmod change fixes a FTBFS with newer debhelper on Eoan and later,
  but it is not required with older debhelper on Bionic:

  Eoan:

$ dpkg -s debhelper | grep Version:
Version: 12.6.1ubuntu2

$ dpkg-buildpackpage
<...>
dh_makeshlibs --add-udeb=libkmod2-udeb -- -c4
dh_makeshlibs: The udeb libkmod2-udeb does not contain any shared 
libraries but --add-udeb=libkmod2-udeb was passed!?
make: *** [debian/rules:120: .stamp-binary] Error 255
dpkg-buildpackage: error: debian/rules binary subprocess returned exit 
status 2

  Bionic:

$ dpkg -s debhelper | grep Version:
Version: 11.1.6ubuntu2

$ dpkg-buildpackpage
<...>
dh_makeshlibs --add-udeb=libkmod2-udeb -- -c4
dh_shlibdeps -- --warnings=7
<...>
dpkg-buildpackage: info: binary and diff upload (original source NOT 
included)

  
  There is no need to "fix" this in Eoan and later, as debhelper >= 12.3
  has support for udeb auto-detection in dh_makeshlibs(1) -- and the udeb
  line is added to shlibs by default (without --add-udeb):

  From dh_makeshlibs(1):

Since debhelper 12.3, dh_makeshlibs will by default add an 

[Touch-packages] [Bug 1882248] Re: [SRU] plug headset won't proper reconfig ouput to it on machine with default output

2020-08-01 Thread Mathew Hodson
** No longer affects: linux-oem (Ubuntu)

** Tags removed: originate-1881842

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

Title:
  [SRU] plug headset won't proper reconfig ouput to it on machine with
  default output

Status in HWE Next:
  New
Status in OEM Priority Project:
  Fix Committed
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released
Status in pulseaudio source package in Bionic:
  Fix Committed

Bug description:
  This is for pulseaudio bionic:

  [Impact]
  On a Dell machine without internal spk and internal mic, after freshly
  install the bionic on it, the active profile is Off, after users plug a
  headset to it and users select the headset from the pop-up dialogue,
  users expect the profile changes to analog-stereo (headset is on it),
  but the active_profile is still Off.

  [Fix]
  Upstream already has a patch to fix it, cherrypiack that patch to bionic.
  And that patch is already in the eoan, focal, ...

  [Test Case]
  freshly install the bionic with this patch on that dell machine,
  plug headset and select the headset from UI, the profile changes to
  analog-stereo, and play some sound, we could hear it from the headset

  [Regression Risk]
  Low, this patch is already in the upstream for a long time, and it is
  already in the eoan and focal.


  
  For linux kernel (oem-b):

  [Impact]
  On a Dell machine without internal spk and internal mic, after freshly
  install the bionic on it, and users plug a headset, the sound couldn't
  output from headset.

  [Fix]
  reverse the order of headset mic and headphone mic

  [Test Case]
  freshly install the bionic with this patch on that dell machine,
  plug headset and play sound, we could hear the sound from headset.

  [Regression Risk]
  Low, this patch only affects the machine without internal mic and
  internal spk, and I already tested this patch on the machine without
  internal mic and internal spk, it worked well.

  target machine does not have built-in speaker, and the monitor does
  not have an audio output (like d-sub VGA)

  As first boot, there will be a "dummy output" in g-c-c.

  After plug-in headset, there will be a headset appear in g-c-c, but it
  won't be automatically selected even it's chosen in the pop-up window.

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

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


[Touch-packages] [Bug 1889206] Re: Regression in USN-4436-1

2020-08-01 Thread Mathew Hodson
** No longer affects: librsvg (Ubuntu)

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

Title:
  Regression in USN-4436-1

Status in librsvg:
  Unknown
Status in librsvg source package in Xenial:
  Fix Released
Status in librsvg source package in Bionic:
  Fix Released

Bug description:
  The security fix for librsvg introduced a regression in aisleriot.

  Steps to reproduce:

  1- install gnome-cards-data
  2- run "sol" to start Aislerot
  3- Switch card layout to "Anglo"
  4- Notice some cards are missing graphics

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

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


[Touch-packages] [Bug 1886809] Re: Pulse connect VPN exists because unwanted avahi network starts

2020-07-30 Thread Mathew Hodson
** Changed in: avahi (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Pulse connect VPN exists because unwanted avahi network starts

Status in avahi package in Ubuntu:
  New

Bug description:
  Pulse VPNs exists very often because avahi enforces network
  192.250.0.0/0 over tun0 interface.  The message error is:

  rmon.error Unauthorized new route to 169.254.0.0/0.0.0.0 has been
  added (conflicts with our route to 0.0.0.0), disconnecting
  (routemon.cpp:598)

  No matter the options to skip avahi on /etc/default/avahi-daemon, it
  always calls /etc/network/if-up.d/avahi-autoipd and raises this
  discovery network.

  A fix can be done patching /etc/network/if-up.d/avahi-autoipd to skip
  any tunnel interface.

  --- /etc/network/if-up.d/avahi-autoipd.dpkg-old 2020-07-08 13:25:41.834569800 
+0200
  +++ /etc/network/if-up.d/avahi-autoipd  2020-07-07 10:07:37.68581 +0200
  @@ -11,6 +11,10 @@
   
   [ -x /usr/sbin/avahi-autoipd ] || exit 0
   
  +case "$IFACE" in
  +   tun*) exit 0 ;;
  +esac
  +
   [ "$IFACE" != "lo" ] || exit 0
   case "$ADDRFAM" in
  inet) ;;

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

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


[Touch-packages] [Bug 1886112] Re: Enabling DMESG_RESTRICT in Groovy Onward

2020-07-30 Thread Mathew Hodson
** Changed in: linux (Ubuntu Groovy)
   Importance: Undecided => Wishlist

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

** Changed in: util-linux (Ubuntu Groovy)
   Importance: Undecided => Wishlist

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

Title:
  Enabling DMESG_RESTRICT in Groovy Onward

Status in linux package in Ubuntu:
  Fix Committed
Status in procps package in Ubuntu:
  In Progress
Status in util-linux package in Ubuntu:
  In Progress
Status in linux source package in Groovy:
  Fix Committed
Status in procps source package in Groovy:
  In Progress
Status in util-linux source package in Groovy:
  In Progress

Bug description:
  [Impact]

  This bug implements the enablement of CONFIG_SECURITY_DMESG_RESTRICT
  feature by default for Groovy onward, proposed to ubuntu-devel:

  https://lists.ubuntu.com/archives/ubuntu-devel/2020-June/041063.html

  The kernel log buffer contains a wealth of sensitive information, such
  as detailed call traces and kernel addresses found in register dumps
  in kernel oops messages.

  Exploit developers and attackers can leverage these information leaks
  to get past KASLR, and they can use the kernel log buffer to get
  instant feedback on their privilege escalation attacks, as failures
  will be shown as further oops messages, which attackers can use to fix
  and tune their programs until they work.

  Currently, if I create a new, unprivileged user on a Focal system,
  they cannot access /var/log/kern.log, /var/log/syslog or see system
  events in journalctl. But yet, they are given free reign to the kernel
  log buffer.

  $ sudo adduser dave
  $ su dave
  $ groups
  dave
  $ cat /var/log/kern.log
  cat: /var/log/kern.log: Permission denied
  $ cat /var/log/syslog
  cat: /var/log/syslog: Permission denied
  $ journalctl
  Hint: You are currently not seeing messages from other users and the system.
    Users in groups 'adm', 'systemd-journal' can see all messages.
    Pass -q to turn off this notice.
  Jun 16 23:44:59 ubuntu systemd[2328]: Reached target Main User Target.
  Jun 16 23:44:59 ubuntu systemd[2328]: Startup finished in 69ms.
  $ dmesg
  [0.00] Linux version 5.4.0-34-generic (buildd at lcy01-amd64-014)
  (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #38-Ubuntu SMP Mon May 25 
15:46:55
  UTC 2020 (Ubuntu 5.4.0-34.38-generic 5.4.41)
  [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-34-generic
  root=UUID=f9f909c3-782a-43c2-a59d-c789656b4188 ro
  ...

  I propose that we restrict access to dmesg to users in group 'adm'
  like so:

  1) Add kernel.dmesg_restrict = 1 to
 /etc/sysctl.d/10-kernel-hardening.conf
  2) Following changes to /bin/dmesg permissions in package 'util-linux'
  - Ownership changes to root:adm
  - Permissions changed to 0750 (-rwxr-x---)
  - Add cap_syslog capability to binary.

  For most users, they will use the initial admin account, which is in
  the 'adm' group already, and will see no impact to these changes. If a
  log scraper type program needs access to dmesg, the user the daemon
  runs as can simply be added to the 'adm' group.

  [Testcase]

  Currently, all users can run /usr/bin/dmesg to view the kernel log
  buffer:

  $ dmesg
  [0.00] Linux version 5.4.0-34-generic (buildd at lcy01-amd64-014)
  (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #38-Ubuntu SMP Mon May 25 
15:46:55
  UTC 2020 (Ubuntu 5.4.0-34.38-generic 5.4.41)
  [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-34-generic
  root=UUID=f9f909c3-782a-43c2-a59d-c789656b4188 ro
  ...

  When the changes are applied, the default admin user will be able to
  view dmesg (since they are in group 'adm'), while new unprivileged
  users will not.

  Test packages are available in the following ppa:
  https://launchpad.net/~mruffell/+archive/ubuntu/lp1886112-test

  $ whoami
  ubuntu
  $ groups
  ubuntu adm cdrom sudo dip plugdev
  $ dmesg
  [0.00] Linux version 5.4.0-34-generic (buildd at lcy01-amd64-014)
  (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #38-Ubuntu SMP Mon May 25 
15:46:55
  UTC 2020 (Ubuntu 5.4.0-34.38-generic 5.4.41)
  [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-34-generic
  root=UUID=f9f909c3-782a-43c2-a59d-c789656b4188 ro
  ...

  $ sudo adduser dave
  $ su dave
  $ groups
  dave
  $ dmesg
  -bash: /usr/bin/dmesg: Permission denied

  [Regression Potential]

  Some users or log scraper type programs may need to view the kernel
  log buffer, or have access to dmesg. In this case, the underlying
  service user would need to be added to the 'adm' group.

  Users have the ability to disable DMESG_RESTRICT by changing
  kernel.dmesg_restrict sysctl in /etc/sysctl.d/10-kernel-hardening.conf
  from '1' to '0', followed by a reboot.

To manage notifications about this bug go to:

[Touch-packages] [Bug 1869117] Re: python-pip install fails in Ubuntu 20.04 unmet dependencies (Focal)

2020-07-22 Thread Mathew Hodson
** No longer affects: python2.7 (Ubuntu)

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

Title:
  python-pip install fails in Ubuntu 20.04 unmet dependencies (Focal)

Status in python-pip package in Ubuntu:
  Won't Fix

Bug description:
  apt-get install python-pip fails in Ubuntu 20.04:

  The following packages have unmet dependencies:
   python-pip : Depends: python-pip-whl (= 18.1-5ubuntu1) but 20.0.2-2 is to be 
installed
Recommends: python-all-dev (>= 2.6) but it is not going to be 
installed
Recommends: python-wheel but it is not going to be installed
  E: Unable to correct problems, you have held broken packages.

  The python-pip package needs to be updated to accept newer versions of
  python-pip-whl.

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

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


[Touch-packages] [Bug 1659719] Re: ssh can't call a binary from a snap without the full path

2020-07-11 Thread Mathew Hodson
** Also affects: openssh (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964580
   Importance: Unknown
   Status: Unknown

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

Title:
  ssh can't call a binary from a snap without the full path

Status in Snappy:
  Fix Committed
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in openssh package in Ubuntu:
  Confirmed
Status in pam package in Ubuntu:
  In Progress
Status in livecd-rootfs source package in Xenial:
  New
Status in openssh source package in Xenial:
  New
Status in pam source package in Xenial:
  New
Status in livecd-rootfs source package in Bionic:
  New
Status in openssh source package in Bionic:
  New
Status in pam source package in Bionic:
  New
Status in livecd-rootfs source package in Focal:
  New
Status in openssh source package in Focal:
  New
Status in pam source package in Focal:
  New
Status in livecd-rootfs source package in Groovy:
  Fix Released
Status in openssh source package in Groovy:
  Confirmed
Status in pam source package in Groovy:
  In Progress
Status in openssh package in Debian:
  Unknown

Bug description:
  ssh can't call a binary from a snap, it will only work using the full
  path.

  Let's say I have the hello snap installed in 192.168.122.24. Then:

  elopio@ubuntu-xenial:~/mosh$ ssh 192.168.122.24 hello
  elopio@192.168.122.24's password:
  bash: hello: command not found
  elopio@ubuntu-xenial:~/mosh$ ssh 192.168.122.24 /snap/bin/hello
  elopio@192.168.122.24's password:
  Hello, world!

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

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


[Touch-packages] [Bug 1782984] Re: Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications

2020-07-05 Thread Mathew Hodson
** Summary changed:

- PCManFM freezes with Assertion `!xcb_xlib_threads_sequence_lost' failed when 
clicking on a file or folder in 18.04
+ Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications

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

Title:
  Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple
  applications

Status in libx11 package in Ubuntu:
  Confirmed
Status in pcmanfm package in Ubuntu:
  Triaged

Bug description:
  STEPS TO REPRODUCE
  ==
  The bug seems to occur when clicking on a file or folder. It is random and 
difficult to provide clear steps to reproduce. It is, however, a common 
situation.

  EXPECTED RESULTS
  
  pcmanfm works without problem.

  ACTUAL RESULTS
  ==
  All pcmanfm windows become unresponsive, though background processes (e.g. 
copying) may continue without problem. with the same error message in 
~/.cache/lxsession/LXDE/run.log:

  [xcb] Unknown sequence number while processing queue
  [xcb] Most likely this is a multi-threaded client and XInitThreads has not 
been called
  [xcb] Aborting, sorry about that.
  pcmanfm: xcb_io.c:259: poll_for_event: Assertion 
`!xcb_xlib_threads_sequence_lost' failed.
  ** Message: 19:58:49.267: app.vala:130: pcmanfm exit with this type of exit: 6
  ** Message: 19:58:49.268: app.vala:148: Exit not normal, try to reload

  (note the timestamp on the message will vary)

  AFFECTED VERSIONS
  =
  1.2.5-3ubuntu1
  NOT 1.2.4-1ubuntu0.1

  UPSTREAM BUG
  
  https://sourceforge.net/p/pcmanfm/bugs/1089/

  ADDITIONAL NOTES
  
  Other GTK2 file managers (e.g. Thunar) and applications (e.g. GIMP, Leafpad) 
seem to have the same problems. This is probably at least rooted in a GTK2 bug:
  https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1808710

  To further assert this, note that there is a SpaceFM file manager that
  is available in GTK2 and GTK3. The GTK2 version displays the behavior.
  The GTK3 version does not. Same with LibreOffice.

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

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


[Touch-packages] [Bug 1782984] Re: PCManFM freezes with Assertion `!xcb_xlib_threads_sequence_lost' failed when clicking on a file or folder in 18.04

2020-07-05 Thread Mathew Hodson
** Changed in: libx11 (Ubuntu)
   Importance: Undecided => High

** Bug watch removed: github.com/rust-windowing/glutin/issues #1034
   https://github.com/rust-windowing/glutin/issues/1034

** Bug watch removed: gitlab.freedesktop.org/mesa/mesa/issues #108
   https://gitlab.freedesktop.org/mesa/mesa/issues/108

** Bug watch removed: gitlab.gnome.org/GNOME/gtk/-/issues #2767
   https://gitlab.gnome.org/GNOME/gtk/-/issues/2767

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

Title:
  PCManFM freezes with Assertion `!xcb_xlib_threads_sequence_lost'
  failed when clicking on a file or folder in 18.04

Status in libx11 package in Ubuntu:
  Confirmed
Status in pcmanfm package in Ubuntu:
  Triaged

Bug description:
  STEPS TO REPRODUCE
  ==
  The bug seems to occur when clicking on a file or folder. It is random and 
difficult to provide clear steps to reproduce. It is, however, a common 
situation.

  EXPECTED RESULTS
  
  pcmanfm works without problem.

  ACTUAL RESULTS
  ==
  All pcmanfm windows become unresponsive, though background processes (e.g. 
copying) may continue without problem. with the same error message in 
~/.cache/lxsession/LXDE/run.log:

  [xcb] Unknown sequence number while processing queue
  [xcb] Most likely this is a multi-threaded client and XInitThreads has not 
been called
  [xcb] Aborting, sorry about that.
  pcmanfm: xcb_io.c:259: poll_for_event: Assertion 
`!xcb_xlib_threads_sequence_lost' failed.
  ** Message: 19:58:49.267: app.vala:130: pcmanfm exit with this type of exit: 6
  ** Message: 19:58:49.268: app.vala:148: Exit not normal, try to reload

  (note the timestamp on the message will vary)

  AFFECTED VERSIONS
  =
  1.2.5-3ubuntu1
  NOT 1.2.4-1ubuntu0.1

  UPSTREAM BUG
  
  https://sourceforge.net/p/pcmanfm/bugs/1089/

  ADDITIONAL NOTES
  
  Other GTK2 file managers (e.g. Thunar) and applications (e.g. GIMP, Leafpad) 
seem to have the same problems. This is probably at least rooted in a GTK2 bug:
  https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1808710

  To further assert this, note that there is a SpaceFM file manager that
  is available in GTK2 and GTK3. The GTK2 version displays the behavior.
  The GTK3 version does not. Same with LibreOffice.

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

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


[Touch-packages] [Bug 1808710] Re: !xcb_xlib_threads_sequence_lost error with GTK2 applications

2020-07-05 Thread Mathew Hodson
*** This bug is a duplicate of bug 1782984 ***
https://bugs.launchpad.net/bugs/1782984

** This bug has been marked a duplicate of bug 1782984
   PCManFM freezes with Assertion `!xcb_xlib_threads_sequence_lost' failed when 
clicking on a file or folder in 18.04

** Bug watch removed: Claws Mail bugzilla #4203
   http://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4203

** Bug watch removed: redmine.audacious-media-player.org/issues #798
   https://redmine.audacious-media-player.org/issues/798

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

Title:
  !xcb_xlib_threads_sequence_lost error with GTK2 applications

Status in gtk+2.0 package in Ubuntu:
  Confirmed
Status in libx11 package in Ubuntu:
  New

Bug description:
  GTK2 applications randomly crash or freeze with error like:

  [xcb] Unknown sequence number while processing queue
  [xcb] Most likely this is a multi-threaded client and XInitThreads has not 
been called
  [xcb] Aborting, sorry about that.
  : ../../src/xcb_io.c:263: poll_for_event: Assertion 
`!xcb_xlib_threads_sequence_lost' failed.

  where  is the name of the executable, e.g. audacious,
  soffice.bin, etc.

  RELATED BUGS
  LibreOffice: 
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1801161
  PCManFM: https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/1782984
  Audacious: https://redmine.audacious-media-player.org/issues/798
  FreeCAD: https://bugs.launchpad.net/ubuntu/+source/freecad/+bug/1754084
  ClawsMail: 
https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4203

  OTHER APPLICATIONS
  SpaceFM, Pidgin, GPicView and GIMP appear to have similar problems.

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

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


[Touch-packages] [Bug 1787460] Re: Unattended upgrades removed linux-image-generic

2020-07-05 Thread Mathew Hodson
The issues with virtualbox and hwe can be tracked in bug 1866518 or bug
1874309

** No longer affects: linux-meta (Ubuntu)

** No longer affects: linux-meta (Ubuntu Trusty)

** No longer affects: linux-meta (Ubuntu Xenial)

** No longer affects: linux-meta (Ubuntu Bionic)

** No longer affects: linux-meta (Ubuntu Cosmic)

** No longer affects: linux-meta (Ubuntu Disco)

** No longer affects: linux-meta-hwe (Ubuntu)

** No longer affects: linux-meta-hwe (Ubuntu Trusty)

** No longer affects: linux-meta-hwe (Ubuntu Xenial)

** No longer affects: linux-meta-hwe (Ubuntu Bionic)

** No longer affects: linux-meta-hwe (Ubuntu Cosmic)

** No longer affects: linux-meta-hwe (Ubuntu Disco)

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

Title:
  Unattended upgrades removed linux-image-generic

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Trusty:
  Fix Released
Status in apt source package in Xenial:
  Fix Released
Status in apt source package in Bionic:
  Fix Released
Status in apt source package in Cosmic:
  Fix Released
Status in apt source package in Disco:
  Fix Released

Bug description:
  [Impact]
  If a user accidentally removed linux-generic, unattended-upgrades will also 
autoremove linux-image-generic, leaving them without kernel upgrades.

  [Test Case]
  1. Remove all reverse dependencies of linux-image-generic
  2. Mark linux-image-generic as automatically installed
  3. Run unattended-upgrades -v --dry-run --debug to ensure that 
linux-image-generic is not removed (after verifying that it is, with old apt)

  [Regression potential]
  This adds two regular expressions to the list of packages that must not be 
automatically removed. As such, the only possible regression is that some 
packages starting with linux-image, not containing any dots, are not removed

  [Original bug report]
  On a fairly fresh install of 18.04 with no modifications whatsoever to the 
unattended-upgrades configuration, it decided to remove linux-image-generic 
which also removed linux-modules-extra which caused sound drivers to disappear, 
etc.

  The relative snippet from /var/log/unattended-upgrades/unattended-
  upgrades.log is:

  2018-08-15 06:18:00,048 INFO Starting unattended upgrades script
  2018-08-15 06:18:00,048 INFO Allowed origins are: o=Ubuntu,a=bionic, 
o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic
  2018-08-15 06:18:01,552 INFO Removing unused kernel packages: 
linux-headers-generic linux-image-generic linux-headers-4.15.0-32-generic 
linux-headers-4.15.0-32
  2018-08-15 06:18:01,588 WARNING Keeping auto-removable linux-headers-generic 
package(s) because it would also remove the following packages which should be 
kept in this step: libxml2 linux-image-4.15.0-32-generic 
linux-modules-4.15.0-32-generic linux-modules-extra-4.15.0-32-generic
  2018-08-15 06:18:09,476 INFO Packages that were successfully auto-removed: 
linux-headers-4.15.0-32 linux-headers-4.15.0-32-generic linux-headers-generic 
linux-image-generic
  2018-08-15 06:18:09,477 INFO Packages that are kept back: 
linux-headers-generic
  2018-08-15 06:18:10,300 INFO Packages that will be upgraded: libxml2 
linux-image-generic
  2018-08-15 06:18:10,300 INFO Writing dpkg log to 
/var/log/unattended-upgrades/unattended-upgrades-dpkg.log
  2018-08-15 06:18:39,238 INFO All upgrades installed
  2018-08-15 06:18:42,818 INFO Packages that were successfully auto-removed: 
linux-image-generic linux-modules-extra-4.15.0-32-generic
  2018-08-15 06:18:42,818 INFO Packages that are kept back:

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: unattended-upgrades 1.1ubuntu1.18.04.5
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 16 13:17:30 2018
  InstallationDate: Installed on 2018-07-24 (23 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180724)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1861082] Re: [SRU] ubuntu-bug doesn't know how to file bugs against snaps

2020-07-03 Thread Mathew Hodson
** Changed in: apport (Ubuntu)
Milestone: ubuntu-20.04.1 => None

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

Title:
  [SRU] ubuntu-bug doesn't know how to file bugs against snaps

Status in Snapcraft:
  New
Status in snapd:
  Triaged
Status in Snap Store Server:
  New
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Focal:
  Fix Committed

Bug description:
  [Impact]
  Users of Ubuntu 20.04 are not able to easily report bugs against applications 
provided as a snap.

  [Test Case]
  Install subiquity snap:
  # sudo snap install subiquity --classic
  subiquity 20.06.1 aus Canonical✓ installiert
  # snap list | grep subiquity
  subiquity   20.06.1  1938  latest/stable  canonical*  classic

  ubuntu-bug subiquity results in message:
  # LANGUAGE="en_US" apport-cli subiquity

  *** Collecting problem information

  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.
  ...dpkg-query: no packages found matching subiquity

  *** You are about to report a bug against the deb package, but you
  also a have snap published by canonical installed. You can contact
  them via https://bugs.launchpad.net/subiquity for help. Do you want to
  continue with the bug report against the deb?

  What would you like to do? Your options are:
    Y: Yes
    N: No
    C: Cancel

  === New/Expected Result ===
  ubuntu-bug  should ask the user if he/she wants to 
report the bug against the snap or deb package, if both are installed. If the 
snap is chosen, the "Snap" and "SnapSource" fields should be part of the report:

  # LANGUAGE="en_US" apport-cli subiquity

  *** Collecting problem information

  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.
  ...dpkg-query: no packages found matching subiquity

  *** You have two versions of this application installed, which one do
  you want to report a bug against?

  Choices:
    1: subiquity 20.06.1 (stable) snap
    2: subiquity (1938) deb package
    C: Cancel
  Please choose (1/2/C): 1
  .

  *** Send problem report to the developers?

  After the problem report has been sent, please fill out the form in the
  automatically opened web browser.

  What would you like to do? Your options are:
    S: Send report (46.1 KB)
    V: View report
    K: Keep report file for sending later or copying to somewhere else
    I: Cancel and ignore future crashes of this program version
    C: Cancel
  Please choose (S/V/K/I/C): V

  Make sure the following two fields are part of the generated report:
  == Snap =
  subiquity 20.06.1 (stable)

  == SnapSource =
  subiquity

  [Regression Potential]
  Small; the change adds a new add_snap_info() method to report.py and is 
triggered in the ui.py logic only in cases which would have otherwise lead to 
an error message. Furthermore, the change has been uploaded to Groovy some 
while ago where it is being used and tested.

  [Original Bug Report]
  Hello, I had problems with subiquity in the focal live server install image. 
I tried to use 'ubuntu-bug subiquity' to report the bug, but ubuntu-bug 
apparently cannot file bug reports against snaps.

  This is frustrating that users need to know which portions of Ubuntu
  are delivered via debs, which portions are delivered by snaps, and try
  to find a way to report bugs correctly.

  ubuntu-bug should know how to report bugs for Canonical software.

  Thanks

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

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


[Touch-packages] [Bug 1884887] Re: rsyslogd dmesg unit leaves /var/log/dmesg* world readable

2020-06-28 Thread Mathew Hodson
** Changed in: rsyslog (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  rsyslogd dmesg unit leaves /var/log/dmesg* world readable

Status in rsyslog package in Ubuntu:
  New

Bug description:
  [Impact]

  The rsyslog dmesg systemd unit /lib/systemd/system/dmesg.service in
  eoan, focal, and groovy create /var/log/dmesg* with the following
  permissions:

-rw-r--r-- 1 root adm 45146 Jun 16 12:32 /var/log/dmesg

  Most other system logs in /var/log/ are only readable by root and
  group adm.

  While it's true that the kernel dmesg buffer by default can be read by
  anyone using the dmesg(1) command, this can be disabled by setting the
  sysctl kernel.dmesg_restrict to 1, but doing so as a hardening measure
  is thwarted by the world readable nature of /var/log/dmesg.

  The reason dmesg output is sensitive is that it sometimes contains
  kernel addresses for diagnosing kernel problems, but attackers looking
  to attack a kernel are also interested in kernel addresses and other
  information that shows up there.

  [Test Case]

  To reproduce:

   $ ls -l /var/log/dmesg*

  should show only root and group adm access like so:

   -rw-r- 1 root adm 50178 Jun 23 12:55 /var/log/dmesg
   -rw-r- 1 root adm 50217 Jun 23 12:55 /var/log/dmesg.0
   -rw-r- 1 root adm 13941 Jun 23 12:47 /var/log/dmesg.1.gz

  and not world readable:

   -rw-r--r-- 1 root adm 45146 Jun 16 12:32 /var/log/dmesg

  [Regression Potential]

  It's possible tools like apport and others might expect /var/log/dmesg
  to be world-readable.

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

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


[Touch-packages] [Bug 1551623] Re: [SRU] package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed

2020-06-22 Thread Mathew Hodson
** Changed in: gconf (Ubuntu)
   Importance: Critical => Medium

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

Title:
  [SRU] package gconf2 3.2.6-3ubuntu6 failed to install/upgrade:
  dependency problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  Triaged

Bug description:
  [Impact]

  During system upgrades, triggers for gconf2 might activate too early,
  while some of its dependencies aren't configured yet. This happens
  several times in a loop and stops the upgrade in the end.

  The attached debdiffs fix this issue by changing interest to interest-
  noawait in debian/gconf2.triggers file. The triggers will now activate
  near the end of upgrade.

  In addition, the debdiff for Bionic also contains a fix for FTBFS (bug
  1834211).

  [Test Case]

  Triggers for gconf2 are usually activated on changes in
  /usr/share/GConf/gsettings folder, so the main Ubuntu edition (with
  GNOME) is most suitable for reproducing the issue. To reproduce it,
  install that edition, apply all updates, then try upgrading to the
  next release.

  [Regression Potential]

  None, interest-noawait trigger is known to work well in other packages
  (comment 31).

  [Other Info]

  Even if Cosmic goes EOL next month, the fix for it might be worth it
  for release upgrades.

  [Original Description]

  When upgrading from 15.10 to 16.04Beta (2016-03-01), this error occured, 
alongside many others related to systemd and gnome.
  Notice that despite all warnings and errors, finally, the system remained 
functional.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: gconf2 3.2.6-3ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Tue Mar  1 09:21:15 2016
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2015-10-04 (148 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.3
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to xenial on 2016-03-01 (0 days ago)

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

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


[Touch-packages] [Bug 1880968] Re: fixrtc fails due to bad format of input to the date command

2020-06-22 Thread Mathew Hodson
** Changed in: initramfs-tools (Ubuntu Focal)
   Importance: Undecided => Medium

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

Title:
  fixrtc fails due to bad format of input to the date command

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Focal:
  Fix Committed

Bug description:
  The fixrtc script is failing with message:

  date: invalid date '  Wed Apr  1 17:23:44 2020'

  when calling the date command. It looks like it does not like the
  leading spaces for the input date. The date is taken from 'dumpe2fs
  -h' ouptput, and some clean-up on it happens, but it looks like it is
  not enough for BusyBox' date command, at least for the version in
  focal.

  Backporting this to focal is needed.

  [Impact]

  The system date shown on first boot is incorrect, which can be
  problematic on first boot if at that point in time there is no network
  connection. If fixrtc works correctly at least we get the date of the
  last time the rootfs was mounted, which is modern enough to avoid
  problems with snap assertions validation, etc.

  [Test case]

  Boot an image with fixrtc in the kernel command line in a system with
  no network. snap seeding will fail without the patch.

  [Regression Potential]

  Quite small, as the fix is small and targeted.

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

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


[Touch-packages] [Bug 1883027] Re: dump_acpi_tables.py: fix incorrect output and change format

2020-06-22 Thread Mathew Hodson
** Changed in: apport (Ubuntu Focal)
   Importance: Undecided => Medium

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

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

Title:
  dump_acpi_tables.py: fix incorrect output and change format

Status in Apport:
  Confirmed
Status in apport package in Ubuntu:
  Confirmed
Status in apport source package in Focal:
  Confirmed
Status in apport source package in Groovy:
  Confirmed

Bug description:
  dump_acpi_tables.py generates log files that is similar as the output
  from "acpidump" in acpica-tools. The output can be passed to other
  utilities in acpica-tools and fwts.

  It, however, has some subtle differences and some errors.

  Summary:

  1. ACPI tables have 4-char signatures - meaning SSDT's are SSDT, not
  SSDT1, SSDT2 and so on. Each table is unique by its table ID.

  Original:
    SSDT1, SSDT2, SSDT3 ...

  Changed:
    SSDT, SSDT, SSDT ...

  2. (Minor) acpidump outputs are all in upper cases

  3. (Minor) acpidump offset are aligned by data, not address

  Original:
    FFF0: 53 41 56 43 52 44 43 41 4E 43 52 4E 72 4E 50 4D  SAVCRDCANCRNrNPM
    1: 56 0A 04 00 0C FC FF FF FF 0A 03 0A 03 52 44 43  VRDC

  Changed:
  FFF0: 53 41 56 43 52 44 43 41 4E 43 52 4E 72 4E 50 4D  SAVCRDCANCRNrNPM
     1: 56 0A 04 00 0C FC FF FF FF 0A 03 0A 03 52 44 43  VRDC

  4. (Bug) dump_acpi_tables.py generates an extra line when data sizes
  are multiple of 16 bytes

  Original:
  05F0: 30 30 0B 00 08 00 A4 48 50 53 44 A4 53 50 53 44  00.HPSD.SPSD
  05F0: 30 30 0B 00 08 00 A4 48 50 53 44 A4 53 50 53 44 
 00.HPSD.SPSD

  Corrected:
  05F0: 30 30 0B 00 08 00 A4 48 50 53 44 A4 53 50 53 44  00.HPSD.SPSD

  5. (Bug) dump_acpi_tables.py misses an line when data sizes are
  multiple of 15 bytes

  Original:
  07E0: 42 0A 87 5C 2F 03 5F 53 42 5F 55 42 54 43 43 43  B..\/._SB_UBTCCC

  Corrected:
  07E0: 42 0A 87 5C 2F 03 5F 53 42 5F 55 42 54 43 43 43  B..\/._SB_UBTCCC
  07F0: 49 33 86 5C 2E 5F 53 42 5F 55 42 54 43 0A 80 I3.\._SB_UBTC..

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

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


[Touch-packages] [Bug 1866194] Re: External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all.

2020-06-22 Thread Mathew Hodson
** Bug watch removed: gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues #832
   https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/832

** Bug watch removed: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #898
   https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/898

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

Title:
  External audio device shows up in the sound output options but the
  sound keeps being emitted from the internal laptop speaker, or none at
  all.

Status in PulseAudio:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Focal:
  In Progress
Status in pulseaudio source package in Groovy:
  Fix Released

Bug description:
  Ubuntu version: focal dev
  Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020
  Pulseaudio: 1:13.99.1-1ubuntu1
  Device CID: 201704-25503

  Steps to reproduce:

  1. Connect an audio interface. I tried with BT headphones and speakers as 
well as a USB microphone/output.
  2. Make sure it's the one selected as "Output device"
  3. Click "Test"
  -> the test sound outputs from the internal laptop speakers (NOK)
  4. Select "Speakers - Built-in Audio" as Output device and click "Test"
  -> the test sound outputs from the internal laptop speakers (OK)
  5. Try to switch back to the BT device and click Test
  -> same result as in step 3

  Tested with 2 different BT devices (one headset and one speaker) as
  well as a USB audio interface (Zoom H2N microphone).

  Attached are btmon logs captured during the procedure described above,
  and pactl logs capture after step 7.

  I was previously using 19.04 and 19.10 on this device and never
  experienced this kind of issue.

  Up to this morning, it was harder to connect the BT device, but once
  connected, the sound would output on it as expected. Now, the BT
  connection seems to work better, but I can't output the sound to the
  BT device...

  I tried to reboot the device, and also to suspend/resume, but in each
  case, the BT device can connect back, but the sound is still output
  from the internal laptop speakers, even when the BT device is selected
  in the Sound settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pieq   1566 F pulseaudio
   /dev/snd/pcmC0D0c:   pieq   1566 F...m pulseaudio
   /dev/snd/pcmC0D0p:   pieq   1566 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  5 22:15:50 2020
  InstallationDate: Installed on 2020-01-17 (48 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200116)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/23/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.14.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7370
  dmi.product.sku: 07E9
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1881549] Re: BCM43602 [14e4:43ba] Subsystem [1028:0020]: Upgraded to 20.04 and wifi broke

2020-06-13 Thread Mathew Hodson
** No longer affects: linux (Ubuntu Groovy)

** No longer affects: linux (Ubuntu Focal)

** No longer affects: linux (Ubuntu)

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

Title:
  BCM43602 [14e4:43ba] Subsystem [1028:0020]: Upgraded to 20.04 and wifi
  broke

Status in wpa package in Ubuntu:
  Fix Released
Status in wpa source package in Focal:
  Confirmed
Status in wpa source package in Groovy:
  Fix Released

Bug description:
  [Impact]

   * A driver supports FT (IEEE 802.11r-2008 or fast BSS transition (FT),
 also called fast roaming) if it either supports SME or the
 NL80211_CMD_UPDATE_FT_IES command. When selecting AKM suites,
 wpa_supplicant currently doesn't take into account whether or not either
 of those conditions are met. This can cause association failures, e.g.,
 when an AP supports both WPA-EAP and FT-EAP but the driver doesn't
 support FT (wpa_supplicant will decide to do FT-EAP since it is unaware
 the driver doesn't support it).

   * This is known to affect users at least users with popular chip-sets,
 such as BCM20703A1 or BCM4350 (notably present in the popular XPS 13/15
 laptops).

   * The upload fixes the bug by allowing an FT suite to be selected only
 when the driver also supports FT.

  [Test Case]

   * requires affected hardware and wpa_supplicant built with CONFIG_IEEE80211R
 and connecting to an AP supporting WPA-EAP and FT-EAP

  [Regression Potential]

   * a driver not advertising correctly its support for SME or the
 NL80211_CMD_UPDATE_FT_IES command via the drv_flags would be prevented from
 using FT but would still be able to connect to APs

  [Other Info]

   * Upstream fix: 
https://w1.fi/cgit/hostap/commit/?id=23dc196fde951b3d508f367a603cddffbd053490
   * Initial report: https://bugs.archlinux.org/task/63397
  ---

  Upgraded to 20.04 and the wifi broke.  It was working fine on 18.04.  Tried a 
variety of things with apw but nada.  /var/log attached
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1438 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-07-09 (329 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Dell Inc. XPS 15 9550
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic 
root=UUID=f73bcd37-31c3-4314-81cf-102bfd94a03e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-33-generic N/A
   linux-backports-modules-5.4.0-33-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-33-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-21 (12 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/12/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.13.1
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.13.1:bd12/12/2019:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9550
  dmi.product.sku: 06E4
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1881982] Re: Memory leak in parse_report()

2020-06-13 Thread Mathew Hodson
** Changed in: whoopsie (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Memory leak in parse_report()

Status in whoopsie package in Ubuntu:
  New

Bug description:
  Hi,

  I have found a security issue on whoopsie 0.2.69 and earlier.

  ## Vulnerability in whoopsie
  - whoopsie 0.2.69 and earlier have a memory leak vulnerability.
  - An attacker can cause a denial of service (application crash) via a crafted 
.crash file.

  ## Basic
  When a program has been crashed, Linux system tries to create a '.crash' file 
on '/var/crash/' directory with python script located in 
'/usr/share/apport/apport'.
  The file contains a series of system crash information including core dump, 
syslog, stack trace, memory map info, etc.
  A user is given read and write permission to the file.
  After then, whoopsie parses key-value pairs in ‘.crash’ file and encodes it 
into binary json (bson) format.
  Lastly, whoopsie forwards the data to a remotely connected Ubuntu error 
report system.

  ## Vulnerability
  We have found a memory leak vulnerability during the parsing the crash file, 
when a collision occurs on GHashTable through g_hash_table_insert().
  According to [1], if the key already exists in the GHashTable, its current 
value is replaced with the new value.
  If 'key_destory_func' and 'value_destroy_func' are supplied when creating the 
table, the old value and the passed key are freed using that function.
  Unfortunately, whoopsie does not handle the old value and the passed key when 
collision happens.
  If a crash file contains same repetitive key-value pairs, it leads to memory 
leak as much as the amount of repetition and results in denial-of-service.

  ## Attack
  1) Create a fake.crash file
  memory_leak_poc.py script measures an available memory and generates a 
malicious crash file that contains same repetitive key-value pairs as much as 
20% of the available memory size; 'ProblemType: Crash'.
  20% indicates arbitrary amount of the memory leakage.
  2) Before the attack, the script checks memory usage of whoopsie process with 
psutil
  3) It triggers the whoopsie to read the fake.crash file
  4) Then, it measures the memory usage of whoopsie process
  5) It results in denial-of-service and then other users can no longer report 
crash to the Ubuntu error report system.

  ## Mitigation
  We should use g_hash_table_new_full() with ‘key_destroy_func’ and 
‘value_destroy_func’ functions instead of g_hash_table_new().
  Otherwise, before g_hash_table_insert(), we should check the collision via 
g_hash_table_lookup_extended() and obtain pointer to the old value and remove 
it.

  Sincerely,

  [1] https://developer.gnome.org/glib/stable/glib-Hash-Tables.html#g
  -hash-table-insert

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

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


[Touch-packages] [Bug 1882042] Re: [SRU] Linux, Ubuntu, 18.4, CI, OLP15, PRTS, Audio/video is out of sync/lag when enter Suspend during playback

2020-06-08 Thread Mathew Hodson
** Changed in: pulseaudio (Ubuntu Bionic)
   Importance: Undecided => High

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

Title:
  [SRU] Linux,Ubuntu,18.4,CI,OLP15,PRTS, Audio/video is out of sync/lag
  when enter Suspend during playback

Status in HWE Next:
  New
Status in pulseaudio package in Ubuntu:
  New
Status in pulseaudio source package in Bionic:
  New

Bug description:
  [Impact]
  Users reported the audio and video is out of sync when entering suspend 
during playback on bionic.

  [Fix]
  The mainline pulseaudio already has the fix for this issue, and the fix is 
already in the eoan, focal and groovy, but it is not in the bionic.

  [Test Case]
  open a online video on the firefox, while it is playing, suspend the system, 
wait for 30 seconds, resume the system, the audio and video is still on the 
sync.

  [Regression Risk]
  Low, these 2 patches are already in the mainline pulseaudio, and already in 
the eoan, focal and groovy.

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

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


[Touch-packages] [Bug 1876055] Re: SRU: Backport 2.4.3-1ubuntu2 from groovy to focal/eoan/bionic/xenial for newer syscalls for core20 base

2020-05-22 Thread Mathew Hodson
** Tags added: upgrade-software-version

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

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

Title:
  SRU: Backport 2.4.3-1ubuntu2 from groovy to focal/eoan/bionic/xenial
  for newer syscalls for core20 base

Status in libseccomp package in Ubuntu:
  New

Bug description:
  [Impact]

  snap-confine from snapd uses libseccomp to filter various system calls
  for confinement. The current version in eoan/bionic/xenial (2.4.1) is
  missing knowledge of various system calls for various architectures.
  As such this causes strange issues like python snaps segfaulting
  (https://github.com/snapcore/core20/issues/48) or the inadvertent
  denial of system calls which should be permitted by the base policy
  (https://forum.snapcraft.io/t/getrlimit-blocked-by-seccomp-on-focal-
  arm64/17237).

  libseccomp in groovy is using the latest upstream base release (2.4.3)
  plus it includes a patch to add some missing aarch64 system calls
  (https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1877633).

  SRUing this version back to older stable releases allows libseccomp to
  operate correctly on all supported architectures.

  
  [Test Case]

  libseccomp includes a significant unit test suite that is run during
  the build and as part of autopkgtests. To verify the new aarch64
  system calls are resolved as expected the scmp_sys_resolver command
  can be used as well:

  $ scmp_sys_resolver -a aarch64 getrlimit
  163

  (whereas in the current version in focal this returns -10180 as
  libseccomp was not aware of this system-call at compile-time).

  As part of this SRU, the test suite in libseccomp has been patched to
  include a local copy of the architecture-specific kernel headers from
  the 5.4 kernel in focal *for all releases*, so that all system calls
  which are defined for the 5.4 kernel are known about *for the
  libseccomp test suite*. This allows all unit tests to pass on older
  releases as well and defaults the build to fail on unit test failures
  (whereas currently in xenial this has been overridden to ignore
  failures).

  
  [Regression Potential]

  This has a low regression potential due to significant testing with
  many packages that depend on libseccomp (lxc, qemu, snapd, apt, man
  etc) and none have shown any regression using this new version.

  Any possible regressions may include applications now seeing correct
  system call resolution whereas previously this would have failed, and
  so perhaps previous failures (which were erroneous) will now be
  permitted. However, this was always permitted previously by the policy
  anyway but just denied due to this bug so it is not a true regression
  as such.

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

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


[Touch-packages] [Bug 1879087] Re: dbus errors, frequent roaming and unstable connectivity

2020-05-22 Thread Mathew Hodson
** Changed in: wpa (Ubuntu Focal)
   Importance: Undecided => High

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

Title:
  dbus errors, frequent roaming and unstable connectivity

Status in wpa package in Ubuntu:
  Fix Committed
Status in wpa source package in Focal:
  Incomplete

Bug description:
  * Impact
  extra roaming events are been generated

  * Test case
  check the output of `journalctl -lu wpa_supplicant`, it should have warnings
  dbus: wpa_dbus_property_changed: no property RoamComplete in object 
/fi/w1/wpa_supplicant1/Interfaces/3

  the roaming events should not be too frequent

  * Regression potential
  check that wifi connection keep working correctly

  --

  When using this version of wpa_supplicant with my company
  WPA2-Enterprise wireless setup, I'm experiencing far too frequent
  roaming events (even when not moving around) accompanied by hiccups in
  connectivity. I also see these messages in the wpa_supplicant log:

  dbus: wpa_dbus_property_changed: no property RoamComplete in object 
/fi/w1/wpa_supplicant1/Interfaces/3
  dbus: wpa_dbus_property_changed: no property RoamTime in object 
/fi/w1/wpa_supplicant1/Interfaces/3
  dbus: wpa_dbus_property_changed: no property SessionLength in object 
/fi/w1/wpa_supplicant1/Interfaces/3

  Having done a little research, at least the dbus errors seem to be
  fixed by this commit upstream:

  
https://w1.fi/cgit/hostap/commit/wpa_supplicant/dbus/dbus_new.c?id=23d87687c2428f3b94865580b0d33e05c03e6756

  So I built a version of wpa_supplicant including this particular patch
  and installed on my machine. Apart from solving the dbus errors
  completely, it seems to have had a positive impact on the frequent
  roaming and unstable connectivity as well (I've run for a day with no
  burst of roaming events at all, where they used to happen every few
  minutes most of the time.)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: wpasupplicant 2:2.9-1ubuntu4
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Sat May 16 16:47:27 2020
  InstallationDate: Installed on 2020-05-12 (4 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1876238] Re: [Dell Inspiron 1525, SigmaTel STAC9228] No sound at all. Internal Speaker Not Detected. Dummy Output. After Upgrading From 19.10 to 20.04 LTS Focal

2020-05-22 Thread Mathew Hodson
*** This bug is a duplicate of bug 1876065 ***
https://bugs.launchpad.net/bugs/1876065

** This bug is no longer a duplicate of bug 1875252
   Ubuntu 20.04 LTS update causing no sound coming from built-in speakers 
** This bug has been marked a duplicate of bug 1876065
   After unplug headphones and plug them again no sound can be heard

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

Title:
  [Dell Inspiron 1525, SigmaTel STAC9228] No sound at all. Internal
  Speaker Not Detected. Dummy Output. After Upgrading From 19.10 to
  20.04 LTS Focal

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal speakers were working fine until I upgraded the system from
  19.10 LTS to 20.04 LTS on April 23, 2020.

  Uninstalled and reinstalled alsamixer and pavucontrol, but of no use.

  Killed pavucontrol and reloaded alsamixer numerous times, but of no
  use. (`pulseaudio -k && sudo alsa force-reload`)

  Waited for two kernel updates, but of no use. Presently on 5.4.0-29.

  Tried upgrading the kernel even up to 5.6, but of no use.

  The Intel sound card is not getting detected.

  Tried every trick like adding "options snd-hda-intel dmic_detect=0" in
  the /etc/modprobe.d/alsa-base.conf, but of no use.

  Out of the two external audio output sockets for headphone, one is
  working. So I can either connect a headphone or an external speaker to
  this jack to tide over the crisis for the time being.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  raj   10952 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May  1 09:54:23 2020
  InstallationDate: Installed on 2016-12-20 (1227 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  raj   10952 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [Inspiron 1525, SigmaTel STAC9228, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/27/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd06/27/2008:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 1525
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-04-26T17:25:43.583147

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

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


[Touch-packages] [Bug 1877580] Re: [Latitude 7490, Realtek ALC3246, Black Headphone Out, Front] No sound at all

2020-05-22 Thread Mathew Hodson
*** This bug is a duplicate of bug 1876065 ***
https://bugs.launchpad.net/bugs/1876065

** This bug is no longer a duplicate of bug 1879939
   Audio stopped working after 5.4.0-31 kernel update
** This bug has been marked a duplicate of bug 1876065
   After unplug headphones and plug them again no sound can be heard

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

Title:
  [Latitude 7490, Realtek ALC3246, Black Headphone Out, Front] No sound
  at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  After upgrade from 19.10 to 20.04 (xubuntu) I've lost the sound on the 
headphones.
  The internal loud speakers works ok when the headphones are not plugged in.

  More specifically:
  If I open the pavucontrol without the headphones plugged in I see that is 
correctly mentioning the output as Port: "Speakers (plugged-in)" and everything 
works ok, I have sound from the speakers.

  The moment I plug in the headphones, for a fraction of a second I can
  hear sound on the headphones, and then the output port switches to
  "headphones" which is the moment I lose the sound.

  The fraction that I hear the sound is when the jack is half-inserted
  and I get the sound on one channel only. When is fully inserted, the
  computer detects it and makes the switch.

  I've tried also in alsamixer all possibilities I could imagine,
  playing with mute/unmute and gain of each channel, with no success

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bnv1312 F pulseaudio
bnv   21367 F alsamixer
   /dev/snd/pcmC0D0c:   bnv1312 F...m pulseaudio
   /dev/snd/pcmC0D0p:   bnv1312 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Fri May  8 15:41:08 2020
  InstallationDate: Installed on 2019-08-08 (274 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bnv1312 F pulseaudio
bnv   21367 F alsamixer
   /dev/snd/pcmC0D0c:   bnv1312 F...m pulseaudio
   /dev/snd/pcmC0D0p:   bnv1312 F...m pulseaudio
  Symptom_Jack: Black Headphone Out, Front
  Symptom_Type: No sound at all
  Title: [Latitude 7490, Realtek ALC3246, Black Headphone Out, Front] No sound 
at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.13.1
  dmi.board.name: 0KP0FT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.13.1:bd11/08/2019:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0KP0FT:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7490
  dmi.product.sku: 081C
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1878327] Re: [Dell Inspiron 1525] Pulse audio update made internal speakers as Dummy Output

2020-05-19 Thread Mathew Hodson
*** This bug is a duplicate of bug 1876065 ***
https://bugs.launchpad.net/bugs/1876065

** Tags removed: regression-update
** Tags added: regression-release

** Tags removed: regression

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

Title:
  [Dell Inspiron 1525] Pulse audio update made internal speakers as
  Dummy Output

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I had already reported bug #1876238 where internal speakers are not
  detected but shown as Dummy Output after upgrading Ubuntu from 19.10
  to 20.04 LTS Focal.

  It was solved by this patch:
  https://launchpad.net/~kaihengfeng/+archive/ubuntu/fix-lp1869819

  The current PulseAudio update today reversed that again. Internal
  speakers are not being detected and are shown as Dummy Output.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.2
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  raj2016 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 13 09:02:53 2020
  InstallationDate: Installed on 2016-12-20 (1239 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/27/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd06/27/2008:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 1525
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant

2020-05-19 Thread Mathew Hodson
** Tags removed: regression-proposed

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

Title:
  [SRU] System can't detect external headset in the codec of Conexant

Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project bionic series:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Bionic:
  In Progress
Status in pulseaudio source package in Focal:
  Fix Released

Bug description:
  [Impact]
  In some hp's devices, there are two audio jacks(one headset and one 
headphone) in the audio interface which is using the codec of Conexant, and 
apparently it's not working, the system can't detect the headset in current 
codec.

  [Test Case]
  1. Insert 4 rings(3 stripes) headset into front audio port (headset icon)
  2. Check System Setting->Sound->Output

  [Expected result]
  Can detect external headset

  [Actual result]
  Only shows internal speaker.
  External headset microphone was detected.
  Another front audio port (earphone icon) works fine.

  [Regression Potential]
  Low.

  [Failure rate]
  100%

  [Additional information]
  system-product-name: HP EliteDesk 800 G5 SFF
  CPU: Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8x)
  GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:3e98] (rev 02)
  OS-version: 18.04
  kernel-version: 4.15.0-1065-oem
  pulseaudio-version: 1:11.1-1ubuntu7.2

  Upstream issue:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/272

  Ubuntu-Focal-Source:
  
https://code.launchpad.net/~hugh712/ubuntu/+source/pulseaudio/+git/pulseaudio/+ref/focal-1869819

  PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1869819

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1869819/+subscriptions

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


[Touch-packages] [Bug 1875605] Re: SRU the current 0.20.3 stable update

2020-05-12 Thread Mathew Hodson
** Changed in: libsecret (Ubuntu Focal)
   Importance: Undecided => Low

** Tags added: upgrade-software-version

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

Title:
   SRU the current 0.20.3 stable update

Status in libsecret package in Ubuntu:
  Fix Released
Status in libsecret source package in Focal:
  Fix Committed

Bug description:
  * Impact
  That's the current GNOME stable update, including some fixes
  https://gitlab.gnome.org/GNOME/libsecret/-/blob/master/NEWS

  * Test case

  The update is part of GNOME stable updates
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Check that using passwords in GNOME applications or gpg/ssh keys still
  work correctly

  * Regression potential

  There is a segfault fix for flapak portals, testing that usecase would
  be useful

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

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


[Touch-packages] [Bug 1877536] Re: BlueZ 5.54 release

2020-05-08 Thread Mathew Hodson
** Tags added: upgrade-software-version

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

Title:
  BlueZ 5.54 release

Status in bluez package in Ubuntu:
  In Progress

Bug description:
  Release BlueZ 5.54 to groovy

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

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


[Touch-packages] [Bug 1876065] Re: After unplug headphones and plug them again no sound can be heard

2020-05-08 Thread Mathew Hodson
** Changed in: pulseaudio (Ubuntu Focal)
   Importance: Undecided => High

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

Title:
  After unplug headphones and plug them again no sound can be heard

Status in pulseaudio package in Ubuntu:
  Fix Committed
Status in pulseaudio source package in Focal:
  Fix Committed

Bug description:
  * Impact
  Sound isn't automatically redirected to headphones when those are connected 
to a jack interface

  * Test case
  Disconnect the headsets
  Start your webbrowser/music player/video player and play some sound
  Connect the headsets to the jack interface

  -> the sound should be directly redirected to the plugged headsets

  * Regression potential
  Check that audio routing when connecting/disconnecting devices to the hack 
entry is working correctly

  

  After startup with headset plugged in they play sound nicely - no
  issue. When they are unplugged, the sound is switched to the speaker
  (laptop) - all good. However, when I plug the headset back there is no
  sound. I see the app on pavucontrol, the volume is fine - everything
  looks fine except there is no sound. I dumped output of "pactl list"
  command on startup (headset plugged), after unplugging the headset,
  and when it is plugged back. From the comparison of these outputs, it
  looks like the source has got muted after the headset is plugged.

  Source #1
   State: RUNNING
   Name: alsa_input.pci-_00_1f.3.analog-stereo
   Description: Built-in Audio Analog Stereo
   Driver: module-alsa-card.c
   Sample Specification: s16le 2ch 44100Hz
   Channel Map: front-left,front-right
   Owner Module: 7
   Mute: yes

  Attached three outputs:
  headset-in.txt - after startup with headset plugged - all fine.
  headset-out.txt - after unplugged headset - sound through the speaker - all 
fine.
  headset-back.txt - after plugged headset back - no sound.

  Any help greatly appreciated.

  Regards,
  Roman

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

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


[Touch-packages] [Bug 1876065] Re: After unplug headphones and plug them again no sound can be heard

2020-05-06 Thread Mathew Hodson
** Tags added: regression-release

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

Title:
  After unplug headphones and plug them again no sound can be heard

Status in pulseaudio package in Ubuntu:
  Fix Committed

Bug description:
  * Impact
  Sound isn't automatically redirected to headphones when those are connected 
to a jack interface

  * Test case
  Disconnect the headsets
  Start your webbrowser/music player/video player and play some sound
  Connect the headsets to the jack interface

  -> the sound should be directly redirected to the plugged headsets

  * Regression potential
  Check that audio routing when connecting/disconnecting devices to the hack 
entry is working correctly

  

  After startup with headset plugged in they play sound nicely - no
  issue. When they are unplugged, the sound is switched to the speaker
  (laptop) - all good. However, when I plug the headset back there is no
  sound. I see the app on pavucontrol, the volume is fine - everything
  looks fine except there is no sound. I dumped output of "pactl list"
  command on startup (headset plugged), after unplugging the headset,
  and when it is plugged back. From the comparison of these outputs, it
  looks like the source has got muted after the headset is plugged.

  Source #1
   State: RUNNING
   Name: alsa_input.pci-_00_1f.3.analog-stereo
   Description: Built-in Audio Analog Stereo
   Driver: module-alsa-card.c
   Sample Specification: s16le 2ch 44100Hz
   Channel Map: front-left,front-right
   Owner Module: 7
   Mute: yes

  Attached three outputs:
  headset-in.txt - after startup with headset plugged - all fine.
  headset-out.txt - after unplugged headset - sound through the speaker - all 
fine.
  headset-back.txt - after plugged headset back - no sound.

  Any help greatly appreciated.

  Regards,
  Roman

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

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


[Touch-packages] [Bug 1876570] Re: Could not resume from hibernation when swap is specified as device

2020-05-04 Thread Mathew Hodson
** Changed in: initramfs-tools (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Could not resume from hibernation when swap is specified as device

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  I originally experienced this on Pop!_OS but I have reproduced it on a
  freshly installed Ubuntu.

  1. Ubuntu 20.04 LTS
  2. initramfs-tools-core 0.136ubuntu6
  3. I expect the system to resume from hibernation when running pm_hibernate
  4. The system starts up anew when I try to resume

  I have setup a swap partition on /dev/vda2 in /etc/fstab. To enable
  hibernate I added the kernel parameter "resume=/dev/vda2" to
  GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub and run update-grub.

  From debugging initramfs it tries to follow a symbolic link

  DEV=$(readlink "$resume")
  (see /usr/share/initramfs-tools/scripts/local-premount/resume, line 35)

  which works well when swap is specified with uuid. When swap is
  specified as a device directly the readlink returns an empty string
  and the system does not resume from hibernation.

  To verify this I added the parameter -f to readlink and run "update-
  initramfs -u". The system now hibernates successfully.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: initramfs-tools 0.136ubuntu6
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May  3 13:26:02 2020
  InstallationDate: Installed on 2020-05-03 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: initramfs-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1559650] Re: gnome-shell crashed with SIGSEGV in ___vsnprintf_chk()

2020-05-02 Thread Mathew Hodson
** Changed in: libxau (Ubuntu Bionic)
   Status: Fix Committed => In Progress

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

Title:
  gnome-shell crashed with SIGSEGV in ___vsnprintf_chk()

Status in libxau package in Ubuntu:
  Fix Released
Status in libxau source package in Bionic:
  In Progress
Status in libxau source package in Eoan:
  Fix Released
Status in libxau source package in Focal:
  Fix Released

Bug description:
  [Impact]

  gnome-shell crashes a lot. Over 38000 times in bionic so far:
  https://errors.ubuntu.com/problem/00455200cd9fb890dacfe09b92c7bda2f6ad3af7

  [Test Case]

  None known yet. Just keeping an eye on the above link for regressions.

  [Regression Potential]

  Low. The same fix has been released to newer distros for the past 2
  years already.

  [Other Info]

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: gnome-shell 3.18.4-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5
  Uname: Linux 4.4.0-13-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Wed Mar 16 17:15:11 2016
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:

  InstallationDate: Installed on 2016-03-13 (6 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160311)
  ProcCmdline: gnome-shell --mode=gdm --wayland --display-server
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x7f1ff33f46ab <___vsnprintf_chk+107>: movb   
$0x0,(%r12)
   PC (0x7f1ff33f46ab) ok
   source "$0x0" ok
   destination "(%r12)" (0x) not located in a known VMA region (needed 
writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   ___vsnprintf_chk (s=0x0, maxlen=, flags=1, slen=, format=0x7f1fe54ccae5 "%s%s", args=args@entry=0x7f1fce502da8) at 
vsnprintf_chk.c:55
   ___snprintf_chk (s=, maxlen=, flags=, slen=, format=) at snprintf_chk.c:34
   XauFileName () from /usr/lib/x86_64-linux-gnu/libXau.so.6
   XauGetBestAuthByAddr () from /usr/lib/x86_64-linux-gnu/libXau.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
  Title: gnome-shell crashed with SIGSEGV in ___vsnprintf_chk()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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


[Touch-packages] [Bug 1442649] Re: nautilus trash doesn't include btrfs and zfs subvolumes

2020-05-02 Thread Mathew Hodson
** Bug watch added: gitlab.gnome.org/GNOME/glib/issues #251
   https://gitlab.gnome.org/GNOME/glib/issues/251

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

** Changed in: glib
   Status: Expired => Unknown

** Changed in: glib
 Remote watch: GNOME Bug Tracker #604015 => gitlab.gnome.org/GNOME/glib/issues 
#251

** Bug watch removed: GNOME Bug Tracker #604015
   https://gitlab.gnome.org/604015

** No longer affects: nautilus (Ubuntu)

** Bug watch added: gitlab.gnome.org/GNOME/gvfs/issues #236
   https://gitlab.gnome.org/GNOME/gvfs/issues/236

** Also affects: gvfs via
   https://gitlab.gnome.org/GNOME/gvfs/issues/236
   Importance: Unknown
   Status: Unknown

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

Title:
  nautilus trash doesn't include btrfs and zfs subvolumes

Status in GLib:
  Unknown
Status in gvfs:
  Unknown
Status in glib2.0 package in Ubuntu:
  Triaged
Status in gvfs package in Ubuntu:
  Triaged

Bug description:
  Files in `/path/to/subvolume/.Trash-1000` aren't listed in the global
  trash.

  Comment by bug triage team: comment 4 has a spot-on analysis of where
  this issue is coming from, an inconsistency between trash handling in
  gvfs and glib/gio.  The problem has been around for quite a while.

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

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


[Touch-packages] [Bug 1873777] Re: Update to 2.64.2

2020-04-30 Thread Mathew Hodson
** Tags added: upgrade-software-version

** Changed in: glib-networking (Ubuntu Focal)
   Importance: Undecided => High

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

Title:
  Update to 2.64.2

Status in glib-networking package in Ubuntu:
  Fix Released
Status in glib-networking source package in Focal:
  Fix Committed

Bug description:
  * Impact
  That's the current GNOME stable update, including some fixes
  https://gitlab.gnome.org/GNOME/glib-networking/-/blob/master/NEWS

  * Test case

  The update is part of GNOME stable updates
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Check that GNOME web still works correctly

  * Regression potential

  The update restore the TLS 1.0/1.1 protocols due to COVID-19, try to
  browse one of those websites from the GNOME browser

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

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


[Touch-packages] [Bug 1571506] Re: update-initramfs won't include firmware in /lib/firmware/updates

2020-04-29 Thread Mathew Hodson
** Changed in: initramfs-tools (Ubuntu)
   Importance: Undecided => Wishlist

** Summary changed:

- update-initramfs won't include firmware in /lib/firmware/updates
+ update-initramfs should include firmware from /lib/firmware/updates

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

Title:
  update-initramfs should include firmware from /lib/firmware/updates

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  according to the kernel doc
  
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/firmware_class/README

  Linux kernel will search firmware from
  "/lib/firmware/updates/" UTS_RELEASE,
  "/lib/firmware/updates",
  "/lib/firmware/" UTS_RELEASE,
  "/lib/firmware"

  But the add module function in initramfs-tools won't search the
  "/lib/firmware/updates".

  This problem applies to all Ubuntu releases.

  Attach patch to fix this.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: initramfs-tools 0.103ubuntu4.2
  ProcVersionSignature: Ubuntu 4.2.0-30.36~14.04.1-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-30-generic i686
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: i386
  CurrentDesktop: Unity
  Date: Mon Apr 18 14:24:29 2016
  InstallationDate: Installed on 2014-04-23 (725 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  PackageArchitecture: all
  SourcePackage: initramfs-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1873031] Re: 245.4-2ubuntu1 throws stderr messages on timesyncd restart in its dhcp hook

2020-04-28 Thread Mathew Hodson
** Changed in: chrony (Ubuntu)
   Importance: Undecided => High

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

Title:
  245.4-2ubuntu1 throws stderr messages on timesyncd restart in its dhcp
  hook

Status in chrony package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  In Progress

Bug description:
  systemd has broken this by the split of timesyncd.

  On a system that installed chrony (or other NTP servers) you'll have:

  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  VersionArchitecture Description
  
+++-=-==--===
  ii  chrony3.5-6ubuntu3   amd64Versatile implementation of 
the Network Time Protocol
  rc  systemd-timesyncd 245.4-4ubuntu1 amd64minimalistic service to 
synchronize local time with NTP servers

  That left this behind:
/etc/dhcp/dhclient-exit-hooks.d/timesyncd

  And if you now run a dhcp based time server push it will fail very
  badly.

  P.S. This is triggered by the chrony autopkgtests but not an issue in chrony 
yet it is in systemd.
  But due to that one can use [1] as easy reproducer, I wonder how systemd 
slipped by this issue in autopkgtest?

  It contains:
  systemctl try-restart systemd-timesyncd.service || true

  Which in the setup the system now has will trigger:
   sudo dhclient dummy0
  Failed to try-restart systemd-timesyncd.service: Unit 
systemd-timesyncd.service is masked.

  P.S. I'll harden the chrony test to not stumble over this but it
  should be revisited for systemd to provide a better fix than causing
  this message every time (maybe pre-check if it is enabled and
  unmasked)?

  [1]: https://git.launchpad.net/ubuntu/+source/chrony/tree/debian/tests
  /time-sources-from-dhcp-servers?h=ubuntu/focal-devel

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

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


[Touch-packages] [Bug 1733321] Re: network-manager ADT tests fail with on ppc64el with artful/linux 4.13.0.17.18

2020-04-28 Thread Mathew Hodson
** Changed in: network-manager (Ubuntu Bionic)
   Importance: Undecided => Medium

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

Title:
  network-manager ADT tests fail with on ppc64el with artful/linux
  4.13.0.17.18

Status in network-manager package in Ubuntu:
  New
Status in network-manager source package in Artful:
  Won't Fix
Status in network-manager source package in Bionic:
  Fix Committed
Status in network-manager source package in Disco:
  Won't Fix
Status in network-manager source package in Eoan:
  Fix Committed
Status in network-manager source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  The killswitches-no-urfkill autopkgtest fails sometimes because nmcli
  reports the old state when it's called right after rfkill
  block/unblock.

  ppc64el ADT log from failed testcase:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-artful/artful/ppc64el/n/network-
  manager/20171120_100719_28642@/log.gz

  Testcase output:
  -
  autopkgtest [10:04:48]: test killswitches-no-urfkill: [---
  make -C /lib/modules/4.13.0-17-generic/build 
KBUILD_SRC=/lib/modules/4.13.0-17-generic/build 
M=/tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests
  make[1]: Entering directory '/usr/src/linux-headers-4.13.0-17-generic'
    AR  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/built-in.o
    CC [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.o
    Building modules, stage 2.
    MODPOST 1 modules
    CC  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.mod.o
    LD [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.ko
  make[1]: Leaving directory '/usr/src/linux-headers-4.13.0-17-generic'
  ERROR: NM could not track device state.
  autopkgtest [10:05:20]: test killswitches-no-urfkill: ---]
  autopkgtest [10:05:20]: test killswitches-no-urfkill:  - - - - - - - - - - 
results - - - - - - - - - -
  killswitches-no-urfkill FAIL non-zero exit status 1
  -

  Package versions [artful/ppc64el]:
  network-manager 1.8.4-1ubuntu3
  linux-meta 4.13.0.17.18

  [Test Case]

  Assume that test vm and host are ppc64

  1. deploy ppc64 vm instance ( with 1 cpu )
  2. modprobe mac80211_hwsim ( may need to install linux-modules-extra- pkg )
  3. apt install network-manager rfkill
  4. modify /etc/netplan/[conf], renderer as NetworkManager
  5. netplan apply
  6. run below command
  - nmcli radio wifi ; rfkill list 0 ; rfkill block 0 ; rfkill list 0 ; nmcli 
radio wifi ; rfkill list 0 ; rfkill unblock 0 ; rfkill list 0 ; nmcli radio wifi

  enabled
  0: fake: Wireless LAN
  Soft blocked: no
  Hard blocked: no
  0: fake: Wireless LAN
  Soft blocked: yes
  Hard blocked: no
  enabled
  0: fake: Wireless LAN
  Soft blocked: yes
  Hard blocked: no
  0: fake: Wireless LAN
  Soft blocked: no
  Hard blocked: no
  enabled

  second 'enabled' should be 'disabled' but not updated properly.

  Adding "udevadm settle" in test file ( killswitches-no-urkfill ) between
  rfkill block/unblock and nmcli radio wifi will help updating status changes 
after rfkill block/unblock.

  [Regression Potential]

  This fixes testcase only, so any regression would cause incorrect test
  pass/fail, and might cause other missed bugs.

  [scope]

  this is needed for all releases.  Debian does not include this
  autopkgtest, and so does not need this fix.

  [Other Info]

  this is caused by the 'systemd-rfkill.socket' listening to rfkill, and
  starting up 'systemd-rfkill.service' for any change.  On a 1-cpu
  system (which all autopkgtest instances for network-manager are), this
  service startup sometimes blocks the uevent from reaching network-
  manager before the autopkgtest proceeds to call nmcli to check the
  rfkill status.  This causes the test case to fail.

  There are (at least) 2 options to fix this:
  1) stop/disable the 'systemd-rfkill.socket' at the start of the autopkgtest
  2) call udevadm settle between the rfkill block/unblock and the nmcli call to 
check status

  This does not need to be fixed outside the test case, as normal nmcli
  use should be not done by users in a script immediately after changing
  rfkill state, nor is there anything that either rfkill or nmcli could
  even do to address this (technically, nmcli could internally issue a
  'udevadm settle' every time it's called, but that seems paranoid and
  extreme).

  [original description]

  On ppc64el architecture, it was observed that a fix for systemd is
  also needed (see bug 1734908) for the testcase to be successful.

  # original test case

  2.1. Download network-manager package source code
  $ apt-get source network-manager

  2.2. Run killswitches-no-urfkill testcase
  $ cd network-manager-1.8.4
  $ sudo ./debian/tests/killswitches-no-urfkill

To 

[Touch-packages] [Bug 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant

2020-04-24 Thread Mathew Hodson
** Tags removed: verification-needed

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

Title:
  [SRU] System can't detect external headset in the codec of Conexant

Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project bionic series:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Bionic:
  Fix Committed
Status in pulseaudio source package in Focal:
  Fix Released

Bug description:
  [Impact]
  In some hp's devices, there are two audio jacks(one headset and one 
headphone) in the audio interface which is using the codec of Conexant, and 
apparently it's not working, the system can't detect the headset in current 
codec.

  [Test Case]
  1. Insert 4 rings(3 stripes) headset into front audio port (headset icon)
  2. Check System Setting->Sound->Output

  [Expected result]
  Can detect external headset

  [Actual result]
  Only shows internal speaker.
  External headset microphone was detected.
  Another front audio port (earphone icon) works fine.

  [Regression Potential]
  Low.

  [Failure rate]
  100%

  [Additional information]
  system-product-name: HP EliteDesk 800 G5 SFF
  CPU: Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8x)
  GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:3e98] (rev 02)
  OS-version: 18.04
  kernel-version: 4.15.0-1065-oem
  pulseaudio-version: 1:11.1-1ubuntu7.2

  Upstream issue:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/272

  Ubuntu-Focal-Source:
  
https://code.launchpad.net/~hugh712/ubuntu/+source/pulseaudio/+git/pulseaudio/+ref/focal-1869819

  PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1869819

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1869819/+subscriptions

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


[Touch-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.

2020-04-24 Thread Mathew Hodson
** No longer affects: systemd (Ubuntu)

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

Title:
  [nvidia] Automatic login fails and then all subsequent logins fail.
  Killing gnome-session-binary fixes it, or just not using automatic
  login.

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-session package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in gdm3 source package in Eoan:
  Confirmed
Status in gnome-session source package in Eoan:
  Confirmed
Status in nvidia-graphics-drivers-435 source package in Eoan:
  Confirmed

Bug description:
  I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM
  login screen (which I shouldn't; I have auto login enabled), and
  logging in just takes me back to the same user selection screen even
  though the password is correct.

  If I switch to a TTY and run `sudo pkill gnome-session-binary`,
  logging in through GDM starts working again.

  I should add that the do-release-upgrade was rocky; I did it in a
  terminal from within gnome, went away for a while, and when I
  returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo
  dpkg --configure -a` and complete the upgrade, but I don't know if
  something's still messed up due to that.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1)
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 28 19:55:42 2019
  DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit()
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4]
  InstallationDate: Installed on 2019-09-14 (13 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: MSI MS-7A67
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic 
root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.60
  dmi.board.asset.tag: Default string
  dmi.board.name: H270I GAMING PRO AC (MS-7A67)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7A67
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


[Touch-packages] [Bug 1849156] Re: systemd-timesyncd.service broken on upgrade to 19.10 if ntp was installed

2020-04-24 Thread Mathew Hodson
** No longer affects: ntp (Ubuntu)

** No longer affects: ntp (Ubuntu Eoan)

** No longer affects: ntp (Ubuntu Focal)

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

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

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

Title:
  systemd-timesyncd.service broken on upgrade to 19.10 if ntp was
  installed

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Eoan:
  Confirmed
Status in systemd source package in Focal:
  Fix Released
Status in systemd package in Debian:
  Unknown

Bug description:
  Ubuntu 19.10's systemd package introduced /lib/systemd/system/systemd-
  timesyncd.service.d/disable-with-time-daemon.conf.  This prevents
  systemd-timesyncd.service from starting if the ntp package has been
  installed.  However, ntp.service has a Conflicts directive for
  systemd-timesyncd.service.  If both services are enabled, neither will
  start on boot.  This breaks upgrades from < 19.10 to 19.10 for systems
  that have both ntp and systemd installed.

  Possible workarounds:

  - Uninstall ntp
  - Disable systemd-timesyncd.service

  % lsb_release -rd
  Description:Ubuntu 19.10
  Release:19.10

  % apt-cache policy systemd
  systemd:
Installed: 242-7ubuntu3
Candidate: 242-7ubuntu3
Version table:
   *** 242-7ubuntu3 500
  500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu eoan/main amd64 
Packages
  100 /var/lib/dpkg/status

  % apt-cache policy ntp
  ntp:
Installed: 1:4.2.8p12+dfsg-3ubuntu2
Candidate: 1:4.2.8p12+dfsg-3ubuntu2
Version table:
   *** 1:4.2.8p12+dfsg-3ubuntu2 500
  500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu eoan/universe 
amd64 Packages
  100 /var/lib/dpkg/status

  % dpkg -S 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
  systemd: 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf

  % sudo systemctl status ntp
  ● ntp.service - Network Time Service
 Loaded: loaded (/lib/systemd/system/ntp.service; enabled; vendor preset: 
enabled)
 Active: inactive (dead)
   Docs: man:ntpd(8)

  % sudo systemctl status systemd-timesyncd.service
  ● systemd-timesyncd.service - Network Time Synchronization
 Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled; 
vendor preset: enabled)
Drop-In: /lib/systemd/system/systemd-timesyncd.service.d
 └─disable-with-time-daemon.conf
 Active: inactive (dead)
  Condition: start condition failed at Mon 2019-10-21 12:05:38 EDT; 29s ago
   Docs: man:systemd-timesyncd.service(8)

  Oct 21 12:05:38 ubuntu systemd[1]: Condition check resulted in Network
  Time Synchronization being skipped.

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

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


[Touch-packages] [Bug 1849156] Re: systemd-timesyncd.service broken on upgrade to 19.10 if ntp was installed

2020-04-23 Thread Mathew Hodson
** Bug watch added: Debian Bug tracker #947936
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947936

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

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

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

Title:
  systemd-timesyncd.service broken on upgrade to 19.10 if ntp was
  installed

Status in ntp package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Released
Status in ntp source package in Eoan:
  Confirmed
Status in systemd source package in Eoan:
  Confirmed
Status in ntp source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  Fix Released
Status in systemd package in Debian:
  Unknown

Bug description:
  Ubuntu 19.10's systemd package introduced /lib/systemd/system/systemd-
  timesyncd.service.d/disable-with-time-daemon.conf.  This prevents
  systemd-timesyncd.service from starting if the ntp package has been
  installed.  However, ntp.service has a Conflicts directive for
  systemd-timesyncd.service.  If both services are enabled, neither will
  start on boot.  This breaks upgrades from < 19.10 to 19.10 for systems
  that have both ntp and systemd installed.

  Possible workarounds:

  - Uninstall ntp
  - Disable systemd-timesyncd.service

  % lsb_release -rd
  Description:Ubuntu 19.10
  Release:19.10

  % apt-cache policy systemd
  systemd:
Installed: 242-7ubuntu3
Candidate: 242-7ubuntu3
Version table:
   *** 242-7ubuntu3 500
  500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu eoan/main amd64 
Packages
  100 /var/lib/dpkg/status

  % apt-cache policy ntp
  ntp:
Installed: 1:4.2.8p12+dfsg-3ubuntu2
Candidate: 1:4.2.8p12+dfsg-3ubuntu2
Version table:
   *** 1:4.2.8p12+dfsg-3ubuntu2 500
  500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu eoan/universe 
amd64 Packages
  100 /var/lib/dpkg/status

  % dpkg -S 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
  systemd: 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf

  % sudo systemctl status ntp
  ● ntp.service - Network Time Service
 Loaded: loaded (/lib/systemd/system/ntp.service; enabled; vendor preset: 
enabled)
 Active: inactive (dead)
   Docs: man:ntpd(8)

  % sudo systemctl status systemd-timesyncd.service
  ● systemd-timesyncd.service - Network Time Synchronization
 Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled; 
vendor preset: enabled)
Drop-In: /lib/systemd/system/systemd-timesyncd.service.d
 └─disable-with-time-daemon.conf
 Active: inactive (dead)
  Condition: start condition failed at Mon 2019-10-21 12:05:38 EDT; 29s ago
   Docs: man:systemd-timesyncd.service(8)

  Oct 21 12:05:38 ubuntu systemd[1]: Condition check resulted in Network
  Time Synchronization being skipped.

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

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


[Touch-packages] [Bug 1849156] Re: systemd-timesyncd.service broken on upgrade to 19.10 if ntp was installed

2020-04-23 Thread Mathew Hodson
** Tags added: dist-upgrade

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

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

Title:
  systemd-timesyncd.service broken on upgrade to 19.10 if ntp was
  installed

Status in ntp package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Released
Status in ntp source package in Eoan:
  Confirmed
Status in systemd source package in Eoan:
  Confirmed
Status in ntp source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  Fix Released
Status in systemd package in Debian:
  Unknown

Bug description:
  Ubuntu 19.10's systemd package introduced /lib/systemd/system/systemd-
  timesyncd.service.d/disable-with-time-daemon.conf.  This prevents
  systemd-timesyncd.service from starting if the ntp package has been
  installed.  However, ntp.service has a Conflicts directive for
  systemd-timesyncd.service.  If both services are enabled, neither will
  start on boot.  This breaks upgrades from < 19.10 to 19.10 for systems
  that have both ntp and systemd installed.

  Possible workarounds:

  - Uninstall ntp
  - Disable systemd-timesyncd.service

  % lsb_release -rd
  Description:Ubuntu 19.10
  Release:19.10

  % apt-cache policy systemd
  systemd:
Installed: 242-7ubuntu3
Candidate: 242-7ubuntu3
Version table:
   *** 242-7ubuntu3 500
  500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu eoan/main amd64 
Packages
  100 /var/lib/dpkg/status

  % apt-cache policy ntp
  ntp:
Installed: 1:4.2.8p12+dfsg-3ubuntu2
Candidate: 1:4.2.8p12+dfsg-3ubuntu2
Version table:
   *** 1:4.2.8p12+dfsg-3ubuntu2 500
  500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu eoan/universe 
amd64 Packages
  100 /var/lib/dpkg/status

  % dpkg -S 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
  systemd: 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf

  % sudo systemctl status ntp
  ● ntp.service - Network Time Service
 Loaded: loaded (/lib/systemd/system/ntp.service; enabled; vendor preset: 
enabled)
 Active: inactive (dead)
   Docs: man:ntpd(8)

  % sudo systemctl status systemd-timesyncd.service
  ● systemd-timesyncd.service - Network Time Synchronization
 Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled; 
vendor preset: enabled)
Drop-In: /lib/systemd/system/systemd-timesyncd.service.d
 └─disable-with-time-daemon.conf
 Active: inactive (dead)
  Condition: start condition failed at Mon 2019-10-21 12:05:38 EDT; 29s ago
   Docs: man:systemd-timesyncd.service(8)

  Oct 21 12:05:38 ubuntu systemd[1]: Condition check resulted in Network
  Time Synchronization being skipped.

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

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


[Touch-packages] [Bug 1863590] Re: Chrony test hangs with libpcap2 1:2.31-1

2020-04-23 Thread Mathew Hodson
bubblewrap (0.4.0-1ubuntu3) focal; urgency=medium

  * d/p/update-output-patterns-libcap-2.29.patch: cherry-pick fix proposed
fix to capability drop-related tests, which broke with newer libcap2.

 -- Łukasz 'sil2100' Zemczak   Wed, 26 Feb
2020 21:39:11 +0100

** No longer affects: chrony (Ubuntu)

** Also affects: bubblewrap (Ubuntu)
   Importance: Undecided
   Status: New

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

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

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

Title:
  Chrony test hangs with libpcap2 1:2.31-1

Status in bubblewrap package in Ubuntu:
  Fix Released
Status in libcap2 package in Ubuntu:
  Fix Released
Status in bubblewrap package in Debian:
  Fix Released
Status in libcap2 package in Debian:
  Fix Released

Bug description:
  Tests are blocking and failing eventually with a timeout.
  Hits all architectures and is reproducible.

  Locally reproducible in autopkgtest:

  sudo ~/work/autopkgtest/autopkgtest/runner/autopkgtest --no-built-
  binaries --apt-upgrade --apt-pocket=proposed=src:libpcap2 --shell-fail
  chrony_3.5-5ubuntu1.dsc -- qemu --qemu-options='-cpu host' --ram-
  size=2048 --cpus 2 ~/work/autopkgtest-focal-amd64.img

  
  Seems to be a block on network on __skb_wait_for_more_packets

  $cat /proc/3833/wchan
  __skb_wait_for_more_packets

  From strace POV that is a wait in accept that does not unblock:

  $ sudo strace -rT -p 3833
  strace: Process 3833 attached
   0.00 accept(6, NULL, NULL
  

  The logs are no help:
  /tmp/autopkgtest.epy1pq/upstream-simulation-test-suite-stderr => empty
  /tmp/autopkgtest.epy1pq/upstream-simulation-test-suite-stdout => matches the 
console

  $ cat /tmp/autopkgtest.epy1pq/upstream-simulation-test-suite-stdout
  make: Entering directory '/tmp/autopkgtest.epy1pq/autopkgtest_tmp'
  cc -O2 -Wall -g -fPIC   -c -o client.o client.c
  cc -O2 -Wall -g -fPIC -shared -o clknetsim.so client.o  -ldl -lm
  g++ -O2 -Wall -g -fPIC   -c -o clock.o clock.cc
  g++ -O2 -Wall -g -fPIC   -c -o node.o node.cc
  g++ -O2 -Wall -g -fPIC   -c -o generator.o generator.cc
  g++ -O2 -Wall -g -fPIC   -c -o network.o network.cc
  g++ -O2 -Wall -g -fPIC   -c -o server.o server.cc
  g++ -O2 -Wall -g -fPIC   -c -o stats.o stats.cc
  g++ -O2 -Wall -g -fPIC -o clknetsim clock.o node.o generator.o network.o 
server.o stats.o
  make: Leaving directory '/tmp/autopkgtest.epy1pq/autopkgtest_tmp'
  001-defaults
  

  Noisy PS output:

  4 0 506   1  20   0   2600  1920 -  Ss   ttyS1  0:00 
/bin/sh
  1 03690 506  20   0   2600   128 -  S+   ttyS1  0:00  \_ 
/bin/sh
  4 036913690  20   0   8172  3660 -  S+   ttyS1  0:00  
\_ su -s /bin/bash ubuntu -c set -e; export USER=`id -nu`; . /etc/profile 
>/dev/null 2>&1 || true;  . ~/.profile
   >/dev/null 2>&1 || true; buildtree="/tmp/autopkgtest.epy1pq/build.KhE/src"; 
mkdir -p -m 1777 -- 
"/tmp/autopkgtest.epy1pq/upstream-simulation-test-suite-artifacts"; export 
AUTOPKGTEST_ARTIFA
  CTS="/tmp/autopkgtest.epy1pq/upstream-simulation-test-suite-artifacts"; 
export ADT_ARTIFACTS="$AUTOPKGTEST_ARTIFACTS"; mkdir -p -m 755 
"/tmp/autopkgtest.epy1pq/autopkgtest_tmp"; export AUTOP
  KGTEST_TMP="/tmp/autopkgtest.epy1pq/autopkgtest_tmp"; export 
ADTTMP="$AUTOPKGTEST_TMP"; export DEBIAN_FRONTEND=noninteractive; export 
LANG=C.UTF-8; export DEB_BUILD_OPTIONS=parallel=2; unset
   LANGUAGE LC_CTYPE LC_NUMERIC LC_TIME LC_COLLATE   LC_MONETARY LC_MESSAGES 
LC_PAPER LC_NAME LC_ADDRESS   LC_TELEPHONE LC_MEASUREMENT LC_IDENTIFICATION 
LC_ALL;rm -f /tmp/autopkgtest_script_pi
  d; set -C; echo $$ > /tmp/autopkgtest_script_pid; set +C; trap "rm -f 
/tmp/autopkgtest_script_pid" EXIT INT QUIT PIPE; cd "$buildtree"; chmod +x 
/tmp/autopkgtest.epy1pq/build.KhE/src/debian/
  tests/upstream-simulation-test-suite; touch 
/tmp/autopkgtest.epy1pq/upstream-simulation-test-suite-stdout 
/tmp/autopkgtest.epy1pq/upstream-simulation-test-suite-stderr; 
/tmp/autopkgtest.epy1
  pq/build.KhE/src/debian/tests/upstream-simulation-test-suite 2> >(tee -a 
/tmp/autopkgtest.epy1pq/upstream-simulation-test-suite-stderr >&2) > >(tee -a 
/tmp/autopkgtest.epy1pq/upstream-simula
  tion-test-suite-stdout);
  4  100037203691  20   0   8608  3852 do_wai Ss   ?  0:00  
\_ bash -c set -e; export USER=`id -nu`; . /etc/profile >/dev/null 2>&1 || 
true;  . ~/.profile >/dev/null 2>
  &1 || true; buildtree="/tmp/autopkgtest.epy1pq/build.KhE/src"; mkdir -p -m 
1777 -- "/tmp/autopkgtest.epy1pq/upstream-simulation-test-suite-artifacts"; 
export AUTOPKGTEST_ARTIFACTS="/tmp/auto
  pkgtest.epy1pq/upstream-simulation-test-suite-artifacts"; export 
ADT_ARTIFACTS="$AUTOPKGTEST_ARTIFACTS"; mkdir -p -m 755 
"/tmp/autopkgtest.epy1pq/autopkgtest_tmp"; export AUTOPKGTEST_TMP="/t
  

[Touch-packages] [Bug 1873031] Re: 245.4-2ubuntu1 throws stderr messages on timesyncd restart in its dhcp hook

2020-04-23 Thread Mathew Hodson
** No longer affects: systemd (Ubuntu Eoan)

** No longer affects: systemd (Ubuntu Bionic)

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

Title:
  245.4-2ubuntu1 throws stderr messages on timesyncd restart in its dhcp
  hook

Status in chrony package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  In Progress

Bug description:
  systemd has broken this by the split of timesyncd.

  On a system that installed chrony (or other NTP servers) you'll have:

  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  VersionArchitecture Description
  
+++-=-==--===
  ii  chrony3.5-6ubuntu3   amd64Versatile implementation of 
the Network Time Protocol
  rc  systemd-timesyncd 245.4-4ubuntu1 amd64minimalistic service to 
synchronize local time with NTP servers

  That left this behind:
/etc/dhcp/dhclient-exit-hooks.d/timesyncd

  And if you now run a dhcp based time server push it will fail very
  badly.

  P.S. This is triggered by the chrony autopkgtests but not an issue in chrony 
yet it is in systemd.
  But due to that one can use [1] as easy reproducer, I wonder how systemd 
slipped by this issue in autopkgtest?

  It contains:
  systemctl try-restart systemd-timesyncd.service || true

  Which in the setup the system now has will trigger:
   sudo dhclient dummy0
  Failed to try-restart systemd-timesyncd.service: Unit 
systemd-timesyncd.service is masked.

  P.S. I'll harden the chrony test to not stumble over this but it
  should be revisited for systemd to provide a better fix than causing
  this message every time (maybe pre-check if it is enabled and
  unmasked)?

  [1]: https://git.launchpad.net/ubuntu/+source/chrony/tree/debian/tests
  /time-sources-from-dhcp-servers?h=ubuntu/focal-devel

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

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


[Touch-packages] [Bug 1871185] Re: urls in ubuntu-bugs dialog not really clickable

2020-04-23 Thread Mathew Hodson
** Changed in: apport (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  urls in ubuntu-bugs dialog not really clickable

Status in apport package in Ubuntu:
  In Progress

Bug description:
  when ubuntu-bug report suggests filing a bug report directly in
  launchpad for snap packages, the displayed url is clickable but the
  url stops at the first + symbol. see attachment.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: apport 2.20.11-0ubuntu8.8
  ProcVersionSignature: Ubuntu 5.3.0-45.37-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.11-0ubuntu8.8
  Architecture: amd64
  CrashReports: 640:1000:124:8919925:2020-03-29 20:16:13.456640958 
+0200:2020-03-29 20:16:14.456640958 
+0200:/var/crash/_usr_bin_python3.7.1000.crash
  CurrentDesktop: XFCE
  Date: Mon Apr  6 19:50:16 2020
  InstallationDate: Installed on 2020-03-18 (18 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1559650] Re: gnome-shell crashed with SIGSEGV in ___vsnprintf_chk()

2020-04-21 Thread Mathew Hodson
** No longer affects: gnome-shell (Ubuntu)

** Project changed: gnome-shell => ubuntu-translations

** No longer affects: ubuntu-translations

** Bug watch removed: gitlab.gnome.org/GNOME/gnome-shell/-/issues #447
   https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/447

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

Title:
  gnome-shell crashed with SIGSEGV in ___vsnprintf_chk()

Status in libxau package in Ubuntu:
  Fix Released
Status in libxau source package in Bionic:
  Fix Committed
Status in libxau source package in Eoan:
  Fix Released
Status in libxau source package in Focal:
  Fix Released

Bug description:
  [Impact]

  gnome-shell crashes a lot. Over 38000 times in bionic so far:
  https://errors.ubuntu.com/problem/00455200cd9fb890dacfe09b92c7bda2f6ad3af7

  [Test Case]

  None known yet. Just keeping an eye on the above link for regressions.

  [Regression Potential]

  Low. The same fix has been released to newer distros for the past 2
  years already.

  [Other Info]

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: gnome-shell 3.18.4-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5
  Uname: Linux 4.4.0-13-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Wed Mar 16 17:15:11 2016
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:

  InstallationDate: Installed on 2016-03-13 (6 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160311)
  ProcCmdline: gnome-shell --mode=gdm --wayland --display-server
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x7f1ff33f46ab <___vsnprintf_chk+107>: movb   
$0x0,(%r12)
   PC (0x7f1ff33f46ab) ok
   source "$0x0" ok
   destination "(%r12)" (0x) not located in a known VMA region (needed 
writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   ___vsnprintf_chk (s=0x0, maxlen=, flags=1, slen=, format=0x7f1fe54ccae5 "%s%s", args=args@entry=0x7f1fce502da8) at 
vsnprintf_chk.c:55
   ___snprintf_chk (s=, maxlen=, flags=, slen=, format=) at snprintf_chk.c:34
   XauFileName () from /usr/lib/x86_64-linux-gnu/libXau.so.6
   XauGetBestAuthByAddr () from /usr/lib/x86_64-linux-gnu/libXau.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
  Title: gnome-shell crashed with SIGSEGV in ___vsnprintf_chk()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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


[Touch-packages] [Bug 1856054] Re: pulseaudio now depends on libsnapd-glib1

2020-04-21 Thread Mathew Hodson
pulseaudio 1:11.1-1ubuntu7.5 with the new dependency was republished in
bug #1781428

** Summary changed:

- pulseaudio now depends on libsnapd-glib1 which recommends snapd
+ pulseaudio now depends on libsnapd-glib1

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

Title:
  pulseaudio now depends on libsnapd-glib1

Status in pulseaudio package in Ubuntu:
  Won't Fix

Bug description:
  The latest update for pulseaudio (1:11.1-1ubuntu7.5) in bionic now has
  libsnapd-glib1 as a dependency.

  This is complete and utter nonsense. I do not want cascading
  dependencies that have no business being installed on the systems I
  manage.

  Please rectify this at once.

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

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


[Touch-packages] [Bug 1781428] Re: please enable snap mediation support

2020-04-21 Thread Mathew Hodson
** Changed in: pulseaudio (Ubuntu)
   Importance: Undecided => High

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

Title:
  please enable snap mediation support

Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  Fix Released
Status in pulseaudio source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  Ubuntu 16.10 added rudimentary snap support to disable audio recording if the 
connecting process was a snap. By Ubuntu 18.04, something changed in the build 
resulting in 'Enable Snappy support: no' with audio recording no longer being 
mediated by pulseaudio (access to the pulseaudio socket continued to be 
mediated by snapd's apparmor policy). This resulted in any application with the 
pulseaudio interface connected to be able to also record. Ubuntu 16.04 never 
had mediation patches and always allowed recording when the pulseaudio 
interface was connected.

  To correct this situation but not regress existing behavior, Ubuntu
  19.04's pulseaudio was updated patch to allow playback to all
  connected clients (snaps or not), record by classic snaps (see bug
  1787324) and record by strict mode snaps if either the pulseaudio or
  new-in-snapd-2.41 audio-record interfaces were connected. With this
  change, snapd is in a position to migrate snaps to the new audio-
  playback and audio-record interfaces and properly mediate audio
  recording (see https://forum.snapcraft.io/t/upcoming-pulseaudio-
  interface-deprecation/13418).

  The patch to pulseaudio consists of adding a module, enabling it in
  default.pa and then when it is enabled, pulseaudio when faced with a
  record operation will, when the connecting process is a snap (ie, its
  security label (ie, apparmor label) starts with 'snap.'), query snapd
  via its control socket to ask if the snap is classic and if not,
  whether the pulseaudio or audio-record interfaces are connected.
  Adjusting pulseaudio in the manner does not require coordination with
  any release of snapd. It does need a newer version of snapd-glib,
  which was recently updated to 1.49 in the last SRU.

  [Test Case]

  IMPORTANT: if updating pulseaudio while the session is running, either
  need to reboot for the test or kill pulseaudio so it can restart with
  the new snap policy

  For unconfined applications:
  $ paplay /usr/share/sounds/alsa/Noise.wav && echo "yes"
  yes

  $ rm -f /tmp/out.wav ; parecord /tmp/out.wav && echo "yes"  # ctrl-c to stop 
recording
  ^Cyes

  $ paplay /tmp/out.wav && echo "yes"
  yes

  For confined, non-snap applications:
  $ sudo apt-get install evince

  $ aa-exec -p /usr/bin/evince -- paplay
  /usr/share/sounds/alsa/Noise.wav && echo yes

  $ rm -f /tmp/out.wav ; aa-exec -p /usr/bin/evince -- parecord /tmp/out.wav && 
echo "yes"  # ctrl-c to stop recording
  ^Cyes

  $ aa-exec -p /usr/bin/evince -- paplay /tmp/out.wav && echo "yes"
  yes

  For classic snaps:
  $ sudo snap install test-snapd-classic-confinement --classic

  $ snap run --shell test-snapd-classic-confinement

  $ cat /proc/self/attr/current   # verify we are classic confined
  snap.test-snapd-classic-confinement.test-snapd-classic-confinement (complain)

  $ paplay /usr/share/sounds/alsa/Noise.wav && echo "yes"
  yes

  $ rm -f /tmp/out.wav ; parecord /tmp/out.wav && echo "yes"  # ctrl-c to stop 
recording
  ^Cyes

  $ paplay /tmp/out.wav && echo "yes"
  yes

  $ exit # out of snap run --shell

  For strict snaps with pulseaudio:
  $ sudo snap install test-snapd-pulseaudio --edge
  $ sudo snap connect test-snapd-pulseaudio:pulseaudio

  $ snap connections test-snapd-pulseaudio
  Interface   Plug  Slot Notes
  pulseaudio  test-snapd-pulseaudio:pulseaudio  :pulseaudio  -

  $ test-snapd-pulseaudio.play --help  # ensure SNAP dirs are created
  ...

  $ sudo cp /usr/share/sounds/alsa/Noise.wav /var/snap/test-snapd-
  pulseaudio/common/

  $ test-snapd-pulseaudio.play /var/snap/test-snapd-pulseaudio/common/Noise.wav 
&& echo yes
  xcb_connection_has_error() returned true
  yes

  (note, the xcb_connection_has_error() message is due to the x11
  interface not being connected which is unrelated to mediation. x11 is
  left out to ensure that just audio-playback/audio-record are tested)

  $ test-snapd-pulseaudio.record /tmp/out.wav && echo yes # should pass
  ...
  ^Cyes

  $ test-snapd-pulseaudio.play /tmp/out.wav && echo yes
  ...
  yes

  For strict snaps with audio-playback/audio-record:
  $ sudo snap refresh core --candidate # make sure have 2.41. 'install' on 16.04
  $ sudo snap install test-snapd-audio-record --edge

  $ snap connections test-snapd-audio-record  # record not connected
  Interface   PlugSlot Notes
  audio-playback  test-snapd-audio-record:audio-playback  :audio-playback  -
  

[Touch-packages] [Bug 1781428] Re: please enable snap mediation support

2020-04-20 Thread Mathew Hodson
** Bug watch removed: freedesktop.org Bugzilla #95135
   https://bugs.freedesktop.org/show_bug.cgi?id=95135

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

Title:
  please enable snap mediation support

Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  Fix Committed
Status in pulseaudio source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  Ubuntu 16.10 added rudimentary snap support to disable audio recording if the 
connecting process was a snap. By Ubuntu 18.04, something changed in the build 
resulting in 'Enable Snappy support: no' with audio recording no longer being 
mediated by pulseaudio (access to the pulseaudio socket continued to be 
mediated by snapd's apparmor policy). This resulted in any application with the 
pulseaudio interface connected to be able to also record. Ubuntu 16.04 never 
had mediation patches and always allowed recording when the pulseaudio 
interface was connected.

  To correct this situation but not regress existing behavior, Ubuntu
  19.04's pulseaudio was updated patch to allow playback to all
  connected clients (snaps or not), record by classic snaps (see bug
  1787324) and record by strict mode snaps if either the pulseaudio or
  new-in-snapd-2.41 audio-record interfaces were connected. With this
  change, snapd is in a position to migrate snaps to the new audio-
  playback and audio-record interfaces and properly mediate audio
  recording (see https://forum.snapcraft.io/t/upcoming-pulseaudio-
  interface-deprecation/13418).

  The patch to pulseaudio consists of adding a module, enabling it in
  default.pa and then when it is enabled, pulseaudio when faced with a
  record operation will, when the connecting process is a snap (ie, its
  security label (ie, apparmor label) starts with 'snap.'), query snapd
  via its control socket to ask if the snap is classic and if not,
  whether the pulseaudio or audio-record interfaces are connected.
  Adjusting pulseaudio in the manner does not require coordination with
  any release of snapd. It does need a newer version of snapd-glib,
  which was recently updated to 1.49 in the last SRU.

  [Test Case]

  IMPORTANT: if updating pulseaudio while the session is running, either
  need to reboot for the test or kill pulseaudio so it can restart with
  the new snap policy

  For unconfined applications:
  $ paplay /usr/share/sounds/alsa/Noise.wav && echo "yes"
  yes

  $ rm -f /tmp/out.wav ; parecord /tmp/out.wav && echo "yes"  # ctrl-c to stop 
recording
  ^Cyes

  $ paplay /tmp/out.wav && echo "yes"
  yes

  For confined, non-snap applications:
  $ sudo apt-get install evince

  $ aa-exec -p /usr/bin/evince -- paplay
  /usr/share/sounds/alsa/Noise.wav && echo yes

  $ rm -f /tmp/out.wav ; aa-exec -p /usr/bin/evince -- parecord /tmp/out.wav && 
echo "yes"  # ctrl-c to stop recording
  ^Cyes

  $ aa-exec -p /usr/bin/evince -- paplay /tmp/out.wav && echo "yes"
  yes

  For classic snaps:
  $ sudo snap install test-snapd-classic-confinement --classic

  $ snap run --shell test-snapd-classic-confinement

  $ cat /proc/self/attr/current   # verify we are classic confined
  snap.test-snapd-classic-confinement.test-snapd-classic-confinement (complain)

  $ paplay /usr/share/sounds/alsa/Noise.wav && echo "yes"
  yes

  $ rm -f /tmp/out.wav ; parecord /tmp/out.wav && echo "yes"  # ctrl-c to stop 
recording
  ^Cyes

  $ paplay /tmp/out.wav && echo "yes"
  yes

  $ exit # out of snap run --shell

  For strict snaps with pulseaudio:
  $ sudo snap install test-snapd-pulseaudio --edge
  $ sudo snap connect test-snapd-pulseaudio:pulseaudio

  $ snap connections test-snapd-pulseaudio
  Interface   Plug  Slot Notes
  pulseaudio  test-snapd-pulseaudio:pulseaudio  :pulseaudio  -

  $ test-snapd-pulseaudio.play --help  # ensure SNAP dirs are created
  ...

  $ sudo cp /usr/share/sounds/alsa/Noise.wav /var/snap/test-snapd-
  pulseaudio/common/

  $ test-snapd-pulseaudio.play /var/snap/test-snapd-pulseaudio/common/Noise.wav 
&& echo yes
  xcb_connection_has_error() returned true
  yes

  (note, the xcb_connection_has_error() message is due to the x11
  interface not being connected which is unrelated to mediation. x11 is
  left out to ensure that just audio-playback/audio-record are tested)

  $ test-snapd-pulseaudio.record /tmp/out.wav && echo yes # should pass
  ...
  ^Cyes

  $ test-snapd-pulseaudio.play /tmp/out.wav && echo yes
  ...
  yes

  For strict snaps with audio-playback/audio-record:
  $ sudo snap refresh core --candidate # make sure have 2.41. 'install' on 16.04
  $ sudo snap install test-snapd-audio-record --edge

  $ snap connections test-snapd-audio-record  # record not connected
  Interface   PlugSlot Notes
  audio-playback  

[Touch-packages] [Bug 1727908] Re: Software & Updates application does not permit changes on the "Other Software" tab

2020-04-17 Thread Mathew Hodson
** No longer affects: gnome-shell (Ubuntu Bionic)

** No longer affects: gnome-shell (Ubuntu)

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

Title:
  Software & Updates application does not permit changes on the "Other
  Software" tab

Status in software-properties package in Ubuntu:
  In Progress
Status in software-properties source package in Bionic:
  Confirmed

Bug description:
  
  On the "Other Software" tab, I am unable to select "Canonical Partners".
  Similarly, the other checkboxes on the "Other Software" can not be clicked.
  Clicking on a checkbox has no effect, and a dialog requesting the admin 
password is not presented.

  However, activating or deactivating checkboxes on other tabs causes an
  authorization dialog to be presented to the user.

  I experience this bug in an an Xorg session.

  sources.list and sources.list.d have the following permissions:
  -rw-r--r--   1 root root  2897 Oct 26 22:35 sources.list
  drwxr-xr-x   2 root root  4096 Oct 26 21:29 sources.list.d

  All files in sources.list.d have the following permissions as this example:
  -rw-r--r-- 1 root root  189 Oct 25 21:50 google-chrome.list

  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  $ apt-cache policy software-properties-gtk
  software-properties-gtk:
Installed: 0.96.24.17
Candidate: 0.96.24.17
Version table:
   *** 0.96.24.17 500
  500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu artful/main i386 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: software-properties-gtk 0.96.24.17
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Oct 26 22:45:09 2017
  InstallationDate: Installed on 2017-10-26 (1 days ago)
  InstallationMedia: Ubuntu 17.10.0 2017.10.25 amd64 "Custom Artful Aardvark"
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1872551] Re: software-properties-qt: nvidia driver version switch fails

2020-04-17 Thread Mathew Hodson
** Changed in: software-properties (Ubuntu)
   Importance: Undecided => High

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

Title:
  software-properties-qt: nvidia driver version switch fails

Status in software-properties package in Ubuntu:
  Fix Committed

Bug description:
  Switching the Nvidia driver version with kubuntu-driver-manager
  doesn't work anymore: Selecting a different driver version (nvidia-
  driver-440 instead of the currently selected / installed -390) and
  clicking "Apply Changes" has no effect and produces this error message
  in the terminal:

Traceback (most recent call last):
File 
"/usr/lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py", 
line 895, in on_driver_changes_apply
  for dep in get_dependencies(self.apt_cache, pkg.shortname, 'nvidia'):
  NameError: name 'get_dependencies' is not defined

  Steps to reproduce:
  - sudo kubuntu-driver-manager
  - Under "Additional Drivers", select a different Nvidia driver version
(in my case: 440 instead of 390)
  - Click "Apply Changes"
  - (observe error message in the terminal)

  Expected result:
  - No error message
  - Nvidia driver version 440 gets installed

  Actual result:
  - Error message
  - No change in the installed Nvidia driver version

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: kubuntu-driver-manager (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Mon Apr 13 23:41:56 2020
  InstallationDate: Installed on 2016-11-26 (1234 days ago)
  InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
  SourcePackage: kubuntu-driver-manager
  UpgradeStatus: Upgraded to focal on 2020-03-06 (38 days ago)

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

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


[Touch-packages] [Bug 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant

2020-04-17 Thread Mathew Hodson
** Changed in: pulseaudio (Ubuntu Bionic)
   Status: Fix Committed => In Progress

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

Title:
  [SRU] System can't detect external headset in the codec of Conexant

Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project bionic series:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Bionic:
  In Progress
Status in pulseaudio source package in Focal:
  Fix Released

Bug description:
  [Impact]
  In some hp's devices, there are two audio jacks(one headset and one 
headphone) in the audio interface which is using the codec of Conexant, and 
apparently it's not working, the system can't detect the headset in current 
codec.

  [Test Case]
  1. Insert 4 rings(3 stripes) headset into front audio port (headset icon)
  2. Check System Setting->Sound->Output

  [Expected result]
  Can detect external headset

  [Actual result]
  Only shows internal speaker.
  External headset microphone was detected.
  Another front audio port (earphone icon) works fine.

  [Regression Potential]
  Low.

  [Failure rate]
  100%

  [Additional information]
  system-product-name: HP EliteDesk 800 G5 SFF
  CPU: Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8x)
  GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:3e98] (rev 02)
  OS-version: 18.04
  kernel-version: 4.15.0-1065-oem
  pulseaudio-version: 1:11.1-1ubuntu7.2

  Upstream issue:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/272

  Ubuntu-Focal-Source:
  
https://code.launchpad.net/~hugh712/ubuntu/+source/pulseaudio/+git/pulseaudio/+ref/focal-1869819

  PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1869819

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1869819/+subscriptions

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


[Touch-packages] [Bug 1870811] Re: compile auto test failure, and root-unittest failure, is extremely noisy

2020-04-10 Thread Mathew Hodson
** Changed in: systemd (Ubuntu Xenial)
   Status: Invalid => Won't Fix

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

Title:
  compile auto test failure, and root-unittest failure, is extremely
  noisy

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

Bug description:
  [impact]

  failure in the compile-time tests (also run from the root-unittest
  autopkgtest) prints out the entire meson testlog.txt, which shows the
  output of all tests, including passed ones, not just the failed test
  output.  This makes it extremely difficult to find the output of the
  failed test(s) and creates a massive log to download.

  [test case]

  see any failed build, e.g.
  
https://launchpadlibrarian.net/471257226/buildlog_ubuntu-eoan-amd64.systemd_245.218-g69d06b7acf+19.10.20200328163536_BUILDING.txt.gz

  [regression potential]

  any regression would likely occur during test failure, likely
  resulting in lack of details of the test failure; or, a regression
  caused by the additional meson parameter could cause build failure.

  [scope]

  Xenial does not use meson, so can not be adjusted.  This is needed in
  Bionic and later.

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

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


[Touch-packages] [Bug 1839290] Re: systemd doesn't restart a service after crashes

2020-04-10 Thread Mathew Hodson
** Description changed:

  [impact]
  
  when a service configured to restart crashes, under certain
  configurations, that service is not correctly restarted.
  
  [test case]
  
  see comment 8
  
  [regression potential]
  
  this changes the job mode of manager-triggered restarts to 'replace' any
  existing queued job(s), instead of failing if there are queued job(s).
  thus any regressions would occur when a service fails, that is
  configured to restart on failure.
  
  [scope]
  
  This is needed only for Xenial and Bionic.
  
  this is fixed with commit 03ff2dc71ecb09272d728d458498b44f7f132f51 which
  is included already in Eoan.
+ 
+ Fixed in Disco with the backported v240 patch from
+ 
https://github.com/systemd/systemd/commit/677b4cc753f183731fc54fcb68ad46f806c394bc
  
  [other info]
  
  original description:
  ---
  
  Affected versions of OS and systemd:
  $ cat /etc/issue
  Ubuntu 16.04.6 LTS \n \l
  $ systemd --version
  systemd 229
  +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP 
+GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN
  
  Affected packages:
  systemd 229-4ubuntu21.22 and previous versions.
  
  Expected behaviour you didn't see:
  Scheduling restart of failed service.
  A process crashed by sigabrt and didn't restart.
  
  Description:
  The bug was reported to a systemd upstream repository: 
https://github.com/systemd/systemd/issues/11456
  The bug was fixed and accepted to the master branch: 
https://github.com/systemd/systemd/pull/11467/files
  
  Action:
  Include this patch to Ubuntu 16.04 and other version of Ubuntu which are 
supported.

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

Title:
  systemd doesn't restart a service after crashes

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  In Progress
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Disco:
  Fix Released

Bug description:
  [impact]

  when a service configured to restart crashes, under certain
  configurations, that service is not correctly restarted.

  [test case]

  see comment 8

  [regression potential]

  this changes the job mode of manager-triggered restarts to 'replace'
  any existing queued job(s), instead of failing if there are queued
  job(s).  thus any regressions would occur when a service fails, that
  is configured to restart on failure.

  [scope]

  This is needed only for Xenial and Bionic.

  this is fixed with commit 03ff2dc71ecb09272d728d458498b44f7f132f51
  which is included already in Eoan.

  Fixed in Disco with the backported v240 patch from
  
https://github.com/systemd/systemd/commit/677b4cc753f183731fc54fcb68ad46f806c394bc

  [other info]

  original description:
  ---

  Affected versions of OS and systemd:
  $ cat /etc/issue
  Ubuntu 16.04.6 LTS \n \l
  $ systemd --version
  systemd 229
  +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP 
+GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN

  Affected packages:
  systemd 229-4ubuntu21.22 and previous versions.

  Expected behaviour you didn't see:
  Scheduling restart of failed service.
  A process crashed by sigabrt and didn't restart.

  Description:
  The bug was reported to a systemd upstream repository: 
https://github.com/systemd/systemd/issues/11456
  The bug was fixed and accepted to the master branch: 
https://github.com/systemd/systemd/pull/11467/files

  Action:
  Include this patch to Ubuntu 16.04 and other version of Ubuntu which are 
supported.

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

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


[Touch-packages] [Bug 1839290] Re: systemd doesn't restart a service after crashes

2020-04-10 Thread Mathew Hodson
** Bug watch removed: github.com/systemd/systemd/issues #11456
   https://github.com/systemd/systemd/issues/11456

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

Title:
  systemd doesn't restart a service after crashes

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  In Progress
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Disco:
  Fix Released

Bug description:
  [impact]

  when a service configured to restart crashes, under certain
  configurations, that service is not correctly restarted.

  [test case]

  see comment 8

  [regression potential]

  this changes the job mode of manager-triggered restarts to 'replace'
  any existing queued job(s), instead of failing if there are queued
  job(s).  thus any regressions would occur when a service fails, that
  is configured to restart on failure.

  [scope]

  This is needed only for Xenial and Bionic.

  this is fixed with commit 03ff2dc71ecb09272d728d458498b44f7f132f51
  which is included already in Eoan.

  Fixed in Disco with the backported v240 patch from
  
https://github.com/systemd/systemd/commit/677b4cc753f183731fc54fcb68ad46f806c394bc

  [other info]

  original description:
  ---

  Affected versions of OS and systemd:
  $ cat /etc/issue
  Ubuntu 16.04.6 LTS \n \l
  $ systemd --version
  systemd 229
  +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP 
+GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN

  Affected packages:
  systemd 229-4ubuntu21.22 and previous versions.

  Expected behaviour you didn't see:
  Scheduling restart of failed service.
  A process crashed by sigabrt and didn't restart.

  Description:
  The bug was reported to a systemd upstream repository: 
https://github.com/systemd/systemd/issues/11456
  The bug was fixed and accepted to the master branch: 
https://github.com/systemd/systemd/pull/11467/files

  Action:
  Include this patch to Ubuntu 16.04 and other version of Ubuntu which are 
supported.

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

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


[Touch-packages] [Bug 1869814] Re: ubuntu-docs build failure - possible solution

2020-04-10 Thread Mathew Hodson
** Also affects: libxml2 via
   https://bugzilla.gnome.org/show_bug.cgi?id=789714
   Importance: Unknown
   Status: Unknown

** Bug watch removed: gitlab.gnome.org/GNOME/libxml2/issues #64
   https://gitlab.gnome.org/GNOME/libxml2/issues/64

** Bug watch removed: gitlab.gnome.org/GNOME/libxml2/-/issues #12
   https://gitlab.gnome.org/GNOME/libxml2/-/issues/12

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

Title:
  ubuntu-docs build failure - possible solution

Status in libxml2:
  Unknown
Status in libxml2 package in Ubuntu:
  In Progress
Status in ubuntu-docs package in Ubuntu:
  Fix Released

Bug description:
  ubuntu-docs failed to build during the second Focal Fossa test
  rebuild:

  https://launchpad.net/ubuntu/+archive/test-
  rebuild-20200327-focal/+build/18982738

  It was itstool which failed to generate the localized zh_CN pages. If
  dropping zh_CN from ubuntu-help/Makefile.am, ubuntu-docs builds. But
  excluding the Chinese pages is apparently not an acceptable solution.

  The itstool package in focal {build-,}depends on python3. I built
  itstool in a PPA with python2 instead, and in that PPA ubuntu-docs
  built fine without modifications:

  https://launchpad.net/~gunnarhj/+archive/ubuntu/ubuntu-docs/+packages

  So the root cause seems to lie neither in ubuntu-docs nor itstool. I
  would suspect that python3-libxml2 is buggy, but since itstool was
  built against python2 in eoan, it's hard to tell if it's a regression.

  Would building itstool against python2 be an acceptable workaround in
  focal?

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

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


[Touch-packages] [Bug 1869814] Re: ubuntu-docs build failure - possible solution

2020-04-10 Thread Mathew Hodson
** No longer affects: itstool (Ubuntu)

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

Title:
  ubuntu-docs build failure - possible solution

Status in libxml2 package in Ubuntu:
  In Progress
Status in ubuntu-docs package in Ubuntu:
  Fix Released

Bug description:
  ubuntu-docs failed to build during the second Focal Fossa test
  rebuild:

  https://launchpad.net/ubuntu/+archive/test-
  rebuild-20200327-focal/+build/18982738

  It was itstool which failed to generate the localized zh_CN pages. If
  dropping zh_CN from ubuntu-help/Makefile.am, ubuntu-docs builds. But
  excluding the Chinese pages is apparently not an acceptable solution.

  The itstool package in focal {build-,}depends on python3. I built
  itstool in a PPA with python2 instead, and in that PPA ubuntu-docs
  built fine without modifications:

  https://launchpad.net/~gunnarhj/+archive/ubuntu/ubuntu-docs/+packages

  So the root cause seems to lie neither in ubuntu-docs nor itstool. I
  would suspect that python3-libxml2 is buggy, but since itstool was
  built against python2 in eoan, it's hard to tell if it's a regression.

  Would building itstool against python2 be an acceptable workaround in
  focal?

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

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


[Touch-packages] [Bug 1831736] Re: [MIR] lz4 by default

2020-04-09 Thread Mathew Hodson
** Also affects: ubuntu-release-upgrader (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-release-upgrader (Ubuntu)
   Status: New => Won't Fix

** Changed in: ubuntu-release-upgrader (Ubuntu)
   Importance: Undecided => High

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

Title:
  [MIR] lz4 by default

Status in Release Upgrader:
  New
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in live-build package in Ubuntu:
  Fix Released
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in lz4 package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Won't Fix

Bug description:
  Use `lz4 -9 -l` compression for initramfs by default as discussed on
  ubuntu-devel.

  This would also pull the lz4 package into main

  https://lists.ubuntu.com/archives/ubuntu-devel/2019-June/040726.html

  [Regression Potential]

  We are trying to optimize for total boot speed, but performing a
  micro-optimization upon time to create/unpack kernel/initrd is an
  insufficient benchmark for total boot speed. This is because it
  ignores time to load the kernel/initrd, and whether the
  firmware/bootloader were able to stream decompress it whilst loading
  it. I.e. it is argued that in the real world, subsecond decompression
  gains are irrelevant if UEFI firmware, tftp boot, etc. take a lot
  longer than that to read extra 10s of MBs of boot material.

  [TODO]
  Measure pure i/o load speed with stopwatch, to figure out MB/s speed of 
loading initrds/kernel off FAT32, EXT4, TFTP, HTTP.
  Re-evaluate if we should provide different compression mechanisms:
  - ie. gzip instead of lz4 for most cases (revert)
  - ie. xz for painful i/o cases (e.g. netboot)

  I booted grub2 and measured loading largish amount of files, ie. $
  date; initrd (hd0,gpt5)/initrd.img;  initrd (hd0,gpt5)/initrd.img;
  initrd (hd0,gpt5)/initrd.img; initrd (hd0,gpt5)/initrd.img; initrd
  (hd0,gpt5)/initrd.img; date

  To get a rough speed between 30 and 44 MB/s of loading these files off
  ext4 on nvme.

  With lz4 initrd taking 67M, and gzip initrd taking 59M, the grub i/o
  penalty is 0.18s whilst I gain over a second in faster decompression
  time. Overall a win.

  xz initrd is 36M meaning saving e.g. 0.8s of i/o time whilst gaining
  2.4s of decompression time, meaning overall worse than gzip.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-upgrader/+bug/1831736/+subscriptions

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


[Touch-packages] [Bug 1831736] Re: [MIR] lz4 by default

2020-04-09 Thread Mathew Hodson
** No longer affects: ubuntu-release-upgrader (Ubuntu)

** No longer affects: linux (Ubuntu)

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

Title:
  [MIR] lz4 by default

Status in Release Upgrader:
  New
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in live-build package in Ubuntu:
  Fix Released
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in lz4 package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Won't Fix

Bug description:
  Use `lz4 -9 -l` compression for initramfs by default as discussed on
  ubuntu-devel.

  This would also pull the lz4 package into main

  https://lists.ubuntu.com/archives/ubuntu-devel/2019-June/040726.html

  [Regression Potential]

  We are trying to optimize for total boot speed, but performing a
  micro-optimization upon time to create/unpack kernel/initrd is an
  insufficient benchmark for total boot speed. This is because it
  ignores time to load the kernel/initrd, and whether the
  firmware/bootloader were able to stream decompress it whilst loading
  it. I.e. it is argued that in the real world, subsecond decompression
  gains are irrelevant if UEFI firmware, tftp boot, etc. take a lot
  longer than that to read extra 10s of MBs of boot material.

  [TODO]
  Measure pure i/o load speed with stopwatch, to figure out MB/s speed of 
loading initrds/kernel off FAT32, EXT4, TFTP, HTTP.
  Re-evaluate if we should provide different compression mechanisms:
  - ie. gzip instead of lz4 for most cases (revert)
  - ie. xz for painful i/o cases (e.g. netboot)

  I booted grub2 and measured loading largish amount of files, ie. $
  date; initrd (hd0,gpt5)/initrd.img;  initrd (hd0,gpt5)/initrd.img;
  initrd (hd0,gpt5)/initrd.img; initrd (hd0,gpt5)/initrd.img; initrd
  (hd0,gpt5)/initrd.img; date

  To get a rough speed between 30 and 44 MB/s of loading these files off
  ext4 on nvme.

  With lz4 initrd taking 67M, and gzip initrd taking 59M, the grub i/o
  penalty is 0.18s whilst I gain over a second in faster decompression
  time. Overall a win.

  xz initrd is 36M meaning saving e.g. 0.8s of i/o time whilst gaining
  2.4s of decompression time, meaning overall worse than gzip.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-upgrader/+bug/1831736/+subscriptions

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


[Touch-packages] [Bug 1866820] Re: crash in nano-4.8 when typing ^6 ^J [patch]

2020-04-08 Thread Mathew Hodson
** Changed in: nano (Ubuntu)
   Importance: Undecided => High

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

Title:
  crash in nano-4.8 when typing ^6 ^J  [patch]

Status in nano package in Ubuntu:
  Confirmed

Bug description:
  Nanos since version 4.0 contain a silly oversight: when the user tries
  to justify an empty region (with ^6 ^J, or similar), nano crashes.

  Attached upstream patch fixes the problem.  Please apply to Focal
  before it is released.

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

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


[Touch-packages] [Bug 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant

2020-04-08 Thread Mathew Hodson
** Changed in: pulseaudio (Ubuntu Bionic)
   Importance: Undecided => High

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

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

Title:
  [SRU] System can't detect external headset in the codec of Conexant

Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project bionic series:
  New
Status in pulseaudio package in Ubuntu:
  In Progress
Status in pulseaudio source package in Bionic:
  Triaged
Status in pulseaudio source package in Focal:
  In Progress

Bug description:
  [Impact]
  In some hp's devices, there are two audio jacks(one headset and one 
headphone) in the audio interface which is using the codec of Conexant, and 
apparently it's not working, the system can't detect the headset in current 
codec.

  [Test Case]
  1. Insert 4 rings(3 stripes) headset into front audio port (headset icon)
  2. Check System Setting->Sound->Output

  [Expected result]
  Can detect external headset

  [Actual result]
  Only shows internal speaker.
  External headset microphone was detected.
  Another front audio port (earphone icon) works fine.

  [Regression Potential]
  Low.

  [Failure rate]
  100%

  [Additional information]
  system-product-name: HP EliteDesk 800 G5 SFF
  CPU: Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8x)
  GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:3e98] (rev 02)
  OS-version: 18.04
  kernel-version: 4.15.0-1065-oem
  pulseaudio-version: 1:11.1-1ubuntu7.2

  Upstream issue:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/272

  Ubuntu-Focal-Source:
  
https://code.launchpad.net/~hugh712/ubuntu/+source/pulseaudio/+git/pulseaudio/+ref/focal-1869819

  PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1869819

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1869819/+subscriptions

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


[Touch-packages] [Bug 1870850] Re: Multi-line paste broken between kitty and nano 4.8 [focal]

2020-04-08 Thread Mathew Hodson
** Changed in: nano (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Multi-line paste broken between kitty and nano 4.8 [focal]

Status in nano package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04 Focal beta (as of 2020-04-04)
  nano 4.8-1

  What I expect to happen: multi-line paste into nano via kitty pastes
  multiple lines.

  What happens instead: pasted multi-line text is one line with no line
  breaks.

  There is a bit of a spat between the developers of kitty (gnome-
  terminal:kitty::screen:tmux, basically) and nano about how to do
  multi-line pasting.  See e.g.:

  * https://savannah.gnu.org/bugs/?58010
  * https://lists.gnu.org/archive/html/nano-devel/2020-03/msg5.html
  * https://github.com/kovidgoyal/kitty/issues/994

  Without taking sides, the facts are:

  * With the current versions in focal (kitty 0.15.0 and nano 4.8), pasting 
multi-line will result in newlines being eaten.
  * nano 4.9 introduces a fix (commit 481529e8650d105c3280def764e4917af0cabb49) 
which brings the newline handling more in line with other terminal-aware 
programs (treating raw \n as line break).

  Peripherally, nano 4.8 introduced new bracketed paste mode support.
  This makes a read of the kitty github issue above harder, since the
  issue being reported here is about an incompatibility in bracketed
  paste mode between kitty and nano, not pre-bracketed ^J handling.

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

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


[Touch-packages] [Bug 1870554] Re: ip-netns(8) unmounts /sys filesystem hierarchy within namespace

2020-04-08 Thread Mathew Hodson
** Changed in: iproute2 (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  ip-netns(8) unmounts /sys filesystem hierarchy within namespace

Status in iproute2 package in Ubuntu:
  New

Bug description:
  Filesystems ordinarily mounted beneath /sys, particularly /sys/fs/cgroup, are 
not mounted within network namespaces created by ip-netns(8), as 
lib/namespace.c:netns_switch() explicitly remounts /sys.
  The patch enclosed removes the offending calls to umount2(2) and mount(2), 
leaving the /sys hierarchy intact within network namespaces.

  $ lsb_release -rd
  Description:Ubuntu 18.04.4 LTS
  Release:18.04

  $ apt-cache policy iproute2
  iproute2:
Installed: 4.15.0-2ubuntu1
Candidate: 4.15.0-2ubuntu1
Version table:
   *** 4.15.0-2ubuntu1 500
  500 http://fr2.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  Nota bene: this bug was reported in [1] (unresolved) and, on Arch
  Linux, [2].

  References:
  [1] https://answers.launchpad.net/ubuntu/+source/iproute2/+question/659146
  [2] https://bugs.archlinux.org/task/33328

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

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


[Touch-packages] [Bug 1863001] Re: Incorrect LAYOUT is set when choosing Lithuanian in dpkg-reconfigure keyboard-configuration and Ubiquity

2020-03-26 Thread Mathew Hodson
** Summary changed:

- [PATCH] Incorrect LAYOUT is set when choosing Lithuanian in dpkg-reconfigure 
keyboard-configuration and Ubiquity
+ Incorrect LAYOUT is set when choosing Lithuanian in dpkg-reconfigure 
keyboard-configuration and Ubiquity

** Changed in: console-setup (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Incorrect LAYOUT is set when choosing Lithuanian in dpkg-reconfigure
  keyboard-configuration and Ubiquity

Status in console-setup package in Ubuntu:
  Confirmed

Bug description:
  If user chooses Lithuanian keyboard layout during installation
  (Ubiquity) or dpkg-reconfigure keyboard-configuration then incorrect
  layout is set in /etc/default/keyboard :

  XKBLAYOUT="lt,lt"
  XKBVARIANT=",us"

  This configuration is not intuitive, because people think, that
  sometimes Lithuanian keyboard works (when lt1 is selected in GNOME
  shell panel) and sometimes doesn't work (when lt2 is selected).

  So, majority of Lithuanian users are force to removed second lt(us)
  layout and add English (US) altgr-intl layout.

  So, correct /etc/default/keyboard should be:

  XKBMODEL="pc105"
  XKBLAYOUT="lt,us"
  XKBVARIANT=",altgr-intl"
  XKBOPTIONS="grp_led:scroll"
  BACKSPACE="guess"

  I'm attaching a patch to debian/keyboard-configuration.config file
  which fixes this issue

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

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


[Touch-packages] [Bug 1867908] Re: Fix RTM NEW/DELLINK IFLA_IFNAME copy for maximum ifname length

2020-03-26 Thread Mathew Hodson
** Changed in: wpa (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Fix RTM NEW/DELLINK IFLA_IFNAME copy for maximum ifname length

Status in wpa package in Ubuntu:
  Triaged

Bug description:
  Some wifi adapters kept asking for a password when MAC address
  randomization was enabled.

  I reported this to Realtek, and they gave me a patch for
  wpa_supplicant, which fixes the issue.

  I asked Realtek to report this upstream to wpasupplicant, and they
  did, the commit is:
  http://w1.fi/cgit/hostap/commit/?id=7546c489a95a033c78331915fcdfa0e6fd74d563

  It would be very nice to cherrypick that for Focal.

  I uploaded it as a merge request below, and I tested that it fixes the issue 
with adapters based on the following chipsets:
  ath9k, rtl8812au, rtl88x2bu and rtl8821cu

  To reproduce this:

  Ubuntu's network-manager defaults to "MAC randomization disabled", I think as 
a workaround to this specific issue. This is defined in two places:
  - wifi.scan-rand-mac-address=no in /etc/NetworkManager/NetworkManager.conf
  - Some specific drivers in 
/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf.

  With these, the problem happens in around 10% of the cases.
  To be able to reproduce it in 100% of the cases, it's best to remove these 
Ubuntu workarounds. So:
  - Set "wifi.scan-rand-mac-address=yes" in 
/etc/NetworkManager/NetworkManager.conf
  - Remove /usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf.
  - systemctl stop network-manager
  - killall wpa_supplicant
  - systemctl start network-manager

  Then insert a USB wifi adapter that results in a big name with 15
  characters like wlx74ee2ae2436a and try to connect to a wifi network.
  It will keep asking for a password.

  Then apply the patch, run the 3 commands above to restart network-
  manager, and verify that it can now connect properly.

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

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


[Touch-packages] [Bug 1863239] Re: /dev/bus/usb/*/* device file of HP multi-function printer assigned to "audio" group

2020-03-26 Thread Mathew Hodson
** No longer affects: pulseaudio (Ubuntu)

** No longer affects: systemd (Ubuntu)

** No longer affects: udev (Ubuntu)

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

Title:
  /dev/bus/usb/*/* device file of HP multi-function printer assigned to
  "audio" group

Status in libmtp package in Ubuntu:
  In Progress
Status in libmtp package in Debian:
  Unknown

Bug description:
  When testing HPLIP I found out that CUPS backends can access my
  printer only when they are running as root, when they are running as
  the special user lp, as it is usually the case, they cannot access the
  printer.

  So I tried to find out why and saw that the /dev/bus/usb/*/* device
  file for the printer has group ownership "audio" and not "lp":

  till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ ll 
/dev/bus/usb/*/*
  crw-rw-r--  1 root root189,   0 Feb 11 14:17 /dev/bus/usb/001/001
  crw-rw-r--  1 root root189,   2 Feb 11 14:17 /dev/bus/usb/001/003
  crw-rw-r--  1 root root189,   3 Feb 11 14:17 /dev/bus/usb/001/004
  crw-rw-r--  1 root plugdev 189,   4 Feb 14 12:23 /dev/bus/usb/001/005
  crw-rw-r--  1 root root189,   5 Feb 11 14:17 /dev/bus/usb/001/006
  crw-rw+ 1 root audio   189,  62 Feb 14 12:37 /dev/bus/usb/001/063
  crw-rw-r--  1 root root189, 128 Feb 11 14:17 /dev/bus/usb/002/001
  crw-rw-r--  1 root root189, 130 Feb 13 09:38 /dev/bus/usb/002/003
  till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$

  The printer is the device /dev/bus/usb/001/063:

  till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ lsusb
  Bus 002 Device 003: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit 
Ethernet
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 005: ID 138a:0097 Validity Sensors, Inc. 
  Bus 001 Device 004: ID 04f2:b5ce Chicony Electronics Co., Ltd Integrated 
Camera
  Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
  Bus 001 Device 006: ID 056a:50b7 Wacom Co., Ltd Pen and multitouch sensor
  Bus 001 Device 063: ID 03f0:7a12 HP, Inc HP OfficeJet Pro 8730
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ 

  There must be a bug somewhere in the UDEV rules.

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

-- 
Mailing list: https://launchpad.net/~touch-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-03-20 Thread Mathew Hodson
** Changed in: apport (Ubuntu Disco)
   Status: New => Won't Fix

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

Title:
  autopkgtest regression in test_add_proc_info

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 Disco:
  Won't Fix
Status in apport source package in Eoan:
  New

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 1861446] Re: on focal 'ubuntu-bug linux' doesn't automatically collect kernel artifacts

2020-03-20 Thread Mathew Hodson
** No longer affects: linux (Ubuntu Focal)

** No longer affects: linux (Ubuntu)

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

Title:
  on focal 'ubuntu-bug linux' doesn't automatically collect kernel
  artifacts

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Focal:
  Fix Released

Bug description:
  Hello, on focal I ran 'ubuntu-bug linux' to report a kernel issue. The
  issue was filed against linux-signed-5.4 (Ubuntu) rather than linux
  (Ubuntu), and none of the logs usually included with kernel bug
  reports were included.

  After the bug was changed from linux-signed-5.4 to linux, I was
  prompted to run apport-collect by the kernel team's triagebot and that
  worked successfully:

  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861359/+activity

  My guess is that apport needs to be updated to understand a change in
  kernel packaging.

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: apport 2.20.11-0ubuntu16
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportLog:
   
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  CrashReports:
   640:1000:1000:40192:2020-01-30 03:32:41.717296496 +:2020-01-30 
03:32:41.717296496 +:/var/crash/_usr_bin_apport-bug.1000.crash
   600:0:0:467987:2020-01-24 20:40:35.855434497 +:2020-01-24 
20:40:35.819434494 +:/var/crash/zfsutils-linux.0.crash
   640:0:0:386063:2020-01-24 20:42:09.391725398 +:2020-01-24 
20:42:08.887728256 +:/var/crash/_usr_sbin_zfs.0.crash
  Date: Thu Jan 30 18:44:47 2020
  PackageArchitecture: all
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago)

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

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


[Touch-packages] [Bug 1851542] Re: autopkgtest fails due to aspell SRU

2020-03-20 Thread Mathew Hodson
** Tags removed: verification-needed

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

Title:
  autopkgtest fails due to aspell SRU

Status in apport package in Ubuntu:
  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:
  Fix Released
Status in apport source package in Focal:
  Fix Released

Bug description:
  [Impact]
  A new autopkgtest test regression began appearing after (and due to) an 
aspell SRU.

  ==
  FAIL: test_install_packages_versioned (__main__.T)
  install_packages() with versions and with cache
  --
  Traceback (most recent call last):
File "./test_backend_apt_dpkg.py", line 557, in 
test_install_packages_versioned
  self.assertIn(result, 'aspell-doc version 1.1 required, but 
0.60.7~20110707-3build1 is available\n')
  AssertionError: 'aspell-doc version 1.1 required, but 
0.60.7~20110707-3ubuntu0.1 is available\n' not found in 'aspell-doc version 1.1 
required, but 0.60.7~20110707-3build1 is available\n'

  --
  Ran 37 tests in 191.123s

  FAILED (failures=1)

  [Test Case]
  ## From within autopkgtest source package, with autopkgtest deps installed
  ## This is a slightly modified version if debian/tests/upstream-system

  # do not run in the source tree, as we want to check the system-installed
  # apport
  TESTDIR=${ADTTMP:-/tmp}/apport-tests
  mkdir -p $TESTDIR
  cp test/test_* test/run "$TESTDIR"
  cd "$TESTDIR"

  # clean up old crash reports
  rm -rf /var/crash/*

  export GNUPGHOME=$TESTDIR/gnupg
  mkdir -m 700 $GNUPGHOME

  ./run backend_apt_dpkg

  [Fix]
  
http://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu/focal/apport/ubuntu/revision/2717

  [Regression Risk]
  Code is restricted to a test that is only ran via autopkgtest.

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

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


[Touch-packages] [Bug 1854237] Re: autopkgtests fail after security fixes

2020-03-20 Thread Mathew Hodson
** Changed in: apport (Ubuntu Disco)
   Status: New => Won't Fix

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

Title:
  autopkgtests fail after security fixes

Status in Apport:
  New
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:
  Fix Released

Bug description:
  The following autopkgtests fail after the recent security fixes:

  log:FAIL: test_get_logind_session (__main__.T)
  log:FAIL: test_core_dump_packaged (__main__.T)
  log:FAIL: test_core_dump_unpackaged (__main__.T)
  log:FAIL: test_crash_setuid_drop (__main__.T)
  log:FAIL: test_crash_setuid_keep (__main__.T)
  log:FAIL: test_crash_setuid_nonwritable_cwd (__main__.T)
  log:FAIL: test_lock_symlink (__main__.T)

  test_get_logind_session is a test failing to keep up with an API
  change. test_core_dump_* is failures to remove partly written core
  files. Both of these are easy fixes, I'll have a MP for them soon.

  test_crash_setuid_* are caused by the dropping of privileges when
  accessing the crashing process's /proc. They seem to be testing
  behaviour now explicitly forbidden by the fix to be honest!

  test_lock_symlink fails because the lock file is now always in
  /var/lock/apport/ and not in $APPORT_REPORT_DIR. I guess we could
  update the test, but is it really worth it after the fix?

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

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


[Touch-packages] [Bug 1758529] Re: landscape-package-changer crashed with io.UnsupportedOperation in pulse(): fileno

2020-02-25 Thread Mathew Hodson
** No longer affects: python-apt (Ubuntu)

** No longer affects: python-apt (Ubuntu Bionic)

** No longer affects: python-apt (Ubuntu Disco)

** No longer affects: python-apt (Ubuntu Eoan)

** Tags removed: verification-needed

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

Title:
  landscape-package-changer crashed with io.UnsupportedOperation in
  pulse(): fileno

Status in Landscape Client:
  Fix Committed
Status in landscape-client package in Ubuntu:
  Fix Released
Status in landscape-client source package in Bionic:
  Fix Committed
Status in landscape-client source package in Disco:
  Won't Fix
Status in landscape-client source package in Eoan:
  Fix Committed

Bug description:
  [Impact]

   * landscape-package-changer will output stack traces when executed
 with python3. This adds noise in the logs and confuse apport into
 thinking there was a crash, even though the error does not affect
 functionality.

   * The activity log for package operations will also show errors.

   * The patch overrides python-apt reporting of progress, as
 landscape-package-changer is never executed from a terminal.

  [Test Case]

   * register landscape-client and wait for packages to be reported.

   * trigger a package installation from the landscape server.

   * check /var/log/landscape/manager.log for Package changer warnings

  [Regression Potential]

   * The change is trivially simple.

   * The changed code path is only used by python-apt progress reporting.
 Since landscape-package-changer does not rely on it and is able
 to continue, other errors would likely have the same fate: that is
 crashing the progress reporting thread and continuing.

  [Original Description]

  Crash in the background

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: landscape-client 18.01-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  Date: Sat Mar 24 07:05:34 2018
  ExecutablePath: /usr/bin/landscape-package-changer
  InstallationDate: Installed on 2015-07-04 (994 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  InterpreterPath: /usr/bin/python3.6
  ProcCmdline: /usr/bin/python3 /usr/bin/landscape-package-changer --quiet
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
  Python3Details: /usr/bin/python3.6, Python 3.6.5rc1, python3-minimal, 3.6.4-1
  PythonArgs: ['/usr/bin/landscape-package-changer', '--quiet']
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  SourcePackage: landscape-client
  Title: landscape-package-changer crashed with io.UnsupportedOperation in 
pulse(): fileno
  Traceback:
   Traceback (most recent call last):
     File "/usr/lib/python3/dist-packages/apt/progress/text.py", line 164, in 
pulse
   not os.isatty(self._file.fileno())):
   io.UnsupportedOperation: fileno
  UpgradeStatus: Upgraded to bionic on 2018-03-15 (8 days ago)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/landscape-client/+bug/1758529/+subscriptions

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


[Touch-packages] [Bug 1794478] Re: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it

2020-02-21 Thread Mathew Hodson
** Changed in: network-manager (Ubuntu)
   Importance: Undecided => High

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

Title:
  Automatic ipv4 not assigned to bond interface is manual ipv6 is
  assigned to it

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Bionic:
  Confirmed

Bug description:
  [Impact]

  In case creating bond interface, IPv4 address is not automatically
  assigned when IPv6 has manual setting.

  [Test Case]

  1. create 18.04.4 instance, network-manager version is 1.10.6-2ubuntu.1.2 as 
original description.
  2. ipv6 manual, ipv4 auto
  ##
  sudo nmcli con add type bond con-name bond0 ifname bond0 mode active-backup;
  sudo nmcli con mod bond0 bond.options "downdelay=0, fail_over_mac=none, 
miimon=100, mode=active-backup,num_grat_arp=0, primary_reselect=always, 
updelay=0";
  sudo nmcli con mod bond0 ipv6.method manual ipv6.addresses 
fe81::ff:fe97:a27f/64;
  sudo nmcli con mod bond0 ipv4.method auto;
  sudo nmcli con add type bond-slave ifname ens34 master bond0;
  sudo nmcli con add type bond-slave ifname ens35 master bond0;
  sudo nmcli con mod bond0 +bond.options mii=100

  sleep 5

  sudo nmcli con up bond-slave-ens34
  sudo nmcli con up bond-slave-ens35
  sudo nmcli con up bond0;

  sleep 5;
  sudo nmcli c s bond0
  ##
  3. ipv6 auto, ipv4 auto
  ##
  sudo nmcli con add type bond con-name bond0 ifname bond0 mode active-backup;
  sudo nmcli con mod bond0 bond.options "downdelay=0, fail_over_mac=none, 
miimon=100, mode=active-backup,num_grat_arp=0, primary_reselect=always, 
updelay=0";
  sudo nmcli con mod bond0 ipv6.method auto;
  sudo nmcli con mod bond0 ipv4.method auto;
  sudo nmcli con add type bond-slave ifname ens34 master bond0;
  sudo nmcli con add type bond-slave ifname ens35 master bond0;
  sudo nmcli con mod bond0 +bond.options mii=100

  sleep 5

  sudo nmcli con up bond-slave-ens34
  sudo nmcli con up bond-slave-ens35
  sudo nmcli con up bond0;

  sleep 5

  sudo nmcli c s bond0
  ##

  when run #3, it is working, but with #2, it is not working.

  [Potential Regression]

  Actually nothing special. fix just remove if statement. but it needs
  Network Manager restarted.

  [Other informations]

  After upstream fix, it is working fine with #2 and #3 above.

  * Upstream bug and fix:

  https://bugzilla.redhat.com/show_bug.cgi?id=1575944
  https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/f03ae35

  * Only affecting Bionic:

  $ git describe --contains f03ae35
  1.10.8~2

  $ rmadison network-manager
  ==> network-manager | 1.10.6-2ubuntu1.2   | bionic-updates
  network-manager | 1.20.4-2ubuntu2.2   | eoan-updates
  network-manager | 1.22.4-1ubuntu2 | focal

  [Original description]

  ---Problem Description---
  Bond interface with automatic ipv4 mode and manual ipv6 mode fails to get 
automatic ipv4 assigned from dhcp server.

  ---uname output---
  Linux NetworkTest 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 13:42:17 UTC 
2018 s390x s390x s390x GNU/Linux

  Machine Type = s390x

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   When user configures ipv4 as automatic and ipv6 as manual for bond interface 
automatic ipv4 is not getting assigned.
  Looks like dhcp client request for ipv4 is not done to dhcp server after 
maunal ipv6 is assigned quickly to bond interface

  This issue will not happen in below cases:
  1)with ipv4 automatic and ipv6 manual configuration for ethernet or vlan 
interface.
  2)with ipv4 automatic and ipv6 automatic configuration for bond interface
  3)with ipv4 automatic and ipv6 disabled configuration for bond interface

  Configuration:
  Bond interface, ipv4 automatic mode and ipv6 automatic mode

  root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond
  [connection]
  id=test_bond
  uuid=63e54542-5135-47ac-a954-b861c3937be2
  type=bond
  interface-name=test_bond
  permissions=
  timestamp=1537944121

  [ethernet]
  mac-address-blacklist=

  [bond]
  downdelay=0
  fail_over_mac=none
  miimon=100
  mode=active-backup
  num_grat_arp=0
  primary_reselect=always
  updelay=0

  [ipv4]
  dns-search=
  method=auto

  [ipv6]
  addr-gen-mode=stable-privacy
  dns-search=
  method=auto

  From /var/log/syslog, we can see ip got assigned:

  Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPDISCOVER on test_bond to 
255.255.255.255 port 67 interval 3 (xid=0x5e04bf1e)
  Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPREQUEST of 10.2.3.55 on 
test_bond to 255.255.255.255 port 67 (xid=0x5e04bf1e)
  Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPOFFER of 10.2.3.55 from 
10.2.3.1
  Sep 26 06:26:26 

[Touch-packages] [Bug 1311056] Re: [SRU] apt-add-repository adds duplicate commented/disabled source lines

2020-02-16 Thread Mathew Hodson
** Changed in: python-apt (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: python-apt (Ubuntu Eoan)
   Importance: Undecided => High

** Changed in: python-apt (Ubuntu Bionic)
   Importance: Undecided => High

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

Title:
  [SRU] apt-add-repository adds duplicate commented/disabled source
  lines

Status in python-apt package in Ubuntu:
  Fix Released
Status in python-apt source package in Xenial:
  New
Status in python-apt source package in Bionic:
  New
Status in python-apt source package in Eoan:
  New

Bug description:
  Impact
  ==

  Under most circumstances, the impact is minimal (a few extra redundant
  comment lines in apt sources. However, if users are automating source
  removal / addition on a machine (as in comment 11), there is the
  potential to wind up with an excessively large (and thus slow to
  parse) apt sources configuration.

  Test packages for the supported releases are available from the
  following PPA:

  https://launchpad.net/~waveform/+archive/ubuntu/python-apt

  Built from the source which can be found in the following branches:

  https://code.launchpad.net/~waveform/ubuntu/+source/python-apt/+git
  /python-apt/+ref/sru-dupe-ppa-xenial

  https://code.launchpad.net/~waveform/ubuntu/+source/python-apt/+git
  /python-apt/+ref/sru-dupe-ppa-bionic

  https://code.launchpad.net/~waveform/ubuntu/+source/python-apt/+git
  /python-apt/+ref/sru-dupe-ppa-eoan

  Test Case
  =

  * sudo add-apt-repository -y ppa:deadsnakes/ppa
  * cat /etc/apt/sources.list.d/deadsnakes*.list
  * Note the presence of one uncommented "deb" line, and one commented 
"deb-src" line
  * sudo add-apt-repository -y ppa:deadsnakes/ppa
  * cat /etc/apt/sources.list.d/deadsnakes*.list
  * Note the uncommented "deb" line is still there but the commented "deb-src" 
line has now been duplicated
  * sudo add-apt-repository ppa:waveform/python-apt
  * sudo apt upgrade  # update python-apt to fixed version
  * sudo add-apt-repository -y ppa:deadsnakes/ppa
  * cat /etc/apt/sources.list.d/deadsnakes*.list
  * Note there has been no further duplication of the commented "deb-src" line

  Regression Potential
  

  Minimal; test cases have been added to cover the duplication case, and
  to cover the enabling of sources (which was not covered by existing
  tests, but was part of the code altered to fix the duplication case),
  and insertion of sources at a position (again, not covered by existing
  tests but modified as part of the fix). The test case has been used
  successfully on all targeted releases (xenial, bionic, and eoan).

  Original Description
  

  Trusty Tahr 14.04

  0 root@osprey:/etc/apt/sources.list.d#cat aims-aims-desktop-trusty.list
  deb http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main
  # deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main
  0 root@osprey:/etc/apt/sources.list.d#apt-add-repository -y 
ppa:aims/aims-desktop
  gpg: keyring `/tmp/tmp0ufdhnmv/secring.gpg' created
  gpg: keyring `/tmp/tmp0ufdhnmv/pubring.gpg' created
  gpg: requesting key BE796FF2 from hkp server keyserver.ubuntu.com
  gpg: /tmp/tmp0ufdhnmv/trustdb.gpg: trustdb created
  gpg: key BE796FF2: public key "Launchpad PPA for AIMS" imported
  gpg: Total number processed: 1
  gpg:   imported: 1  (RSA: 1)
  OK
  0 root@osprey:/etc/apt/sources.list.d#cat aims-aims-desktop-trusty.list deb 
http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main
  # deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main
  # deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main
  0 root@osprey:/etc/apt/sources.list.d#

  That deb-src line should have stayed commented out, and not been
  duplicated. (Commented deb lines should of course be uncommented, as
  already fixed per https://bugs.launchpad.net/ubuntu/+source/python-
  apt/+bug/1042916 .)

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

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


[Touch-packages] [Bug 1860606] Re: TypeError: _fetch_archives() missing 1 required positional argument: 'allow_unauthenticated'

2020-02-16 Thread Mathew Hodson
** Tags added: regression-update

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

Title:
  TypeError: _fetch_archives() missing 1 required positional argument:
  'allow_unauthenticated'

Status in python-apt package in Ubuntu:
  Fix Released
Status in python-apt source package in Xenial:
  Fix Released
Status in python-apt source package in Bionic:
  Fix Released
Status in python-apt source package in Disco:
  Fix Released
Status in python-apt source package in Eoan:
  Fix Released
Status in python-apt source package in Focal:
  Fix Released

Bug description:
  I was upgrading my workstation from 19.04 to 19.10 and following that
  to 20.04. In each case I used do-release-upgrade (without and with -d
  respectively). The 20.04 upgrade failed as the tool crashed on invalid
  function signature:

  Original exception was:
  Traceback (most recent call last):
File "/tmp/ubuntu-release-upgrader-f_816ncr/focal", line 8, in 
  sys.exit(main())
File 
"/tmp/ubuntu-release-upgrader-f_816ncr/DistUpgrade/DistUpgradeMain.py", line 
238, in main
  if app.run():
File 
"/tmp/ubuntu-release-upgrader-f_816ncr/DistUpgrade/DistUpgradeController.py", 
line 2082, in run
  return self.fullUpgrade()
File 
"/tmp/ubuntu-release-upgrader-f_816ncr/DistUpgrade/DistUpgradeController.py", 
line 1998, in fullUpgrade
  if not self.doDistUpgradeFetching():
File 
"/tmp/ubuntu-release-upgrader-f_816ncr/DistUpgrade/DistUpgradeController.py", 
line 1233, in doDistUpgradeFetching
  self.cache._fetch_archives(self.fetcher, pm)
  TypeError: _fetch_archives() missing 1 required positional argument: 
'allow_unauthenticated'

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

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


[Touch-packages] [Bug 1862505] Re: alsa-lib-1.2.1.2: should install the alsa-ucm-conf and alsa-topology-conf to focal image by default

2020-02-16 Thread Mathew Hodson
** Tags added: packaging

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

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

Status in alsa-lib package in Ubuntu:
  New

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

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

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

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


[Touch-packages] [Bug 1861757] Re: Missing libgcc_s.so.1 decrypting partition on boot

2020-02-05 Thread Mathew Hodson
** No longer affects: cryptsetup (Ubuntu)

** No longer affects: gcc-10 (Ubuntu)

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

Title:
  Missing libgcc_s.so.1 decrypting partition on boot

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools package in Debian:
  Unknown

Bug description:
  On focal with -proposed repo enabled. Updated all packages and
  rebooted. Upon entering the LUKS passphrase for disk decryption I get
  the following message, and cannot boot:

"libgcc_s.so.1 must be installed for pthread_cancel to work"

  Booting with the previous kernel works.

  Found this question with an identical issue:
  https://askubuntu.com/questions/1190687/ubuntu-19-10-missing-lib-gcc-
  so-1-after-kernel-update, which points to "/usr/share/initramfs-
  tools/hooks/cryptroot" being unable to find that lib. It was looking
  in "/lib/x86_64-linux-gnu/", but libgcc_s.so.1 is not there, but at
  "/usr/lib/" and "/usr/lib/x86_64-linux-gnu/". Temporarily fixed by
  copying the file to "/lib/x86_64-linux-gnu/" and regenerating the
  initramdisk.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libgcc1 1:10-20200202-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-13.16-generic 5.4.16
  Uname: Linux 5.4.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue Feb  4 00:05:48 2020
  InstallationDate: Installed on 2019-09-23 (133 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190917)
  SourcePackage: gcc-10
  UpgradeStatus: Upgraded to focal on 2020-01-24 (10 days ago)

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

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


[Touch-packages] [Bug 1814355] Re: snapd remove /usr/local/bin from the PATH for all systemd unit (bionic SRU regression)

2020-02-05 Thread Mathew Hodson
** No longer affects: systemd (Ubuntu Cosmic)

** No longer affects: systemd (Ubuntu Bionic)

** No longer affects: systemd (Ubuntu)

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

Title:
  snapd remove /usr/local/bin from the PATH for all systemd unit (bionic
  SRU regression)

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in snapd package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Bionic:
  New
Status in snapd source package in Bionic:
  Fix Released
Status in initramfs-tools source package in Cosmic:
  Won't Fix
Status in snapd source package in Cosmic:
  Won't Fix

Bug description:
  [Impact]

   * Initramfs exports PATH to init, which is different than the
  expected stock / compiled one, which results in slightly different
  runtime behaviour of init, if it has environment generators as well.

  [Test Case]

   * Disable snapd env generator & disable initrd-less boot (if enabled)
     sudo chmod -x 
/usr/lib/systemd/system-environment-generators/snapd-env-generator
     set empty GRUB_FORCE_PARTUUID= and update-grub

   * Reboot cosmic system with an initramfs
     $ journalctl -b -k | grep initramfs
     (verify that initramfs was unpacked)

   * Check the path used by systemd, ie.:
     systemd-run /usr/bin/env
     journalctl -b -e | grep PATH

     It should contain /usr/local

   * Enable any env generator for example & reboot:
 /usr/lib/systemd/system-environment-generators/xnox.sh
 #!/bin/sh
 echo XNOX=ROCKS

   * Verify path used by systemd

     It should still contain /usr/local

  Repeat again with the new initramfs-tools.

  
  [Regression Potential]

   * We are hardcoding, the same path, yet again, in one more place. However, 
we are setting it to a well-known value (see https://wiki.ubuntu.com/PATH
   ) as it is universally expected and regressed when booted (a) with initrd 
AND (b) with broken path exported by initrd AND (c) with an env-generator.

  [Other Info]

   * Anything else you think is useful to include
   * Anticipate questions from users, SRU, +1 maintenance, security teams and 
the Technical Board
   * and address these questions in advance

  ===

  Big regression in 2.37.1+18.04 compare to version 2.34.2

  all these paths  /usr/local/sbin &  /usr/local/bin are not anymore in
  the path of all systemd process .

  So we can not start a daemon that use /usr/local/bin

  reinstalling package 2.34.2 fix the problem

  in 2.34.2 :

  ~# strings  /proc/$(pidof /lib/systemd/systemd-resolved)/environ | grep PATH
  PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

  in 2.37.1+18.04 :

  ~# strings  /proc/$(pidof /lib/systemd/systemd-resolved)/environ | grep PATH
  PATH=/sbin:/usr/sbin:/bin:/usr/bin:/snap/bin

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

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


[Touch-packages] [Bug 1832919] Re: installed libssl1.1:amd64 package post-installation script subprocess returned error exit status 10

2020-02-01 Thread Mathew Hodson
** Changed in: openssl (Ubuntu Cosmic)
   Status: Fix Committed => Won't Fix

** Tags removed: libssl1.1 verification-done

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

Title:
  installed libssl1.1:amd64 package post-installation script subprocess
  returned error exit status 10

Status in openssl package in Ubuntu:
  Fix Released
Status in openssl source package in Bionic:
  Fix Released
Status in openssl source package in Cosmic:
  Won't Fix
Status in openssl source package in Disco:
  Fix Released
Status in openssl source package in Eoan:
  Fix Released

Bug description:
  [Impact]

   * Systems that have in error removed debconf database fail to upgrade
  libssl1.1 (as e.g. is known to be done in some vagrant boxes)

   * libssl1.1 tries to use debconf template from libc6 package, but
  doesn't ship one by itself as it should for shared templates. As it is
  not guaranteed that template will be available.

  [TestCase]

  # DO NOT DO THIS ON PRODUCTION MACHINES #
  # echo PURGE | debconf-communicate libpam0g:amd64
  0
  # echo PURGE | debconf-communicate libpam0g
  0
  # echo PURGE | debconf-communicate libc6:amd64
  0
  # echo PURGE | debconf-communicate libc6
  0

  Then upgrade from bionic-release to the -proposed package and it
  should work.

  It should not fail with exit code 10.

  [Regression Potential]

   * A new template is added, an identical import from glibc without any
  further changes. This registers the template in debconf, for this
  package, preventing the above describe error. This has no codechanges,
  only metadata.

  [Other Info]
   
   * Original bug report 

  The error happens when trying to configure libssl1.1:amd64 (dpkg
  --configure -D 2  libssl1.1)

  dpkg: error processing package libssl1.1:amd64 (--configure):
   installed libssl1.1:amd64 package post-installation script subprocess 
returned error exit status 10
  D02: post_script_tasks - ensure_diversions
  D02: post_script_tasks - trig_incorporate
  D02: check_triggers_cycle pnow=libc-bin:amd64 first
  Processing triggers for libc-bin (2.27-3ubuntu1) ...
  D02: post_postinst_tasks - trig_incorporate
  Errors were encountered while processing:
   libssl1.1:amd64

  [ WORKAROUND TO RECOVER YOUR SYSTEM ]

  $ sudo dpkg-reconfigure libc6
  $ sudo dpkg --configure libssl1.1

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

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


[Touch-packages] [Bug 1832421] Re: openssl reboot needed message using incorrect path to X server

2020-02-01 Thread Mathew Hodson
** Changed in: openssl (Ubuntu Cosmic)
   Status: Fix Committed => Won't Fix

** Tags removed: removal-candidate verification-needed verification-
needed-cosmic verification-needed-disco

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

Title:
  openssl reboot needed message using incorrect path to X server

Status in openssl package in Ubuntu:
  Fix Released
Status in openssl source package in Bionic:
  Fix Released
Status in openssl source package in Cosmic:
  Won't Fix
Status in openssl source package in Disco:
  Fix Released
Status in openssl source package in Eoan:
  Fix Released

Bug description:
  [Impact]

   * On desktop, upgrading libssl1.1 does not show reboot required
  notification

  [Test Case]

   * Boot ubuntu desktop
   * Upgrade libssl1.1
   * Observe reboot notification pop-up from update-notifier is _not_ shown

  [Regression Potential]

   * Tweaking postinst only to correct for the Xorg path. Current code
  is innert, but is well excercised in prior releases.

  [Other Info]

   * Original bug report:

  Hello, the openssl library postinst file is using pidof /usr/bin/X,
  but that doesn't appear to be the path to the X11 server any more:

  debian/libssl1.1.postinst:

  # Only issue the reboot notification for servers; we proxy this by
  # testing that the X server is not running (LP: #244250)
  if ! pidof /usr/bin/X > /dev/null && [ -x 
/usr/share/update-notifier/notify-reboot-required ]; then
  /usr/share/update-notifier/notify-reboot-required
  fi

  On my 18.04 LTS laptop:

  $ ps auxw | grep Xorg
  root  2440  0.5  0.4 495932 78996 tty7 Rsl+ May10 264:45 
/usr/lib/xorg/Xorg :0 vt7 -nolisten tcp -auth /var/l

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: openssl 1.1.1-1ubuntu2.1~18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18
  Uname: Linux 4.15.0-50-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  Date: Tue Jun 11 18:06:51 2019
  InstallationDate: Installed on 2012-10-18 (2427 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: openssl
  UpgradeStatus: Upgraded to bionic on 2018-05-02 (406 days ago)

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

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


[Touch-packages] [Bug 1828215] Re: openssl ca -spkac output regressed

2020-02-01 Thread Mathew Hodson
** Changed in: openssl (Ubuntu Cosmic)
   Status: Fix Committed => Won't Fix

** Tags removed: verification-done

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

Title:
  openssl ca -spkac output regressed

Status in OpenSSL:
  Fix Released
Status in openssl package in Ubuntu:
  Fix Released
Status in openssl source package in Bionic:
  Fix Released
Status in openssl source package in Cosmic:
  Won't Fix
Status in openssl source package in Disco:
  Fix Released
Status in openssl source package in Eoan:
  Fix Released

Bug description:
  [Impact]

   * openssl command line utility option parsing has regressed in
  1.1.0i+ and produces binary output, where text output is expected,
  breaking applications that parse that.

  [Test Case]

  Setup CA:
  $ apt install openssl
  $ mkdir -p  demoCA/private demoCA/newcerts
  $ touch demoCA/index.txt
  $ echo 01 > demoCA/serial

  $ openssl req -new -x509 -days 365 -newkey rsa:4096 -keyout
  demoCA/private/cakey.pem -out demoCA/cacert.pem

  # Use password test
  # Accept defaults for all other settings

  $ openssl req -new -days 365 -newkey rsa:4096 -keyout
  demoCA/sslkey.pem -out demoCA/sslcert.pem

  Generate regular request / key:
  # Use password test
  # Set common name to: example.com
  # Accept defaults for all other settings

  Generate spkac request:
  $ openssl spkac -key demoCA/sslkey.pem -out demoCA/sslcert.spkac
  $ cat <>demoCA/sslcert.spkac 
  countryName=AU
  stateOrProvinceName=Some-State
  organizationName=Internet Widgits Pty Ltd
  commonName=example.com
  EOF

  Sign spkac request:
  $ echo test | openssl ca -passin stdin -batch -spkac demoCA/sslcert.spkac 
-startdate 190121130654Z

  Expected: pure text output
  Unexpected: binary output for the signed cert

  
   Currently produces binary goop.

   Should produce PEM format Base64 encoded certificate data in a block 
surrounded
   with BEGIN/END certificate.

  [Regression Potential]

   * This is a regression in cosmic and up, and impeding regression in
  bionic with the upcoming 1.1.1 SRU. A bugfix exists upstream.

  [Other Info]

   * Originally reported
  https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1797386/comments/39

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

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


[Touch-packages] [Bug 1832522] Re: openssl maintainer scripts do not trigger services restart

2020-02-01 Thread Mathew Hodson
** Changed in: openssl (Ubuntu Cosmic)
   Status: Fix Committed => Won't Fix

** Tags removed: removal-candidate verification-needed verification-
needed-cosmic

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

Title:
  openssl maintainer scripts do not trigger services restart

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

Bug description:
  [Impact]

   * Major libssl ugprades require services to be restarted, for them to 
continue to function correctly at runtime.
   * The maintainer scripts were not adjusted to trigger.

  [Test Case]

   * Install bionic from release pocket and install ssl using daemon e.g. 
openssh-server libapache-mod-ssl
   * Upgrade libssl1.1
   * Ensure that services that use openssl are offered to be restarted.

  [Regression Potential]

   * We are rebuilding libssl1.1 and changing maintainer scripts. Given
  that we have missed upgrade trigger, we will ask users to restart
  services again even if they may have restarted them already.

  [Other Info]
   
   * Previous major libssl upgrade issue of similar nature was
 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=743889

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

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


[Touch-packages] [Bug 1832659] Re: openssl 1.1.1-1ubuntu2.1~18.04.1 contains upstream bug 7350

2020-02-01 Thread Mathew Hodson
** Changed in: openssl (Ubuntu Cosmic)
   Status: Fix Committed => Won't Fix

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

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

Title:
  openssl 1.1.1-1ubuntu2.1~18.04.1 contains upstream bug 7350

Status in OpenSSL:
  Fix Released
Status in openssl package in Ubuntu:
  Fix Released
Status in openssl source package in Bionic:
  Fix Released
Status in openssl source package in Cosmic:
  Won't Fix
Status in openssl source package in Disco:
  Fix Released
Status in openssl source package in Eoan:
  Fix Released

Bug description:
  [Impact]

   * Regression was introduced in OpenSSL 1.1.1 and fixed in 1.1.1b that 
prevents initialising libcrypto/libssl multiple times, and/or with different 
options.
   * This breaks existing applications that correctly use init API, ie. 
initialise libcrypto before/separately from libssl and/or with different 
options.

  [Test Case]

   * wget
  
https://bugs.launchpad.net/ubuntu/cosmic/+source/openssl/+bug/1832659/+attachment/5270802/+files/test_multiple_libssl_libcrypto_init.py

   * python3 ./test_multiple_libssl_libcrypto_init.py

  test_multiple_init (__main__.TestMultipleInit) ... ok

  --
  Ran 1 test in 0.014s

  OK

  [Regression Potential]

   * This is a cherrypick from upstream, and is backwards compatible
  with existing code. Simply init succeeds under more conditions now,
  than it did previously in 1.1.1. Also with this fix, OpenSSL is back
  to how things used to work with 1.1.0 and prior releases.

  [Original Bug report]

  After the update of openssl in bionic, I started having an issue and
  after troubleshooting found this issue:

  https://github.com/openssl/openssl/issues/7350

  Applying the patch linked in that issue and rebuilding the openssl
  package avoided the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: openssl 1.1.1-1ubuntu2.1~18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
  Uname: Linux 4.15.0-51-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  Date: Thu Jun 13 00:21:16 2019
  InstallationDate: Installed on 2019-06-12 (0 days ago)
  InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: openssl
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1858092] Re: Network Manager not saving OpenVPN password

2020-02-01 Thread Mathew Hodson
** Tags removed: kwallet manager network openvpn
** Tags added: regression-release

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

Title:
  Network Manager not saving OpenVPN password

Status in NetworkManager:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Eoan:
  Fix Committed
Status in network-manager source package in Focal:
  Fix Released

Bug description:
  [impact]

  network-manager no longer correctly saves VPN passwords

  [test case]

  on a 19.10 (or later) system, configure a VPN with network-manager and
  provide a password that it should save.  On next connection, it will
  prompt for a password again.

  [regression potential]

  as this adjusts how n-m handles connections with secrets/passwords,
  any regression would likely cause secrets to fail to be stored for
  later use, and/or failure to correctly use the secrets at all to setup
  the connection.

  [scope]

  This is needed only in eoan.

  The patch:
  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/cf557bf06f344bdbcd775dce35daa42335c645d7
  is included in the 1.20.6 release:
  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/230#note_283402

  focal-proposed currently has version 1.20.8, so this patch is already
  included in focal.

  This bug was introduced after version 1.18.2:
  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/230#note_235976

  disco-updates has version 1.60.0, so this patch is not needed in disco
  or earlier.

  [other info]

  original description:
  ---

  Hi everyone,

  After upgrading to kubuntu 19.10 I can't save the VPN password using Store 
password for this user only. It seems the integration with the kwallet is 
failing somehow...
  The system logs seem to show that everything went ok, but the password is not 
saved:
  jan 02 11:40:40 NetworkManager[5530]:  [1577965240.2166] audit: 
op="connection-update" uuid="4c05-911a-1d9161f05a19" name="ovpn" 
args="vpn.secrets" pid=14142 uid=1000 result="success"

  This also happens with a clean install.

  Operating System: Kubuntu 19.10
  KDE Plasma Version: 5.16.5
  KDE Frameworks Version: 5.62.0
  Qt Version: 5.12.4
  Kernel Version: 5.3.0-24-generic
  OS Type: 64-bit

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

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


[Touch-packages] [Bug 1780996] Re: Convert triggers to noawait

2020-02-01 Thread Mathew Hodson
** Changed in: clutter-imcontext (Ubuntu)
   Status: Triaged => Won't Fix

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

** Changed in: libomxil-bellagio (Ubuntu Xenial)
   Status: Triaged => Won't Fix

** Changed in: libomxil-bellagio (Ubuntu Bionic)
   Status: Triaged => Won't Fix

** Changed in: maxima (Ubuntu Xenial)
   Status: Fix Committed => Won't Fix

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

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

Title:
  Convert triggers to noawait

Status in appstream package in Ubuntu:
  Fix Released
Status in bumblebee package in Ubuntu:
  Fix Released
Status in clutter-imcontext package in Ubuntu:
  Won't Fix
Status in django-countries package in Ubuntu:
  Fix Released
Status in dochelp package in Ubuntu:
  Fix Released
Status in dovecot package in Ubuntu:
  Fix Released
Status in fusiondirectory package in Ubuntu:
  Fix Released
Status in gdk-pixbuf package in Ubuntu:
  Fix Released
Status in glib2.0 package in Ubuntu:
  Fix Released
Status in gosa package in Ubuntu:
  Won't Fix
Status in guile-2.0 package in Ubuntu:
  Fix Released
Status in guile-2.2 package in Ubuntu:
  Fix Released
Status in hicolor-icon-theme package in Ubuntu:
  Fix Released
Status in libomxil-bellagio package in Ubuntu:
  Won't Fix
Status in libreoffice package in Ubuntu:
  Fix Released
Status in ltsp package in Ubuntu:
  Fix Released
Status in mate-icon-theme package in Ubuntu:
  Fix Released
Status in maxima package in Ubuntu:
  Fix Released
Status in neurodebian package in Ubuntu:
  Fix Released
Status in nevow package in Ubuntu:
  Fix Released
Status in octave package in Ubuntu:
  Fix Released
Status in packagekit package in Ubuntu:
  Fix Released
Status in pike7.8 package in Ubuntu:
  Fix Released
Status in pike8.0 package in Ubuntu:
  Fix Released
Status in postgresql-common package in Ubuntu:
  Fix Released
Status in qgis package in Ubuntu:
  Fix Released
Status in reconf-inetd package in Ubuntu:
  Won't Fix
Status in shared-mime-info package in Ubuntu:
  Fix Released
Status in sphinx package in Ubuntu:
  Fix Released
Status in syslog-ng-incubator package in Ubuntu:
  Fix Released
Status in tex-common package in Ubuntu:
  Fix Released
Status in wokkel package in Ubuntu:
  Fix Released
Status in xpdf package in Ubuntu:
  Fix Released
Status in yorick package in Ubuntu:
  Fix Released
Status in appstream source package in Xenial:
  Fix Released
Status in bumblebee source package in Xenial:
  Fix Released
Status in clutter-imcontext source package in Xenial:
  Won't Fix
Status in django-countries source package in Xenial:
  Fix Released
Status in dochelp source package in Xenial:
  Fix Released
Status in dovecot source package in Xenial:
  Fix Released
Status in fusiondirectory source package in Xenial:
  Fix Released
Status in gdk-pixbuf source package in Xenial:
  Fix Released
Status in glib2.0 source package in Xenial:
  Fix Released
Status in gosa source package in Xenial:
  Won't Fix
Status in guile-2.0 source package in Xenial:
  Fix Released
Status in hicolor-icon-theme source package in Xenial:
  Fix Released
Status in libomxil-bellagio source package in Xenial:
  Won't Fix
Status in libreoffice source package in Xenial:
  Fix Released
Status in ltsp source package in Xenial:
  Fix Released
Status in mate-icon-theme source package in Xenial:
  Fix Released
Status in maxima source package in Xenial:
  Won't Fix
Status in neurodebian source package in Xenial:
  Fix Released
Status in nevow source package in Xenial:
  Fix Released
Status in octave source package in Xenial:
  Fix Released
Status in packagekit source package in Xenial:
  Fix Released
Status in pike7.8 source package in Xenial:
  Fix Released
Status in pike8.0 source package in Xenial:
  Fix Released
Status in postgresql-common source package in Xenial:
  Fix Released
Status in qgis source package in Xenial:
  Fix Released
Status in reconf-inetd source package in Xenial:
  Won't Fix
Status in shared-mime-info source package in Xenial:
  Fix Released
Status in sphinx source package in Xenial:
  Fix Released
Status in syslog-ng-incubator source package in Xenial:
  Fix Released
Status in tex-common source package in Xenial:
  Fix Released
Status in wokkel source package in Xenial:
  Fix Released
Status in xpdf source package in Xenial:
  Fix Released
Status in yorick source package in Xenial:
  Fix Released
Status in appstream source package in Bionic:
  Fix Released
Status in bumblebee source package in Bionic:
  Fix Released
Status in clutter-imcontext source package in Bionic:
  Won't Fix
Status in django-countries source package in Bionic:
  Fix Released
Status in dochelp source package in Bionic:
  Fix Released
Status in dovecot source package in Bionic:
  Fix Released
Status in 

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

2020-02-01 Thread Mathew Hodson
** Bug watch removed: github.com/systemd/systemd/issues #14567
   https://github.com/systemd/systemd/issues/14567

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

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

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

Bug description:
  [Impact]

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

  [Test Case]

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

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

  Actual result:
  no group membership gained from pam_group.

  [Regression Potential]

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

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

  [Other Info]
  Original bug description:

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

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

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

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

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

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

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


[Touch-packages] [Bug 1845046] Re: Bluetooth headphones default to low quality headset mode and fail to switch to A2DP when selected

2020-01-25 Thread Mathew Hodson
** Bug watch removed: PulseAudio #525
   https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/525

** Bug watch removed: PulseAudio #716
   https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/716

** No longer affects: pulseaudio (Ubuntu)

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

Title:
  Bluetooth headphones default to low quality headset mode and fail to
  switch to A2DP when selected

Status in bluez package in Ubuntu:
  Fix Released
Status in bluez source package in Bionic:
  Fix Committed
Status in bluez source package in Eoan:
  Fix Committed
Status in bluez source package in Focal:
  Fix Released

Bug description:
  [Impact]

  Whenever I turn on my headphones they'll connect to my computer but
  I'm able to hear the input audio from my microphone and low quality
  output audio. I have to disconnect the headphones in the bluetooth
  devices and reconnect for it to fix the problem.

  [Test Case]

  0. Set up your Bluetooth headphones with Ubuntu.
  1. Turn off the headphones.
  2. Turn on the headphones.
  3. In Settings>Sound verify they have reconnected in A2DP mode (stereo, high 
quality, no microphone support).

  [Regression Potential]

  Low. Only the headset code path is affected and the fix has already
  been released for some time in BlueZ 5.51 onward.

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

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


[Touch-packages] [Bug 1860606] Re: TypeError: _fetch_archives() missing 1 required positional argument: 'allow_unauthenticated'

2020-01-23 Thread Mathew Hodson
** No longer affects: ubuntu-release-upgrader (Ubuntu)

** No longer affects: ubuntu-release-upgrader (Ubuntu Xenial)

** No longer affects: ubuntu-release-upgrader (Ubuntu Bionic)

** No longer affects: ubuntu-release-upgrader (Ubuntu Disco)

** No longer affects: ubuntu-release-upgrader (Ubuntu Eoan)

** No longer affects: ubuntu-release-upgrader (Ubuntu Focal)

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

Title:
  TypeError: _fetch_archives() missing 1 required positional argument:
  'allow_unauthenticated'

Status in python-apt package in Ubuntu:
  Confirmed
Status in python-apt source package in Xenial:
  Fix Released
Status in python-apt source package in Bionic:
  Fix Released
Status in python-apt source package in Disco:
  Fix Released
Status in python-apt source package in Eoan:
  Fix Released
Status in python-apt source package in Focal:
  Confirmed

Bug description:
  I was upgrading my workstation from 19.04 to 19.10 and following that
  to 20.04. In each case I used do-release-upgrade (without and with -d
  respectively). The 20.04 upgrade failed as the tool crashed on invalid
  function signature:

  Original exception was:
  Traceback (most recent call last):
File "/tmp/ubuntu-release-upgrader-f_816ncr/focal", line 8, in 
  sys.exit(main())
File 
"/tmp/ubuntu-release-upgrader-f_816ncr/DistUpgrade/DistUpgradeMain.py", line 
238, in main
  if app.run():
File 
"/tmp/ubuntu-release-upgrader-f_816ncr/DistUpgrade/DistUpgradeController.py", 
line 2082, in run
  return self.fullUpgrade()
File 
"/tmp/ubuntu-release-upgrader-f_816ncr/DistUpgrade/DistUpgradeController.py", 
line 1998, in fullUpgrade
  if not self.doDistUpgradeFetching():
File 
"/tmp/ubuntu-release-upgrader-f_816ncr/DistUpgrade/DistUpgradeController.py", 
line 1233, in doDistUpgradeFetching
  self.cache._fetch_archives(self.fetcher, pm)
  TypeError: _fetch_archives() missing 1 required positional argument: 
'allow_unauthenticated'

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

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


[Touch-packages] [Bug 1856574] Re: removal of various autopilot packages

2020-01-12 Thread Mathew Hodson
python-testtools (2.3.0-6build1) focal; urgency=medium

  * No-change rebuild to generate dependencies on python2.

 -- Matthias Klose   Tue, 17 Dec 2019 12:53:30 +

python-testtools (2.3.0-6) unstable; urgency=medium

  [ Mattia Rizzolo ]
  * Remove Robert Collins from uploaders, as he has retired.  Closes: #920508

  [ Ondřej Nový ]
  * Running wrap-and-sort -bast.
  * Use debhelper-compat instead of debian/compat.

  [ Thomas Goirand ]
  * Removed Python 2 support (Closes: #938215).

 -- Thomas Goirand   Sat, 14 Sep 2019 18:51:58 +0200

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

Title:
  removal of various autopilot packages

Status in autopilot-gtk package in Ubuntu:
  Fix Released
Status in autopilot-legacy package in Ubuntu:
  Fix Released
Status in python-fixtures package in Ubuntu:
  Fix Released
Status in python-testtools package in Ubuntu:
  Fix Released

Bug description:
  python-fixtures and python-testtools are not built anymore in focal,
  but still referenced by some Ubuntu-only packages.  We need to at
  least remove autopilot-legacy if we don't want to re-introduce those
  package, and modify autopilot-gtk to build witout the autopilot-legacy
  b-d.

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

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


[Touch-packages] [Bug 1856574] Re: removal of various autopilot packages

2020-01-12 Thread Mathew Hodson
python-fixtures (3.0.0-3build1) focal; urgency=medium

  * No-change rebuild to generate dependencies on python2.

 -- Matthias Klose   Tue, 17 Dec 2019 12:52:51 +

python-fixtures (3.0.0-3) unstable; urgency=medium

  * Removed d/gbp.conf.
  * Ran wrap-and-sort -bast.
  * Point VCS fields to Salsa.
  * Adopt the package in the OpenStack team, since Robert Collins resigned
from Debian (Closes: #920510).
  * Removed build-dependency on python-docutils (Closes: #635259).
  * Removed Python 2 support (Closes: #937756).
  * Use python3 -m testtools.run fixtures.test_suite to run tests.
  * Removed build-dependency on python3-nose.
  * Standards-Version is now 4.4.0.

 -- Thomas Goirand   Sun, 15 Sep 2019 17:27:02 +0200

** Changed in: python-fixtures (Ubuntu)
   Status: Fix Committed => Fix Released

** Changed in: autopilot-legacy (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  removal of various autopilot packages

Status in autopilot-gtk package in Ubuntu:
  Fix Released
Status in autopilot-legacy package in Ubuntu:
  Fix Released
Status in python-fixtures package in Ubuntu:
  Fix Released
Status in python-testtools package in Ubuntu:
  Fix Released

Bug description:
  python-fixtures and python-testtools are not built anymore in focal,
  but still referenced by some Ubuntu-only packages.  We need to at
  least remove autopilot-legacy if we don't want to re-introduce those
  package, and modify autopilot-gtk to build witout the autopilot-legacy
  b-d.

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

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


[Touch-packages] [Bug 1831736] Re: [MIR] lz4 by default

2020-01-12 Thread Mathew Hodson
** No longer affects: partman-auto (Ubuntu)

** Changed in: initramfs-tools (Ubuntu)
   Importance: Undecided => High

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

** Changed in: live-build (Ubuntu)
   Importance: Undecided => High

** Changed in: livecd-rootfs (Ubuntu)
   Importance: Undecided => High

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

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

Title:
  [MIR] lz4 by default

Status in Release Upgrader:
  New
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in live-build package in Ubuntu:
  Fix Released
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in lz4 package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Invalid

Bug description:
  Use `lz4 -9 -l` compression for initramfs by default as discussed on
  ubuntu-devel.

  This would also pull the lz4 package into main

  https://lists.ubuntu.com/archives/ubuntu-devel/2019-June/040726.html

  [Regression Potential]

  We are trying to optimize for total boot speed, but performing a
  micro-optimization upon time to create/unpack kernel/initrd is an
  insufficient benchmark for total boot speed. This is because it
  ignores time to load the kernel/initrd, and whether the
  firmware/bootloader were able to stream decompress it whilst loading
  it. I.e. it is argued that in the real world, subsecond decompression
  gains are irrelevant if UEFI firmware, tftp boot, etc. take a lot
  longer than that to read extra 10s of MBs of boot material.

  [TODO]
  Measure pure i/o load speed with stopwatch, to figure out MB/s speed of 
loading initrds/kernel off FAT32, EXT4, TFTP, HTTP.
  Re-evaluate if we should provide different compression mechanisms:
  - ie. gzip instead of lz4 for most cases (revert)
  - ie. xz for painful i/o cases (e.g. netboot)

  I booted grub2 and measured loading largish amount of files, ie. $
  date; initrd (hd0,gpt5)/initrd.img;  initrd (hd0,gpt5)/initrd.img;
  initrd (hd0,gpt5)/initrd.img; initrd (hd0,gpt5)/initrd.img; initrd
  (hd0,gpt5)/initrd.img; date

  To get a rough speed between 30 and 44 MB/s of loading these files off
  ext4 on nvme.

  With lz4 initrd taking 67M, and gzip initrd taking 59M, the grub i/o
  penalty is 0.18s whilst I gain over a second in faster decompression
  time. Overall a win.

  xz initrd is 36M meaning saving e.g. 0.8s of i/o time whilst gaining
  2.4s of decompression time, meaning overall worse than gzip.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-upgrader/+bug/1831736/+subscriptions

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


[Touch-packages] [Bug 1847570] Re: PulseAudio automatically switches to HDMI sound output on login

2020-01-12 Thread Mathew Hodson
** Bug watch removed: Xfce Bugzilla #16335
   https://bugzilla.xfce.org/show_bug.cgi?id=16335

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

Title:
  PulseAudio automatically switches to HDMI sound output on login

Status in PulseAudio:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Eoan:
  Fix Committed
Status in pulseaudio source package in Focal:
  Fix Released

Bug description:
  [Impact]

  On my freshly installed eoan system I have two output devices:
  - HDMI/DisplayPort 2 - GK208 ...
  - Line Out - Family 17h ...

  When I login into the system pulseaudio always select the "wrong"
  one (HDMI) and I need to go to gnome-settings/Sound/Output Device
  and switch to "line out". This applies to every login/logout not
  just reboots.

  [Test Case]

  0. Plug in a monitor that supports HDMI audio (one that appears in
  your Settings>Sound)

  1. Log out and in again.

  Verify the default audio device in Settings is still speakers or
  headphones. Not the monitor's HDMI audio device.

  [Regression Potential]

  The behaviour is changed back to what it was before 19.10, some users
  might find it inconvenient and prefer the auto switch but the feedback
  we got shows it's unreliable and an annoying for the majority of our
  users so we will got back to default to safest behaviour.

  The fix proposed just reverts to the same code used in PulseAudio 12
  and earlier. It has also been released and verified on focal already.

  [Workaround]

  Comment out:

  load-module module-switch-on-port-available
  load-module module-switch-on-connect

  from /etc/pulse/default.pa

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

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


[Touch-packages] [Bug 1847570] Re: PulseAudio automatically switches to HDMI sound output on login

2019-12-31 Thread Mathew Hodson
** Changed in: pulseaudio (Ubuntu Eoan)
   Status: Fix Committed => Triaged

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

Title:
  PulseAudio automatically switches to HDMI sound output on login

Status in PulseAudio:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Eoan:
  Triaged
Status in pulseaudio source package in Focal:
  Fix Released

Bug description:
  [Impact]

  On my freshly installed eoan system I have two output devices:
  - HDMI/DisplayPort 2 - GK208 ...
  - Line Out - Family 17h ...

  When I login into the system pulseaudio always select the "wrong"
  one (HDMI) and I need to go to gnome-settings/Sound/Output Device
  and switch to "line out". This applies to every login/logout not
  just reboots.

  [Test Case]

  0. Plug in a monitor that supports HDMI audio (one that appears in
  your Settings>Sound)

  1. Log out and in again.

  Verify the default audio device in Settings is still speakers or
  headphones. Not the monitor's HDMI audio device.

  [Regression Potential]

  Low. The fix proposed just reverts to the same code used in PulseAudio
  12 and earlier. It has also been released and verified on focal
  already.

  [Workaround]

  Comment out:

  load-module module-switch-on-port-available
  load-module module-switch-on-connect

  from /etc/pulse/default.pa

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

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


[Touch-packages] [Bug 1856574] Re: removal of various autopilot packages

2019-12-24 Thread Mathew Hodson
** Changed in: python-testtools (Ubuntu)
   Status: New => Fix Committed

** Changed in: python-fixtures (Ubuntu)
   Importance: Undecided => Medium

** Changed in: python-testtools (Ubuntu)
   Importance: Undecided => High

** Changed in: python-testtools (Ubuntu)
   Importance: High => Medium

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

Title:
  removal of various autopilot packages

Status in autopilot-gtk package in Ubuntu:
  Fix Released
Status in autopilot-legacy package in Ubuntu:
  Fix Released
Status in python-fixtures package in Ubuntu:
  Fix Committed
Status in python-testtools package in Ubuntu:
  Fix Committed

Bug description:
  python-fixtures and python-testtools are not built anymore in focal,
  but still referenced by some Ubuntu-only packages.  We need to at
  least remove autopilot-legacy if we don't want to re-introduce those
  package, and modify autopilot-gtk to build witout the autopilot-legacy
  b-d.

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

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


[Touch-packages] [Bug 1771041] Re: Remove gconf from Ubuntu

2019-12-24 Thread Mathew Hodson
** No longer affects: autopilot-legacy (Ubuntu)

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

Title:
  Remove gconf from Ubuntu

Status in desktopnova package in Ubuntu:
  New
Status in evolution-indicator package in Ubuntu:
  New
Status in gconf package in Ubuntu:
  New
Status in gconf-editor package in Ubuntu:
  New
Status in gkdebconf package in Ubuntu:
  New
Status in gnome-mastermind package in Ubuntu:
  New
Status in gnome-phone-manager package in Ubuntu:
  New
Status in gnome-xcf-thumbnailer package in Ubuntu:
  New
Status in gnomint package in Ubuntu:
  New
Status in gtkwave package in Ubuntu:
  Fix Released
Status in guake-indicator package in Ubuntu:
  New
Status in gyrus package in Ubuntu:
  New
Status in jack-mixer package in Ubuntu:
  New
Status in jana package in Ubuntu:
  New
Status in mssh package in Ubuntu:
  New
Status in ogmrip package in Ubuntu:
  New
Status in ooo-thumbnailer package in Ubuntu:
  New
Status in planner package in Ubuntu:
  New
Status in ogmrip package in Debian:
  Confirmed

Bug description:
  gconf is being removed from Debian Testing. We should remove it from
  Ubuntu also.

  eclipse is troublesome. At a minimum, we can remove everything but
  eclipse and gconf.

  libgnome is sort of a blocker so do it first LP: #1771031
  And remove libqt-gconf LP: #1740538

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

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


[Touch-packages] [Bug 1856574] Re: removal of various autopilot packages

2019-12-24 Thread Mathew Hodson
** Changed in: python-fixtures (Ubuntu)
   Status: New => Fix Committed

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

Title:
  removal of various autopilot packages

Status in autopilot-gtk package in Ubuntu:
  Fix Released
Status in autopilot-legacy package in Ubuntu:
  Fix Released
Status in python-fixtures package in Ubuntu:
  Fix Committed
Status in python-testtools package in Ubuntu:
  New

Bug description:
  python-fixtures and python-testtools are not built anymore in focal,
  but still referenced by some Ubuntu-only packages.  We need to at
  least remove autopilot-legacy if we don't want to re-introduce those
  package, and modify autopilot-gtk to build witout the autopilot-legacy
  b-d.

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

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


[Touch-packages] [Bug 1843479] Re: gzip in Ubuntu Eoan results in Exec format error on WSL1

2019-12-20 Thread Mathew Hodson
** Changed in: binutils (Ubuntu)
   Importance: Undecided => Medium

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

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

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

Title:
  gzip in Ubuntu Eoan results in Exec format error on WSL1

Status in binutils:
  Confirmed
Status in binutils package in Ubuntu:
  Fix Released
Status in gzip package in Ubuntu:
  Fix Released
Status in binutils source package in Eoan:
  Fix Committed
Status in gzip source package in Eoan:
  Fix Released

Bug description:
  [Impact]

   * Running gzip on WSL1 results in the following error:
     $ gzip
     -bash: /bin/gzip: cannot execute binary file: Exec format error
   * The error occurs frequently in package updates and makes gzip inoperable 
on WSL1
   * The problem is caused by PT_LOAD offset pointing past the end of file and 
the fix is fixing strip to not generate such ELF files and recompiling gzip 
with the fixed strip.

  [Test Case]

   * Check the gzip binary for wrong offset:
    $ FILE=/usr/bin/gzip; readelf -W --program-headers $FILE | awk -v 
size=$(stat -c %s $FILE) '/^  LOAD/ {if (strtonum($2) > size) {print "wrong 
offset ("$2" ("strtonum($2)") points past EOF:" size; exit 1;}}'

  [ Regression Potential ]

   * The binutils fix could cause binutils to generate invalid ELF files. The 
fix is very small and isolated and has been tested and accepted by upstream, 
which makes such problems unlikely.
   * Bugs in the toolchain in general can make the rebuilt gzip show new 
errors, but this generally applies to many SRUs and security updates. The 
testing period in proposed should mitigate this risk.

  [Other Info]

   * Binutils 2.33.1-6ubuntu1.1 was accidentally built in -proposed
  instead of in a PPA. I've rebuilt it in https://launchpad.net/~ci-
  train-ppa-service/+archive/ubuntu/3878 for the -security pocket as
  2.33-2ubuntu1.2.

  [Originial Bug Text]

  Summary:

  Running gzip on WSL1 results in the following error:

  $ gzip
  -bash: /bin/gzip: cannot execute binary file: Exec format error

  What I expect to happen:

  gzip executes correctly on WSL1.

  What happens instead:

  gzip fails with an Exec format error.

  Notes:

  I suspect a change in how gzip is being built for Eoan is causing
  issues with ELF parsing on the WSL1 translation layer. For example:

  On Disco with gzip 1.9-3:

  $ file /bin/gzip
  /bin/gzip: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), 
dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 
3.2.0, BuildID[sha1]=efa859c26eaf8e035efe9a139361e2a60cd17b3e, stripped

  On Eoan with gzip 1.10-0ubuntu3:

  $ file /bin/gzip
  /bin/gzip: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), 
dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, 
BuildID[sha1]=bc0f5994544c2a469d04c914bf4bf44b4ded6040, for GNU/Linux 3.2.0, 
stripped

  Eoan ships with gzip 1.10, while Disco ships with gzip 1.9, but I do
  not believe this is an issue in 1.10 because this error does not occur
  when building gzip from GNU project source on Ubuntu Eoan.

  Justifications:

  WSL1 will need to be patched in future Windows builds for this change
  in ELF. However that patch will likely not be backported to older
  builds of Windows, including Windows Enterprise/Server 2019.

  To ensure Eoan can run on current and older builds of Windows Ubuntu
  should consider looking at how it's building gzip and see if it can be
  made to 'play nice' until WSL1 can be updated.

  This was originally reported here:
  https://github.com/microsoft/WSL/issues/4461

  Details:

  Description:Ubuntu Eoan Ermine (development branch)
  Release:19.10

  gzip:
    Installed: 1.10-0ubuntu3
    Candidate: 1.10-0ubuntu3
    Version table:
   *** 1.10-0ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  100 /var/lib/dpkg/status

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

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


[Touch-packages] [Bug 1855893] Re: Properly let PCM leave suspended state when hardware doesn't support PCM resume

2019-12-10 Thread Mathew Hodson
** Changed in: pulseaudio (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Properly let PCM leave suspended state when hardware doesn't support
  PCM resume

Status in HWE Next:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  [Impact]
  Headset Mic plugged into Dell WD19TB dock stops working after suspend/resume.

  [Fix]
  According to alia-lib's document, to make PCM properly leave suspended state, 
we only use snd_pcm_resume() if hardware support PCM resume.
  For hardware that doesn't support PCM resume, like snd-usb-audio on WD19TB 
dock, we should use snd_pcm_prepare(), snd_pcm_drop() or snd_pcm_drain() to 
make device leave suspended state. This patch defaults to use snd_pcm_drop() to 
achieve the goal.

  [Test]
  1. See if microphone on snd-usb-audio works in gnome-control-center/cheese.
  2. Suspend/resume.
  3. See if microphone still works in those apps.
  I can the issue is fixed after each suspend/resume cycle.

  [Regression Potential]
  Low. This fix makes PCM suspend/resume more reliable. No functional change 
intended. I also don't find any regression during some smoke test.

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

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


[Touch-packages] [Bug 1854689] Re: BlueZ 5.52 release

2019-12-10 Thread Mathew Hodson
** Tags added: upgrade-software-version

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

Title:
  BlueZ 5.52 release

Status in bluez package in Ubuntu:
  In Progress

Bug description:
  BlueZ 5.52 release:
  http://www.bluez.org/release-of-bluez-5-52/

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

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


[Touch-packages] [Bug 1733321] Re: network-manager ADT tests fail with on ppc64el with artful/linux 4.13.0.17.18

2019-12-10 Thread Mathew Hodson
** Tags added: testcase

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

Title:
  network-manager ADT tests fail with on ppc64el with artful/linux
  4.13.0.17.18

Status in network-manager package in Ubuntu:
  New
Status in network-manager source package in Artful:
  Won't Fix
Status in network-manager source package in Disco:
  New
Status in network-manager source package in Eoan:
  New
Status in network-manager source package in Focal:
  New

Bug description:
  [Impact]

  The killswitches-no-urfkill autopkgtest fails sometimes because nmcli
  reports the old state when it's called right after rfkill
  block/unblock. Adding a sleep before calling nmcli fixes the issue.

  ppc64el ADT log from failed testcase:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-artful/artful/ppc64el/n/network-
  manager/20171120_100719_28642@/log.gz

  Testcase output:
  -
  autopkgtest [10:04:48]: test killswitches-no-urfkill: [---
  make -C /lib/modules/4.13.0-17-generic/build 
KBUILD_SRC=/lib/modules/4.13.0-17-generic/build 
M=/tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests
  make[1]: Entering directory '/usr/src/linux-headers-4.13.0-17-generic'
    AR  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/built-in.o
    CC [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.o
    Building modules, stage 2.
    MODPOST 1 modules
    CC  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.mod.o
    LD [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.ko
  make[1]: Leaving directory '/usr/src/linux-headers-4.13.0-17-generic'
  ERROR: NM could not track device state.
  autopkgtest [10:05:20]: test killswitches-no-urfkill: ---]
  autopkgtest [10:05:20]: test killswitches-no-urfkill:  - - - - - - - - - - 
results - - - - - - - - - -
  killswitches-no-urfkill FAIL non-zero exit status 1
  -

  Package versions [artful/ppc64el]:
  network-manager 1.8.4-1ubuntu3
  linux-meta 4.13.0.17.18

  
  [Test Case]

  2.1. Download network-manager package source code
  $ apt-get source network-manager

  2.2. Run killswitches-no-urfkill testcase
  $ cd network-manager-1.8.4
  $ sudo ./debian/tests/killswitches-no-urfkill

  
  [Regression Potential]

  No regression potential. The fix touches only the testcase shipped
  with the source package and it doesn't change the binary package. The
  sleep time added is very small, so no possibility of causing testcase
  timeout.

  
  [Other Info]

  On ppc64el architecture, it was observed that a fix for systemd is
  also needed (see bug 1734908) for the testcase to be successful.

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

-- 
Mailing list: https://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   >