[Touch-packages] [Bug 1857182] [NEW] Unable to Google Online Account in Kubuntu 19.10

[Donnie Hanna]

Public bug reported:

Adding Google Online account in Kubuntu, i am able to enter my google username 
and password after that a message is received: Sign in with Google temporarily 
disabled for this app
This app has not been verified yet by Google in order to use Google Sign In.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: signon-ui-x11 0.17+18.04.20171027+really20160406-0ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
Uname: Linux 5.3.0-24-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: KDE
Date: Sat Dec 21 01:17:36 2019
ExecutablePath: /usr/bin/signon-ui
InstallationDate: Installed on 2019-12-20 (1 days ago)
InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: signon-ui
UpgradeStatus: No upgrade log present (probably fresh install)
XsessionErrors:
 (pcmanfm:9039): Gtk-WARNING **: 23:27:13.685: Unable to locate theme engine in 
module_path: "adwaita",
 (pcmanfm:9039): Gtk-WARNING **: 23:27:13.691: Unable to locate theme engine in 
module_path: "adwaita",

** Affects: signon-ui (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug eoan

** Attachment added: "Google_Online_Accounts.png"
   
https://bugs.launchpad.net/bugs/1857182/+attachment/5314441/+files/Google_Online_Accounts.png

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

Title:
  Unable to Google Online Account in Kubuntu 19.10

Status in signon-ui package in Ubuntu:
  New

Bug description:
  Adding Google Online account in Kubuntu, i am able to enter my google 
username and password after that a message is received: Sign in with Google 
temporarily disabled for this app
  This app has not been verified yet by Google in order to use Google Sign In.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: signon-ui-x11 0.17+18.04.20171027+really20160406-0ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Dec 21 01:17:36 2019
  ExecutablePath: /usr/bin/signon-ui
  InstallationDate: Installed on 2019-12-20 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: signon-ui
  UpgradeStatus: No upgrade log present (probably fresh install)
  XsessionErrors:
   (pcmanfm:9039): Gtk-WARNING **: 23:27:13.685: Unable to locate theme engine 
in module_path: "adwaita",
   (pcmanfm:9039): Gtk-WARNING **: 23:27:13.691: Unable to locate theme engine 
in module_path: "adwaita",

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

-- 
Mailing list: https://launchpad.net/~touch-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

[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 1849559] Re: /etc/dbus-1/system.d/wpa_supplicant.conf is in wrong location

[Francis Ginther]

** Tags added: id-5cf575c4e6712e6048974772

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

Title:
  /etc/dbus-1/system.d/wpa_supplicant.conf is in wrong location

Status in wpa package in Ubuntu:
  New

Bug description:
  The /etc/dbus-1/system.d/wpa_supplicant.conf is installed in the wrong
  location. It is a system-wide default config for dbus, and as such
  probably should be in /usr/share/dbus-1/system.d instead; like most
  other DBus definitions installed on a typical system.

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

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

[Touch-packages] [Bug 1774843] Re: apport python exception handler messes up python3.7

[Francis Ginther]

** Tags added: id-5de941fa03cfeb8f3edbe11c

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

Title:
  apport python exception handler messes up python3.7

Status in Apport:
  New
Status in apport package in Ubuntu:
  Triaged
Status in python-apt package in Ubuntu:
  Invalid
Status in apport source package in Focal:
  Triaged
Status in python-apt source package in Focal:
  Invalid

Bug description:
  it seems apport installs an exception hook whenever running python3.
  This hook is apparently installed for python3.7 too.
  This exception handler has a dependency on apt_pkg, which is a binary that is 
not compatible with python3.7 it seems (you can't import it, see below)

  As a result, whenever I run a python3.7 script and run into an exception 
(which happens often when writing code), I get an additional exception in the 
exception handler + a copy of the original exception, so three stacktraces in 
total.
  A solution would be to only install the exception hook for the system python  
i.e. python3.6

  
  $ lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  apport: 2.20.9-0ubuntu7
  python-apt: 1.6.0
  python3.7: 3.7.0~b3-1

  Demo with a trivial error:
  $ python3 -c 'print hello'
File "", line 1
  print hello
^
  SyntaxError: Missing parentheses in call to 'print'. Did you mean 
print(hello)?

  
  $ python3.7 -c 'print hello'
File "", line 1
  print hello
^
  SyntaxError: Missing parentheses in call to 'print'. Did you mean 
print(hello)?
  Error in sys.excepthook:
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 63, in 
apport_excepthook
  from apport.fileutils import likely_packaged, get_recent_crashes
File "/usr/lib/python3/dist-packages/apport/__init__.py", line 5, in 

  from apport.report import Report
File "/usr/lib/python3/dist-packages/apport/report.py", line 30, in 
  import apport.fileutils
File "/usr/lib/python3/dist-packages/apport/fileutils.py", line 23, in 

  from apport.packaging_impl import impl as packaging
File "/usr/lib/python3/dist-packages/apport/packaging_impl.py", line 24, in 

  import apt
File "/usr/lib/python3/dist-packages/apt/__init__.py", line 23, in 
  import apt_pkg
  ModuleNotFoundError: No module named 'apt_pkg'

  Original exception was:
File "", line 1
  print hello
^
  SyntaxError: Missing parentheses in call to 'print'. Did you mean 
print(hello)?


  Python 3.6.5 (default, Apr  1 2018, 05:46:30) 
  [GCC 7.3.0] on linux
  Type "help", "copyright", "credits" or "license" for more information.
  >>> import sys
  >>> sys.excepthook
  
  >>> import apt_pkg
  >>> apt_pkg.__file__
  '/usr/lib/python3/dist-packages/apt_pkg.cpython-36m-x86_64-linux-gnu.so'
  >>> 

  Python 3.7.0b3 (default, Mar 30 2018, 04:35:22) 
  [GCC 7.3.0] on linux
  Type "help", "copyright", "credits" or "license" for more information.
  >>> import sys
  >>> sys.excepthook
  
  >> import apt_pkg
  Traceback (most recent call last):
File "", line 1, in 
  ModuleNotFoundError: No module named 'apt_pkg'

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

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

[Touch-packages] [Bug 1849554] Re: Please move cache files to a different location

[Francis Ginther]

** Tags added: id-5cf575c4e6712e6048974772

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

Title:
  Please move cache files to a different location

Status in apparmor package in Ubuntu:
  Fix Released

Bug description:
  /etc/apparmor.d/cache is currently used to keep cache files for
  apparmor. Unfortunately, these files are in a location that is
  inconsistent with FHS guidelines for cache.

  Moreover, /etc is not a core path for Ubuntu Core 20, which means it
  is planned to not be writable; and to come directly from images.

  According to the FHS, the best location for apparmor cache files
  should be in a hierarchy under /var/cache.

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

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

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

[Francis Ginther]

** Tags added: id-5b9bc98090150323f87c64a2

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

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

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

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

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

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

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

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

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

[Touch-packages] [Bug 1849261] Re: Update systemd for ubuntu 18.04 with fix for interaction between OnFailure= and Restart=

[Francis Ginther]

** Tags added: id-5de127a738dabd05006e38e8

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

Title:
  Update systemd for ubuntu 18.04 with fix for interaction between
  OnFailure= and Restart=

Status in Ubuntu on IBM z Systems:
  In Progress
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 Disco:
  Fix Released
Status in systemd source package in Eoan:
  Fix Released

Bug description:
  [impact]

  services configured with both OnFailure= and Restart= directives will
  both start the failure service(s), as well as restarting itself.  The
  documentation (and later versions) indicate that OnFailure= services
  will only be started once the service actually does stop (due to
  failure) once its restart limit has been exceeded.

  [test case]

  create service files as:

  ubuntu@lp1849261-b:/etc/systemd/system$ cat test.service
  [Unit]
  OnFailure=failure.service

  [Service]
  ExecStart=/bin/sh -c '/bin/sleep 10; /bin/false'
  Restart=always

  ubuntu@lp1849261-b:/etc/systemd/system$ cat failure.service
  [Service]
  ExecStart=/bin/true

  perform daemon-reload, and then start test service:

  ubuntu@lp1849261-b:/etc/systemd/system$ sudo systemctl daemon-reload
  ubuntu@lp1849261-b:/etc/systemd/system$ sudo systemctl start test

  wait for a while for the test service to exit - at least 10 seconds,
  as that's what we configured in the service, although I have waited
  longer in this example.  Then check the journal for both test and
  failure services:

  ubuntu@lp1849261-b:/etc/systemd/system$ journalctl -b -u test
  -- Logs begin at Fri 2019-12-13 00:52:50 UTC, end at Fri 2019-12-13 01:18:34 
UTC. --
  Dec 13 01:17:43 lp1849261-b systemd[1]: Started test.service.
  Dec 13 01:17:53 lp1849261-b systemd[1]: test.service: Main process exited, 
code=exited, status=1/FAILURE
  Dec 13 01:17:53 lp1849261-b systemd[1]: test.service: Failed with result 
'exit-code'.
  Dec 13 01:17:53 lp1849261-b systemd[1]: test.service: Triggering OnFailure= 
dependencies.
  Dec 13 01:17:53 lp1849261-b systemd[1]: test.service: Service hold-off time 
over, scheduling restart.
  Dec 13 01:17:53 lp1849261-b systemd[1]: test.service: Scheduled restart job, 
restart counter is at 1.
  Dec 13 01:17:53 lp1849261-b systemd[1]: Stopped test.service.
  Dec 13 01:17:53 lp1849261-b systemd[1]: Started test.service.
  Dec 13 01:18:03 lp1849261-b systemd[1]: test.service: Main process exited, 
code=exited, status=1/FAILURE
  Dec 13 01:18:03 lp1849261-b systemd[1]: test.service: Failed with result 
'exit-code'.
  Dec 13 01:18:03 lp1849261-b systemd[1]: test.service: Triggering OnFailure= 
dependencies.
  Dec 13 01:18:04 lp1849261-b systemd[1]: test.service: Service hold-off time 
over, scheduling restart.
  Dec 13 01:18:04 lp1849261-b systemd[1]: test.service: Scheduled restart job, 
restart counter is at 2.
  Dec 13 01:18:04 lp1849261-b systemd[1]: Stopped test.service.
  Dec 13 01:18:04 lp1849261-b systemd[1]: Started test.service.
  Dec 13 01:18:14 lp1849261-b systemd[1]: test.service: Main process exited, 
code=exited, status=1/FAILURE
  Dec 13 01:18:14 lp1849261-b systemd[1]: test.service: Failed with result 
'exit-code'.
  Dec 13 01:18:14 lp1849261-b systemd[1]: test.service: Triggering OnFailure= 
dependencies.
  Dec 13 01:18:14 lp1849261-b systemd[1]: test.service: Service hold-off time 
over, scheduling restart.
  Dec 13 01:18:14 lp1849261-b systemd[1]: test.service: Scheduled restart job, 
restart counter is at 3.
  Dec 13 01:18:14 lp1849261-b systemd[1]: Stopped test.service.
  Dec 13 01:18:14 lp1849261-b systemd[1]: Started test.service.
  Dec 13 01:18:24 lp1849261-b systemd[1]: test.service: Main process exited, 
code=exited, status=1/FAILURE
  Dec 13 01:18:24 lp1849261-b systemd[1]: test.service: Failed with result 
'exit-code'.
  Dec 13 01:18:24 lp1849261-b systemd[1]: test.service: Triggering OnFailure= 
dependencies.
  Dec 13 01:18:24 lp1849261-b systemd[1]: test.service: Service hold-off time 
over, scheduling restart.
  Dec 13 01:18:24 lp1849261-b systemd[1]: test.service: Scheduled restart job, 
restart counter is at 4.
  Dec 13 01:18:24 lp1849261-b systemd[1]: Stopped test.service.
  Dec 13 01:18:24 lp1849261-b systemd[1]: Started test.service.
  Dec 13 01:18:34 lp1849261-b systemd[1]: test.service: Main process exited, 
code=exited, status=1/FAILURE
  Dec 13 01:18:34 lp1849261-b systemd[1]: test.service: Failed with result 
'exit-code'.
  Dec 13 01:18:34 lp1849261-b systemd[1]: test.service: Triggering OnFailure= 
dependencies.
  Dec 13 01:18:34 lp1849261-b systemd[1]: test.service: Service hold-off time 
over, scheduling restart.
  Dec 13 01:18:34 lp1849261-b systemd[1]: test.service: Scheduled restart job, 
restart counter is at 5.
  Dec 

[Touch-packages] [Bug 1856045] Re: capabilities set with setcap are not honoured

[Francis Ginther]

** Tags added: id-5dfbada861bbb0737ab3648f

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

Title:
  capabilities set with setcap are not honoured

Status in libcap2 package in Ubuntu:
  New
Status in libcap2 source package in Eoan:
  Confirmed

Bug description:
  Hi,

  In Ubuntu 19.10 I set capabilities as;

  setcap cap_net_admin,cap_sys_admin+ep /bin/ip
  getcap /bin/ip
  /bin/ip = cap_net_admin,cap_sys_admin+ep

  but;

  > ip addr add 20.20.20.20/32 dev lo
  RTNETLINK answers: Operation not permitted

  *exactly* the same works perfect on 18.04.3 LTS.

  BTW the set of a silly address on "lo" is just an example.
  Nothing works on Ubuntu 19.10

  Regards,

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: libcap2-bin 1:2.25-2
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  Date: Wed Dec 11 15:27:00 2019
  InstallationDate: Installed on 2019-12-09 (2 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: libcap2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1849560] Re: Please revise the files installed in /etc/

[Francis Ginther]

** Tags added: id-5cf575c4e6712e6048974772

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

Title:
  Please revise the files installed in /etc/

Status in openssh package in Ubuntu:
  New

Bug description:
  openssh-server and openssh-client install various files under /etc:

  /etc/ssh/*
  /etc/systemd/system/sshd.service

  Please see if these files can be moved elsewhere, in accordance with
  FHS: /etc should only contain files writable by the system
  administrator, and in Ubuntu Core 20 we should aim to have no writable
  files in /etc (as it will be included in images, avoid conflict
  resolution on upgrades).

  At a glance, it looks like /etc/systemd/system/sshd.service could be
  moved to /lib/systemd/system, and many of the files in /etc/ssh do
  have suitable locations elsewhere on the system, such as /var/lib/ for
  generated keys, /usr/share/ for default SSH configurations, etc.)

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

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

[Touch-packages] [Bug 1845529] Re: bash completion shows `awk: line 18: function gensub never defined` on `umount /dev/`

[Francis Ginther]

** Tags added: id-5ddff28c2475535c4124414c

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

Title:
  bash completion shows `awk: line 18: function gensub never defined` on
  `umount /dev/`

Status in bash-completion package in Ubuntu:
  Invalid
Status in ubuntu-meta package in Ubuntu:
  Invalid
Status in util-linux package in Ubuntu:
  Fix Released
Status in bash-completion source package in Eoan:
  Invalid
Status in gawk source package in Eoan:
  New
Status in mawk source package in Eoan:
  New
Status in ubuntu-meta source package in Eoan:
  New
Status in util-linux source package in Eoan:
  Fix Committed
Status in bash-completion source package in Focal:
  Invalid
Status in gawk source package in Focal:
  Invalid
Status in mawk source package in Focal:
  Invalid
Status in ubuntu-meta source package in Focal:
  Invalid
Status in util-linux source package in Focal:
  Fix Released
Status in Debian:
  Confirmed

Bug description:
  [Impact]
  Any user attempting to tab-complete from "umount /dev/" when running the bash 
shell.

  [Test cases]
  Steps to reproduce:
  1. Install Ubuntu MATE 19.10 using minimal desktop option
  2. Open terminal and enter `umount /dev/s` and then hit 

  Expected result:
  * bash completion works as expected

  Actual results:
  * bash completion does not work :

  $ umount /dev/awk: line 18: function gensub never defined
  awk: line 18: function gensub never defined
  awk: line 18: function gensub never defined
  awk: line 18: function gensub never defined

  $ umount /meawk: line 18: function gensub never defined
  awk: line 18: function gensub never defined
  awk: line 18: function gensub never defined
  awk: line 18: function gensub never defined

  
  [Regression potential]
  Since it is limited to a single file 
(/usr/share/bash-completion/completions/umount) and affects only it, as well as 
given that it currently does not work, I estimate this as a low risk change. 
Things to look out for as a regression would be if another previously-working 
completion would fail to work (ie. what if mount stops completing correctly, 
and works again if the fix is backed out?).

  ---

  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: bash-completion 1:2.9-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Thu Sep 26 18:46:59 2019
  Dependencies:

  InstallationDate: Installed on 2019-09-26 (0 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
  PackageArchitecture: all
  SourcePackage: bash-completion
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1851806] Re: 'module' object has no attribute 'O_PATH'

[Francis Ginther]

** Tags added: id-5dd454a1dd84728273703743

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

Title:
  'module' object has no attribute 'O_PATH'

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  I encountered the following exception in python-apport while
  encountering an exception `bup` which uses `python-apport`. I'm sure
  that the exception lies in the responsibility of `python-apport` (the
  `AttributeError` stacktrace is relevant):

  ```
  Traceback (most recent call last):
File "/usr/lib/bup/cmd/bup-index", line 269, in 
  update_index(rp, excluded_paths, exclude_rxs, xdev_exceptions=xexcept)
File "/usr/lib/bup/cmd/bup-index", line 191, in update_index
  mi.close()
File "/usr/lib/bup/bup/index.py", line 528, in close
  os.rename(self.tmpname, self.filename)
  OSError: [Errno 13] Permission denied
  Error in sys.excepthook:
  Traceback (most recent call last):
File "/usr/lib/bup/bup/helpers.py", line 916, in newhook
  return oldhook(exctype, value, traceback)
File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 109, in 
apport_excepthook
  pr.add_proc_info(extraenv=['PYTHONPATH', 'PYTHONHOME'])
File "/usr/lib/python2.7/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)
  AttributeError: 'module' object has no attribute 'O_PATH'

  Original exception was:
  Traceback (most recent call last):
File "/usr/lib/bup/cmd/bup-index", line 269, in 
  update_index(rp, excluded_paths, exclude_rxs, xdev_exceptions=xexcept)
File "/usr/lib/bup/cmd/bup-index", line 191, in update_index
  mi.close()
File "/usr/lib/bup/bup/index.py", line 528, in close
  os.rename(self.tmpname, self.filename)
  OSError: [Errno 13] Permission denied
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: python-apport 2.20.11-0ubuntu8.2
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportLog: Error: [Errno 13] Keine Berechtigung: '/var/log/apport.log'
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov  8 10:43:02 2019
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to eoan on 2019-10-25 (13 days ago)

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

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

[Touch-packages] [Bug 1857018] Re: apt-get: Can not downgrade dependencies or anything with -t

[Jarno Suni]

Well, actually I have thought a lot about this downgrading thing. I have 
contributed to ppa-purge and even made a PPA of that: 
https://launchpad.net/~jarnos/+archive/ubuntu/ppa-purge
I still have to fix it to keep auto installed packages auto installed, which is 
not very difficult.

I just thought of an alternative way to downgrade the manually installed
packages of a PPA or such together with their dependencies to given
distribution, but there would still be the task to remove the packages
of the PPA that are not needed.

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

Title:
   apt-get: Can not downgrade dependencies or anything with -t

Status in apt package in Ubuntu:
  Invalid

Bug description:
  Only the latter command downgrades the mythtv-frontend package (after
  removing the PPA from /etc/apt/sources.list.d/ and running 'apt
  update'):

  $ sudo apt-get install mythtv-frontend -s -V -t bionic
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  mythtv-frontend is already the newest version 
(2:30.0+fixes.201912012038.a27754a~ubuntu18.04.1).
  0 upgraded, 0 newly installed, 0 to remove and 8 not upgraded.

  $ sudo apt-get install mythtv-frontend/bionic -s -V
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Selected version '2:29.1+fixes.20180414.329c235-0ubuntu3' 
(Ubuntu:18.04/bionic [amd64]) for 'mythtv-frontend'
  Suggested packages:
 mythtv-backend (2:29.1+fixes.20180414.329c235-0ubuntu3)
 mythmusic (2:29.1+fixes.20180414.329c235-0ubuntu3)
 mythweather (2:29.1+fixes.20180414.329c235-0ubuntu3)
 mythgallery (2:29.1+fixes.20180414.329c235-0ubuntu3)
 mythgame (2:29.1+fixes.20180414.329c235-0ubuntu3)
  The following packages will be REMOVED:
 mythtv-dbg (2:30.0+fixes.201912012038.a27754a~ubuntu18.04.1)
  The following packages will be DOWNGRADED:
 mythtv-frontend (2:30.0+fixes.201912012038.a27754a~ubuntu18.04.1 => 
2:29.1+fixes.20180414.329c235-0ubuntu3)
  0 upgraded, 0 newly installed, 1 downgraded, 1 to remove and 4 not upgraded.
  Remv mythtv-dbg [2:30.0+fixes.201912012038.a27754a~ubuntu18.04.1]
  Inst mythtv-frontend [2:30.0+fixes.201912012038.a27754a~ubuntu18.04.1] 
(2:29.1+fixes.20180414.329c235-0ubuntu3 Ubuntu:18.04/bionic [amd64])
  Conf mythtv-frontend (2:29.1+fixes.20180414.329c235-0ubuntu3 
Ubuntu:18.04/bionic [amd64])

  I do not know, if there is a reason for the different behavior.
  Anyway, I want to be able to easily downgrade the depending packages, too, 
retaining their auto/manual status.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apt 1.6.12
  ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-37-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Dec 19 16:25:51 2019
  InstallationDate: Installed on 2019-05-08 (224 days ago)
  InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1853861] Re: [SRU] Unattended-upgrades silently does not apply updates when MinimalSteps is disabled and there are autoremovable kernels

[Francis Ginther]

** Tags added: id-5ddbf97425c5f4266c2b848a

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

Title:
  [SRU] Unattended-upgrades silently does not apply updates when
  MinimalSteps is disabled and there are autoremovable kernels

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Released
Status in unattended-upgrades source package in Bionic:
  Fix Released
Status in unattended-upgrades source package in Disco:
  Fix Released
Status in unattended-upgrades source package in Eoan:
  Fix Released

Bug description:
  [Impact]

   * When autoremovable kernel packages are present on the system, there are 
updates to apply and Unattended-Upgrade::MinimalSteps is set to "false", the 
autoremovable kernel packages are not removed and the updates are not applied.
   * The root cause is u-u not cleaning the dirty cache between operations and 
also relying on having a cache with packages marked to be installed when 
applying updates in one shot.
   * The fix is clearing the cache between operations and marking packages 
before installing them in one shot.

  [Test Case]

   * Install kernel-related packages, mark them as automatically installed to 
make them auto-removable ones.
   * Downgrade a few packages to a version lower than what is present in the 
security pocket.
   * Set Unattended-Upgrade::MinimalSteps to "false":
 # echo 'Unattended-Upgrade::MinimalSteps "false";' > 
/etc/apt/apt.conf.d/51unattended-upgrades-oneshot

   * Run u-u:
 # unattended-upgrade --verbose --debug

   * Observe fixed versions removing the kernel packages properly and
  also upgrading packages.

  [Regression Potential]

   * The changes introduce marking packages to install/upgrade and clearing the 
cache more often. The added operations slow down u-u, but clearing the cache 
adds a few 100 milliseconds on typical hardware and marking upgradable packages 
is also in the same range.
   * Functional regressions are unlikely due to those changes since the fixes 
are present in 19.04 and later releases and the extensive autopkgtest also 
covers when upgrades are performed in minimal steps.

  [Other Info]

   * While this bug has a security impact by holding back installation of 
security updates I don't recommend releasing the fix via the security pocket 
because this bug occurs only when the local configuration file of u-u is 
changed and u-u does not hold back upgrades with UCF-managed config file 
conflicts.
See: https://github.com/mvo5/unattended-upgrades/issues/168

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

-- 
Mailing list: https://launchpad.net/~touch-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

[Francis Ginther]

** Tags added: id-5dbd08153201707b96d7796f

-- 
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:
  New
Status in apport source package in Bionic:
  New
Status in apport source package in Disco:
  New
Status in apport source package in Eoan:
  New

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 1852772] Re: test_updates_interval fails on focal

[Francis Ginther]

** Tags added: id-5ddff3a8c61a0a7a58a83a70

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

Title:
  test_updates_interval fails on focal

Status in software-properties package in Ubuntu:
  Fix Released

Bug description:
  ==

  FAIL: test_updates_interval (tests.test_dbus.TestDBus)

  --

  Traceback (most recent call last):

File "/build/software-properties-0.98.6/tests/test_dbus.py", line 332, in 
test_updates_interval 
  self.assertTrue('APT::Periodic::Update-Package-Lists "1";' in config) 

  
  AssertionError: False is not true   

  Looking closer, while in the SetUpdateInterval() method in
  softwareproperties/dbus/SoftwarePropertiesDBus.py, days is of
  dbus.Int32 type. A simple print output shows:

  days=dbus.Int32(1)

  D-Bus is statically typed, unlike python. More details at:
  https://dbus.freedesktop.org/doc/dbus-python/tutorial.html#data-types

  I think once we're in the dbus method (SetUpdateInterval() method in
  softwareproperties/dbus/SoftwarePropertiesDBus.py) we can convert the
  dbus.Int32 to an int.

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

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

[Touch-packages] [Bug 1850608] Re: Segfaults trying to send crash report

[Francis Ginther]

** Tags added: id-5db9d1d5e211d16cb03620fe

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

Title:
  Segfaults trying to send crash report

Status in whoopsie package in Ubuntu:
  Fix Released

Bug description:
  After this morning's upgrade to "whoopsie 0.2.62ubuntu0.2"
  plus "libwhoopsie0 0.2.62ubuntu0.2"(fix to bug #1830865),
  whoopsie repeatedly crashes with a segfault (in what seems to be libc?).
  An excerpt from /var/log/syslog (slightly redacted):

  Oct 30 08:33:06 [REDACTED] systemd[1]: Started crash report submission daemon.
  Oct 30 08:33:06 [REDACTED] whoopsie[22414]: [08:33:06] Using lock path: 
/var/lock/whoopsie/lock
  Oct 30 08:33:06 [REDACTED] whoopsie[22414]: [08:33:06] The default IPv4 route 
is: /org/freedesktop/NetworkManager/ActiveConnection/1
  Oct 30 08:33:06 [REDACTED] whoopsie[22414]: [08:33:06] Not a paid data plan: 
/org/freedesktop/NetworkManager/ActiveConnection/1
  Oct 30 08:33:06 [REDACTED] whoopsie[22414]: [08:33:06] Found usable 
connection: /org/freedesktop/NetworkManager/ActiveConnection/1
  Oct 30 08:33:06 [REDACTED] whoopsie[22414]: [08:33:06] Parsing 
/var/crash/_usr_bin_kdeinit5.1000.crash.
  Oct 30 08:33:06 [REDACTED] whoopsie[22414]: [08:33:06] Uploading 
/var/crash/_usr_bin_kdeinit5.1000.crash.
  Oct 30 08:33:10 [REDACTED] kernel: [ 2129.099314] whoopsie[22414]: segfault 
at 7f4f878a4000 ip 7f4f866fe5e1 sp 7ffe348bed78 error 4 in 
libc-2.27.so[7f4f86591000+1e7000]
  Oct 30 08:33:11 [REDACTED] systemd[1]: whoopsie.service: Main process exited, 
code=dumped, status=11/SEGV
  Oct 30 08:33:11 [REDACTED] systemd[1]: whoopsie.service: Failed with result 
'core-dump'.
  Oct 30 08:33:11 [REDACTED] systemd[1]: whoopsie.service: Service hold-off 
time over, scheduling restart.
  Oct 30 08:33:11 [REDACTED] systemd[1]: whoopsie.service: Scheduled restart 
job, restart counter is at 133.
  Oct 30 08:33:11 [REDACTED] systemd[1]: Stopped crash report submission daemon.

  The above sequence of logged events repeats endlessly,
  with only(?) the times and whoospie PID changing.

  The problem can be (temporarily) stopped by `service whoopsie stop';
  using `service whoopsie start' resumes the above behaviour.
  Rebooting does not "fix".

  Manually running whoopsie shows the same behaviour:

  $ sudo /bin/sh -c 'export CRASH_DB_URL=https://daisy.ubuntu.com; exec 
whoopsie -f'
  [09:45:14] Using lock path: /var/lock/whoopsie/lock
  [09:45:14] The default IPv4 route is: 
/org/freedesktop/NetworkManager/ActiveConnection/1
  [09:45:14] Not a paid data plan: 
/org/freedesktop/NetworkManager/ActiveConnection/1
  [09:45:14] Found usable connection: 
/org/freedesktop/NetworkManager/ActiveConnection/1
  [09:45:14] Parsing /var/crash/_usr_bin_kdeinit5.1000.crash.
  [09:45:14] Uploading /var/crash/_usr_bin_kdeinit5.1000.crash.
  Segmentation fault
  $ 
  $ ls -la /var/crash/
  total 33340
  drwxrwsrwt  2 root whoopsie 4096 Oct 30 08:52 .
  drwxr-xr-x 16 root root 4096 Sep 14  2018 ..
  -rw-r--r--  1 root whoopsie  281 Oct 30 08:55 kexec_cmd
  -rwxrwxrwx  1 root whoopsie0 Oct 30 08:22 .lock
  -rw-r-  1 blf  whoopsie 17624101 Oct 30 08:53 
_usr_bin_kdeinit5.1000.crash
  -rw-rw-r--  1 blf  whoopsie0 Oct 30 08:22 
_usr_bin_kdeinit5.1000.upload
  -rw-r-  1 root whoopsie   398157 Oct 24 11:49 _usr_bin_sddm.0.crash
  -rw-r-  1 whoopsie whoopsie 15996866 Oct 30 08:22 
_usr_bin_whoopsie.108.crash
  -rw-r-  1 root whoopsie99379 Oct 22 15:07 _usr_sbin_inetd.0.crash
  $ 

  Because (as far as I know) the various `.crash' files MAY contain sensitive 
information,
  I have not attached them to this (public) bug report.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: whoopsie 0.2.62ubuntu0.2
  ProcVersionSignature: Ubuntu 4.15.0-66.75-generic 4.15.18
  Uname: Linux 4.15.0-66-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.8
  Architecture: amd64
  Date: Wed Oct 30 09:28:01 2019
  InstallationDate: Installed on 2016-10-07 (1118 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions: apport-noui N/A
  SourcePackage: whoopsie
  UpgradeStatus: Upgraded to bionic on 2018-08-18 (438 days ago)

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

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

[Touch-packages] [Bug 1856428] Re: Disable TLS1.0, TLS 1.1, DTLS1.0

[Francis Ginther]

** Tags added: id-5db1c4c64e98bd59adc18616

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

Title:
  Disable TLS1.0, TLS 1.1, DTLS1.0

Status in gnutls28 package in Ubuntu:
  New
Status in nss package in Ubuntu:
  New
Status in openssl package in Ubuntu:
  New

Bug description:
  Disable TLS 1.0, TLS1.1, DTLS1.0

  As part of focal commitment, we shall disable obsolete protocols by
  default.

  Users can override this behaviour with a config file.

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

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

[Touch-packages] [Bug 1855092] Re: [SRU] Please set MOTD_SHOWN=pam when MOTD was shown

[Francis Ginther]

** Tags added: id-5d78fc6cca6d1b77a77952cc

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

Title:
  [SRU] Please set MOTD_SHOWN=pam when MOTD was shown

Status in pam package in Ubuntu:
  Fix Released
Status in pam source package in Eoan:
  Fix Released

Bug description:
  [Impact]

    * Users of containers may never see the MOTD of the container if they are 
always to the container's shell without PAM being involved.
    * MOTD contains important information about the system's health including 
the security updates to be installed thus it is desired to show MOTD in 
container shells, too.
    * The fix in update-motd is creating a snippet in /etc/profile.d which 
shows MOTD, but only if UPDATE_MOTD is not set, to avoid printing MOTD twice.

  [Test Case]

   * Log in to the system, where PAM prints the MOTD.
   * After seeing the MOTD observe MOTD_SHOWN set:
     $ echo $MOTD_SHOWN
     pam
     $

  [Regression Potential]

   * The fix is simple thus it is unlikely to see any regression due to bad 
implementation.
   * The newly set environment variable may interact with existing software, 
but this variable seems to be not used:
   https://codesearch.debian.net/search?q=MOTD_SHOWN=1
   * With this change pam_motd module starts reporting errors and, most of the 
time, success. This is being refined at upstream to not report success, just 
PAM_IGNORE and errors: https://github.com/linux-pam/linux-pam/pull/157 . The 
behaviour change should not cause any issue on real-life systems since the 
return value of pam_motd is not used by default nor can we expect any 
configuration using it since it always returned PAM_IGNORE:

  $ grep -A1 -B5 pam_motd  /etc/pam.d/login

  # Prints the message of the day upon successful login.
  # (Replaces the `MOTD_FILE' option in login.defs)
  # This includes a dynamically generated part from /run/motd.dynamic
  # and a static (admin-editable) part from /etc/motd.
  sessionoptional   pam_motd.so motd=/run/motd.dynamic
  sessionoptional   pam_motd.so noupdate

  
  However, I plan reverting the behaviour change in the follow-up upload (LP: 
#1856703) right after it is finalized at upstream. I propose releasing this 
change in the current form to Eoan, because it is needed by the update-motd SRU 
and the ubuntu-meta SRU that enables printing MOTD in the Eoan Ubuntu WSL 
instances.

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

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

[Touch-packages] [Bug 1847967] Re: oem kernel packages treated differently from generic kernel ones

[Francis Ginther]

** Tags added: id-5de96a57d56e071554100fdb

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

Title:
  oem kernel packages treated differently from generic kernel ones

Status in OEM Priority Project:
  New
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Bionic:
  In Progress
Status in apport source package in Disco:
  In Progress
Status in apport source package in Eoan:
  In Progress
Status in apport source package in Focal:
  Fix Released

Bug description:
  [SRU Justification]

  [Impact]
  When `apport-bug linux` was executed on systems with linux-oem, 
linux-oem-osp1 kernels, many details are not included as generic linux kernel 
does. Alsa info, dmesg, lspci, lsusb, DMI, etc. are missing.

  [Fix]
  Fix already merged in Focal: 
https://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu/focal/apport/ubuntu/revision/2724
 .

  SRU merge proposals in:
  * 
https://code.launchpad.net/~vicamo/ubuntu/bionic/apport/bug-1847967/+merge/376380
  * 
https://code.launchpad.net/~vicamo/ubuntu/disco/apport/bug-1847967/+merge/376381
  * 
https://code.launchpad.net/~vicamo/ubuntu/eoan/apport/bug-1847967/+merge/374263

  [Test Case]
  1. Boot with linux-oem or linux-oem-osp1 kernel and try to collect apport 
logs with:

$ apport-cli --save saved.apport linux-oem-osp1

  2. Make sure the report contains PCI/ALSA/DMI/Sysfs info.

  [Regression Potential]
  Low.

   original bug description 

  When `apport-bug linux` was executed on systems with linux-oem, linux-
  oem-osp1 kernels, many details are not included as generic linux
  kernel does. Alsa info, dmesg, lspci, lsusb, DMI, etc. are missing.

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

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

[Touch-packages] [Bug 1658556] Re: watch -c --differences=permanent misbehaves (highlights everything)

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: procps (Ubuntu)
   Status: New => Confirmed

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

Title:
  watch -c --differences=permanent misbehaves (highlights everything)

Status in procps package in Ubuntu:
  Confirmed

Bug description:
  If the watch -c and --differences=permanent options are combined, then
  upon the first update _every_ character is highlighted even if nothing
  has ever changed.

  It appears that -c ("Interpret ANSI color and style sequences")
  tickles a bug in the persistence logic.  Regular non-permanent
  highlighting (with option -d) works okay with -c.

  STEPS TO REPRODUCE:

  1.  /usr/bin/watch -c --differences=permanent -n 1 echo This never
  changes

  RESULTS:  After one second all output is highlighted

  EXPECTED RESULTS: No highlighting until something changes

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: procps 2:3.3.10-4ubuntu2.3
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Jan 22 17:35:09 2017
  InstallationDate: Installed on 2013-08-06 (1266 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: procps
  UpgradeStatus: Upgraded to xenial on 2016-05-11 (257 days ago)

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

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

[Touch-packages] [Bug 1857123] [NEW] IPv4 addresses are not assigned in LXC with systemd 244.1

[Balint Reczey]

Public bug reported:

triaging

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


** Tags: block-proposed

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

Title:
  IPv4 addresses are not assigned in LXC with systemd 244.1

Status in systemd package in Ubuntu:
  New

Bug description:
  triaging

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

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

[Touch-packages] [Bug 1798400]

[Sergio Callegari]

The bug is also confirmed in the ubuntu launchpad at
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1798400.

Users there are reporting that they are experiencing the issue in ubuntu
(from bionic, I think) and gentoo. This adds to the reports in fedora
and to the confirmation here on arch linux.

I think that this is enough to mark as "NEW"

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

Title:
  Regression: cannot use impress remote over bluetooth with ubuntu
  bionic

Status in LibreOffice:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in libreoffice package in Fedora:
  Unknown

Bug description:
  Trying to use the impress remote
  (https://wiki.documentfoundation.org/Impress_Remote) over bluetooth
  with libreoffice over ubuntu bionic fails.

  The handset errors out that it cannot connect with Libreoffice on the
  computer even if the bluetooth adapter on the handset and on the
  computer are correctly paired.

  This does not seem to be an issue in the Libreoffice or in the impress
  remote code:

  - I have tested also past LibO versions
  - The Impress remote codebase has not changed recently

  This used to work on the same hardware (headset and laptop) with
  ubuntu 16.04.

  Hence the issue seems to be in a regression in the ubuntu bluetooth
  stack.

  To replicate:

  1) Install Libreoffice on Ubuntu bionic (either from the ubuntu repo
  or with the deb packages from the document fundation)

  2) Assure that your computer has bluetooth

  3) Install impress remote on an android handset (either from the play
  store of via fdroid)

  4) Assure that "remote control" is enabled in impress
  Tools>Options>Impress>General

  5) Pair the bluetooth adapters in the laptop and in the computer

  6) Open a presentation on the laptop

  7) Open the remote on the handset, got to the bluetooth pane see the
  computer there, touch it

  8) See the impress remote erroring out

  Most likely you will also get a bluetooth error on dmesg

  RFCOMM server failed for LibreOffice Impress Remote: rfcomm_bind:
  Address already in use (98)

  Same issue was reported for fedora

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Oct 17 16:57:29 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-12-12 (1769 days ago)
  InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Notebook W740SU
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic 
root=/dev/mapper/zagar_ssd--vg-root ro quiet splash 
resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: Upgraded to bionic on 2018-06-08 (131 days ago)
  dmi.bios.date: 10/02/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W740SU
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: W740SU
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 00:C2:C6:1A:28:71  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN ISCAN 
RX bytes:245088 acl:15156 sco:0 events:1266 errors:0
TX bytes:15571 acl:402 sco:1 commands:131 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1798400/+subscriptions

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

[Touch-packages] [Bug 1798400]

[Sergio Callegari]

Andrzej, I am CC-ing you on this, because I believe that you were one of
the original corder of the BT code for the impress remote on linux. I
hope that you may able to provide some advice on this. If I'm wrong,
please take my apology for the noise.

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

Title:
  Regression: cannot use impress remote over bluetooth with ubuntu
  bionic

Status in LibreOffice:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in libreoffice package in Fedora:
  Unknown

Bug description:
  Trying to use the impress remote
  (https://wiki.documentfoundation.org/Impress_Remote) over bluetooth
  with libreoffice over ubuntu bionic fails.

  The handset errors out that it cannot connect with Libreoffice on the
  computer even if the bluetooth adapter on the handset and on the
  computer are correctly paired.

  This does not seem to be an issue in the Libreoffice or in the impress
  remote code:

  - I have tested also past LibO versions
  - The Impress remote codebase has not changed recently

  This used to work on the same hardware (headset and laptop) with
  ubuntu 16.04.

  Hence the issue seems to be in a regression in the ubuntu bluetooth
  stack.

  To replicate:

  1) Install Libreoffice on Ubuntu bionic (either from the ubuntu repo
  or with the deb packages from the document fundation)

  2) Assure that your computer has bluetooth

  3) Install impress remote on an android handset (either from the play
  store of via fdroid)

  4) Assure that "remote control" is enabled in impress
  Tools>Options>Impress>General

  5) Pair the bluetooth adapters in the laptop and in the computer

  6) Open a presentation on the laptop

  7) Open the remote on the handset, got to the bluetooth pane see the
  computer there, touch it

  8) See the impress remote erroring out

  Most likely you will also get a bluetooth error on dmesg

  RFCOMM server failed for LibreOffice Impress Remote: rfcomm_bind:
  Address already in use (98)

  Same issue was reported for fedora

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Oct 17 16:57:29 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-12-12 (1769 days ago)
  InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Notebook W740SU
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic 
root=/dev/mapper/zagar_ssd--vg-root ro quiet splash 
resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: Upgraded to bionic on 2018-06-08 (131 days ago)
  dmi.bios.date: 10/02/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W740SU
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: W740SU
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 00:C2:C6:1A:28:71  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN ISCAN 
RX bytes:245088 acl:15156 sco:0 events:1266 errors:0
TX bytes:15571 acl:402 sco:1 commands:131 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1798400/+subscriptions

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

[Touch-packages] [Bug 1857118] [NEW] Build pcscd with --enable-filter option

[Kazuhiro Suzuki]

Public bug reported:

This is a feature request. I'd like to use filter features[1] of pcscd.
To activate it, could you build pcsc-lite with "--enable-filter" option
in debian/rules? Thanks.

[1]: https://ludovicrousseau.blogspot.com/2015/12/remove-andor-
customize-pcsc-reader-names.html

** Affects: pcsc-lite (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Build pcscd with --enable-filter option

Status in pcsc-lite package in Ubuntu:
  New

Bug description:
  This is a feature request. I'd like to use filter features[1] of
  pcscd. To activate it, could you build pcsc-lite with "--enable-
  filter" option in debian/rules? Thanks.

  [1]: https://ludovicrousseau.blogspot.com/2015/12/remove-andor-
  customize-pcsc-reader-names.html

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

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

[Touch-packages] [Bug 1798400] Re: Regression: cannot use impress remote over bluetooth with ubuntu bionic

[Bug Watch Updater]

** Changed in: df-libreoffice
   Status: New => Confirmed

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

Title:
  Regression: cannot use impress remote over bluetooth with ubuntu
  bionic

Status in LibreOffice:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in libreoffice package in Fedora:
  Unknown

Bug description:
  Trying to use the impress remote
  (https://wiki.documentfoundation.org/Impress_Remote) over bluetooth
  with libreoffice over ubuntu bionic fails.

  The handset errors out that it cannot connect with Libreoffice on the
  computer even if the bluetooth adapter on the handset and on the
  computer are correctly paired.

  This does not seem to be an issue in the Libreoffice or in the impress
  remote code:

  - I have tested also past LibO versions
  - The Impress remote codebase has not changed recently

  This used to work on the same hardware (headset and laptop) with
  ubuntu 16.04.

  Hence the issue seems to be in a regression in the ubuntu bluetooth
  stack.

  To replicate:

  1) Install Libreoffice on Ubuntu bionic (either from the ubuntu repo
  or with the deb packages from the document fundation)

  2) Assure that your computer has bluetooth

  3) Install impress remote on an android handset (either from the play
  store of via fdroid)

  4) Assure that "remote control" is enabled in impress
  Tools>Options>Impress>General

  5) Pair the bluetooth adapters in the laptop and in the computer

  6) Open a presentation on the laptop

  7) Open the remote on the handset, got to the bluetooth pane see the
  computer there, touch it

  8) See the impress remote erroring out

  Most likely you will also get a bluetooth error on dmesg

  RFCOMM server failed for LibreOffice Impress Remote: rfcomm_bind:
  Address already in use (98)

  Same issue was reported for fedora

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Oct 17 16:57:29 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-12-12 (1769 days ago)
  InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Notebook W740SU
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic 
root=/dev/mapper/zagar_ssd--vg-root ro quiet splash 
resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: Upgraded to bionic on 2018-06-08 (131 days ago)
  dmi.bios.date: 10/02/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W740SU
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: W740SU
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 00:C2:C6:1A:28:71  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN ISCAN 
RX bytes:245088 acl:15156 sco:0 events:1266 errors:0
TX bytes:15571 acl:402 sco:1 commands:131 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1798400/+subscriptions

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

[Touch-packages] [Bug 1857118] Re: Build pcscd with --enable-filter option

[Ludovic Rousseau]

I can provide a special package for you if you want.

Contact me by email.

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

Title:
  Build pcscd with --enable-filter option

Status in pcsc-lite package in Ubuntu:
  New

Bug description:
  This is a feature request. I'd like to use filter features[1] of
  pcscd. To activate it, could you build pcsc-lite with "--enable-
  filter" option in debian/rules? Thanks.

  [1]: https://ludovicrousseau.blogspot.com/2015/12/remove-andor-
  customize-pcsc-reader-names.html

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

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

[Touch-packages] [Bug 1856997] Re: Nvidia driver is not working / not supported

[Eduardo dos Santos Barretto]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  Nvidia driver is not working / not supported

Status in xorg package in Ubuntu:
  New

Bug description:
  Nvidia driver is not working / not supported

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CompositorRunning: None
  Date: Thu Dec 19 15:58:21 2019
  DistUpgraded: 2019-12-19 15:24:18,069 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 435.21, 5.3.0-24-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation TU116 [GeForce GTX 1660] [10de:2184] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd TU116 [GeForce GTX 1660] 
[1458:3fc8]
  InstallationDate: Installed on 2019-12-10 (8 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: Gigabyte Technology Co., Ltd. H110M-H
  ProcEnviron:
   LANGUAGE=en_IN:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=278e84d9-0ed9-4039-b35a-37a9366865af ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to eoan on 2019-12-19 (0 days ago)
  dmi.bios.date: 12/03/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: C4
  dmi.board.asset.tag: Default string
  dmi.board.name: H110M-H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrC4:bd12/03/2018:svnGigabyteTechnologyCo.,Ltd.:pnH110M-H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnH110M-H-CF:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: H110M-H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  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/xorg/+bug/1856997/+subscriptions

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

[Touch-packages] [Bug 1857145] [NEW] printer behaves erratically - detected ok, message says its printing, but no printout. Sometimes it prints, sometimes it does not print.

[Hemant Desai]

Public bug reported:


hemant@hemant-Vostro-3268:~$ lsmod | grep usb
rtsx_usb_ms24576  0
memstick   20480  1 rtsx_usb_ms
btusb  49152  0
btrtl  20480  1 btusb
btbcm  16384  1 btusb
btintel24576  1 btusb
bluetooth 557056  34 btrtl,btintel,btbcm,bnep,ath3k,btusb,rfcomm
usblp  24576  0
rtsx_usb_sdmmc 28672  0
usbhid 53248  0
hid   126976  2 usbhid,hid_generic
rtsx_usb   24576  2 rtsx_usb_sdmmc,rtsx_usb_ms

hemant@hemant-Vostro-3268:~$ tail -f /var/log/syslog 
Dec 20 20:14:28 hemant-Vostro-3268 canonical-livepatch[966]: Updated last-check.
Dec 20 20:14:28 hemant-Vostro-3268 canonical-livepatch[966]: No updates 
available at this time.
Dec 20 20:14:28 hemant-Vostro-3268 canonical-livepatch[966]: No payload 
available.
Dec 20 20:14:42 hemant-Vostro-3268 dbus-daemon[1084]: [session uid=1000 
pid=1084] Activating service name='org.gnome.ChromeGnomeShell' requested by 
':1.132' (uid=1000 pid=6315 comm="/usr/bin/python3 /usr/bin/chrome-gnome-shell 
chrom" label="unconfined")
Dec 20 20:14:42 hemant-Vostro-3268 dbus-daemon[1084]: [session uid=1000 
pid=1084] Successfully activated service 'org.gnome.ChromeGnomeShell'
Dec 20 20:17:01 hemant-Vostro-3268 CRON[6441]: (root) CMD (   cd / && run-parts 
--report /etc/cron.hourly)
Dec 20 20:17:39 hemant-Vostro-3268 kernel: [ 3828.347641] usb 1-7: USB 
disconnect, device number 12
Dec 20 20:17:39 hemant-Vostro-3268 kernel: [ 3828.347921] usblp1: removed
Dec 20 20:17:39 hemant-Vostro-3268 upowerd[1287]: unhandled action 'unbind' on 
/sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0
Dec 20 20:17:39 hemant-Vostro-3268 upowerd[1287]: unhandled action 'unbind' on 
/sys/devices/pci:00/:00:14.0/usb1/1-7
Dec 20 20:18:51 hemant-Vostro-3268 kernel: [ 3899.785488] usb 1-7: new 
high-speed USB device number 13 using xhci_hcd
Dec 20 20:18:51 hemant-Vostro-3268 kernel: [ 3899.935000] usb 1-7: New USB 
device found, idVendor=04f9, idProduct=0062, bcdDevice= 1.00
Dec 20 20:18:51 hemant-Vostro-3268 kernel: [ 3899.935005] usb 1-7: New USB 
device strings: Mfr=1, Product=2, SerialNumber=3
Dec 20 20:18:51 hemant-Vostro-3268 kernel: [ 3899.935008] usb 1-7: Product: 
HL-L2320D series
Dec 20 20:18:51 hemant-Vostro-3268 kernel: [ 3899.935011] usb 1-7: 
Manufacturer: Brother
Dec 20 20:18:51 hemant-Vostro-3268 kernel: [ 3899.935013] usb 1-7: 
SerialNumber: E73793L4N593434
Dec 20 20:18:51 hemant-Vostro-3268 kernel: [ 3899.940171] usblp 1-7:1.0: 
usblp1: USB Bidirectional printer dev 13 if 0 alt 0 proto 2 vid 0x04F9 pid 
0x0062
Dec 20 20:18:51 hemant-Vostro-3268 upowerd[1287]: unhandled action 'bind' on 
/sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0
Dec 20 20:18:51 hemant-Vostro-3268 upowerd[1287]: unhandled action 'bind' on 
/sys/devices/pci:00/:00:14.0/usb1/1-7
^C


hemant@hemant-Vostro-3268:~$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 007: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
Bus 001 Device 013: ID 04f9:0062 Brother Industries, Ltd 
Bus 001 Device 011: ID 413c:2113 Dell Computer Corp. 
Bus 001 Device 004: ID 04ca:009b Lite-On Technology Corp. 
Bus 001 Device 008: ID 0cf3:e005 Atheros Communications, Inc. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

hemant@hemant-Vostro-3268:~$ ls -l /dev/usb/lp* /dev/bus/usb/*/*
crw-rw-r--  1 root root 189,   0 Dec 20 18:39 /dev/bus/usb/001/001
crw-rw-r--  1 root root 189,   3 Dec 20 18:39 /dev/bus/usb/001/004
crw-rw-r--  1 root root 189,   6 Dec 20 18:39 /dev/bus/usb/001/007
crw-rw-r--  1 root root 189,   7 Dec 20 18:39 /dev/bus/usb/001/008
crw-rw-r--  1 root root 189,  10 Dec 20 19:49 /dev/bus/usb/001/011
crw-rw-r--+ 1 root lp   189,  12 Dec 20 20:18 /dev/bus/usb/001/013
crw-rw-r--  1 root root 189, 128 Dec 20 18:39 /dev/bus/usb/002/001
crw-rw  1 root lp   180,   1 Dec 20 20:18 /dev/usb/lp1

hemant@hemant-Vostro-3268:~$ sudo usb_printerid /dev/usb/lp1
[sudo] password for hemant: 
GET_DEVICE_ID string:
MFG:Brother;CMD:PJL,HBP;MDL:HL-L2320D series;CLS:PRINTER;CID:Brother Laser 
Type1;
hemant@hemant-Vostro-3268:~$ lpinfo -v
network http
network lpd
network ipp
network socket
network ipps
file cups-brf:/
network beh
network https
serial serial:/dev/ttyS0?baud=115200
direct hp
direct usb://Brother/HL-L2320D%20series?serial=E73793L4N593434
direct hpfax
hemant@hemant-Vostro-3268:~$

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: cups 2.2.7-1ubuntu2.7
ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21
Uname: Linux 5.0.0-37-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Dec 20 21:09:23 2019
InstallationDate: Installed on 2019-12-16 (4 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
Lpstat:
 device for Brother-HL-L2320D-series: 

[Touch-packages] [Bug 1857145] Re: printer behaves erratically - detected ok, message says its printing, but no printout. Sometimes it prints, sometimes it does not print.

[Hemant Desai]

Would appreciate any help. It used to work perfectly without a hitch for
last 2 years.

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

Title:
  printer behaves erratically - detected ok, message says its printing,
  but no printout. Sometimes it prints, sometimes it does not print.

Status in cups package in Ubuntu:
  New

Bug description:
  
  hemant@hemant-Vostro-3268:~$ lsmod | grep usb
  rtsx_usb_ms24576  0
  memstick   20480  1 rtsx_usb_ms
  btusb  49152  0
  btrtl  20480  1 btusb
  btbcm  16384  1 btusb
  btintel24576  1 btusb
  bluetooth 557056  34 btrtl,btintel,btbcm,bnep,ath3k,btusb,rfcomm
  usblp  24576  0
  rtsx_usb_sdmmc 28672  0
  usbhid 53248  0
  hid   126976  2 usbhid,hid_generic
  rtsx_usb   24576  2 rtsx_usb_sdmmc,rtsx_usb_ms

  hemant@hemant-Vostro-3268:~$ tail -f /var/log/syslog 
  Dec 20 20:14:28 hemant-Vostro-3268 canonical-livepatch[966]: Updated 
last-check.
  Dec 20 20:14:28 hemant-Vostro-3268 canonical-livepatch[966]: No updates 
available at this time.
  Dec 20 20:14:28 hemant-Vostro-3268 canonical-livepatch[966]: No payload 
available.
  Dec 20 20:14:42 hemant-Vostro-3268 dbus-daemon[1084]: [session uid=1000 
pid=1084] Activating service name='org.gnome.ChromeGnomeShell' requested by 
':1.132' (uid=1000 pid=6315 comm="/usr/bin/python3 /usr/bin/chrome-gnome-shell 
chrom" label="unconfined")
  Dec 20 20:14:42 hemant-Vostro-3268 dbus-daemon[1084]: [session uid=1000 
pid=1084] Successfully activated service 'org.gnome.ChromeGnomeShell'
  Dec 20 20:17:01 hemant-Vostro-3268 CRON[6441]: (root) CMD (   cd / && 
run-parts --report /etc/cron.hourly)
  Dec 20 20:17:39 hemant-Vostro-3268 kernel: [ 3828.347641] usb 1-7: USB 
disconnect, device number 12
  Dec 20 20:17:39 hemant-Vostro-3268 kernel: [ 3828.347921] usblp1: removed
  Dec 20 20:17:39 hemant-Vostro-3268 upowerd[1287]: unhandled action 'unbind' 
on /sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0
  Dec 20 20:17:39 hemant-Vostro-3268 upowerd[1287]: unhandled action 'unbind' 
on /sys/devices/pci:00/:00:14.0/usb1/1-7
  Dec 20 20:18:51 hemant-Vostro-3268 kernel: [ 3899.785488] usb 1-7: new 
high-speed USB device number 13 using xhci_hcd
  Dec 20 20:18:51 hemant-Vostro-3268 kernel: [ 3899.935000] usb 1-7: New USB 
device found, idVendor=04f9, idProduct=0062, bcdDevice= 1.00
  Dec 20 20:18:51 hemant-Vostro-3268 kernel: [ 3899.935005] usb 1-7: New USB 
device strings: Mfr=1, Product=2, SerialNumber=3
  Dec 20 20:18:51 hemant-Vostro-3268 kernel: [ 3899.935008] usb 1-7: Product: 
HL-L2320D series
  Dec 20 20:18:51 hemant-Vostro-3268 kernel: [ 3899.935011] usb 1-7: 
Manufacturer: Brother
  Dec 20 20:18:51 hemant-Vostro-3268 kernel: [ 3899.935013] usb 1-7: 
SerialNumber: E73793L4N593434
  Dec 20 20:18:51 hemant-Vostro-3268 kernel: [ 3899.940171] usblp 1-7:1.0: 
usblp1: USB Bidirectional printer dev 13 if 0 alt 0 proto 2 vid 0x04F9 pid 
0x0062
  Dec 20 20:18:51 hemant-Vostro-3268 upowerd[1287]: unhandled action 'bind' on 
/sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0
  Dec 20 20:18:51 hemant-Vostro-3268 upowerd[1287]: unhandled action 'bind' on 
/sys/devices/pci:00/:00:14.0/usb1/1-7
  ^C

  
  hemant@hemant-Vostro-3268:~$ lsusb
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 007: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
  Bus 001 Device 013: ID 04f9:0062 Brother Industries, Ltd 
  Bus 001 Device 011: ID 413c:2113 Dell Computer Corp. 
  Bus 001 Device 004: ID 04ca:009b Lite-On Technology Corp. 
  Bus 001 Device 008: ID 0cf3:e005 Atheros Communications, Inc. 
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  hemant@hemant-Vostro-3268:~$ ls -l /dev/usb/lp* /dev/bus/usb/*/*
  crw-rw-r--  1 root root 189,   0 Dec 20 18:39 /dev/bus/usb/001/001
  crw-rw-r--  1 root root 189,   3 Dec 20 18:39 /dev/bus/usb/001/004
  crw-rw-r--  1 root root 189,   6 Dec 20 18:39 /dev/bus/usb/001/007
  crw-rw-r--  1 root root 189,   7 Dec 20 18:39 /dev/bus/usb/001/008
  crw-rw-r--  1 root root 189,  10 Dec 20 19:49 /dev/bus/usb/001/011
  crw-rw-r--+ 1 root lp   189,  12 Dec 20 20:18 /dev/bus/usb/001/013
  crw-rw-r--  1 root root 189, 128 Dec 20 18:39 /dev/bus/usb/002/001
  crw-rw  1 root lp   180,   1 Dec 20 20:18 /dev/usb/lp1

  hemant@hemant-Vostro-3268:~$ sudo usb_printerid /dev/usb/lp1
  [sudo] password for hemant: 
  GET_DEVICE_ID string:
  MFG:Brother;CMD:PJL,HBP;MDL:HL-L2320D series;CLS:PRINTER;CID:Brother Laser 
Type1;
  hemant@hemant-Vostro-3268:~$ lpinfo -v
  network http
  network lpd
  network ipp
  network socket
  network ipps
  file cups-brf:/
  network beh
  network https
  serial serial:/dev/ttyS0?baud=115200
  direct hp
  direct 

[Touch-packages] [Bug 1731798] Re: package unattended-upgrades 0.90ubuntu0.7 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

[Balint Reczey]

IMO this is fixed in latest unattended-upgrades version available via
-updates.

** Changed in: unattended-upgrades (Ubuntu)
   Status: New => Fix Released

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

Title:
  package unattended-upgrades 0.90ubuntu0.7 failed to install/upgrade:
  subprocess new pre-removal script returned error exit status 1

Status in unattended-upgrades package in Ubuntu:
  Fix Released

Bug description:
  My ubuntu system locks up regularly. Bugs I've reported about this get
  closed for inattention, after being ignored, and queries about how to
  do basic debugging get the same treatment, so I just power cycle
  whenever it happens again.

  This time the lock up happened while the GUI upgrade-everything-to-
  latest tool was running.

  When I power cycled the box to recover, the system was unusable -
  flashing "system problem detected" popups, none staying stable long
  enough to respond.

  ssh + "sudo apt-get update" + "sudo apt-get upgrade" pointed me to
  "sudo dpkg --configure -a"

  That command reported numerous errors - I don't know which of them are
  "normal" for this system, but hidden by the GUI, and which are new.

  But it got the system semi-usable from the GUI, so now I'm clicking on
  "yes, report it" for the many pop-ups, of which this is one.

  FWIW, unattended-upgrades is one of the ones "dpkg --reconfigure -a"
  complained about.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 0.90ubuntu0.8
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Uname: Linux 4.4.0-93-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Sun Nov 12 11:21:07 2017
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2012-04-26 (2026 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: unattended-upgrades
  Title: package unattended-upgrades 0.90ubuntu0.7 failed to install/upgrade: 
subprocess new pre-removal script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2017-03-31 (226 days ago)
  mtime.conffile..etc.apt.apt.conf.d.50unattended-upgrades: 
2017-06-25T18:42:16.676378

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

-- 
Mailing list: https://launchpad.net/~touch-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

[Steve Langasek]

Hello Hayden, or anyone else affected,

Accepted binutils into eoan-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/binutils/2.33-2ubuntu1.2 in a few
hours, and then in the -proposed repository.

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

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

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

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

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

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

  

[Touch-packages] [Bug 1002978] Re: [meta-bug] Inverted Internal microphone (phase inversion)

[vlad]

Same problem on Lenovo Ideapad 320-15IKB

** Changed in: alsa-driver (Ubuntu)
   Status: Expired => Confirmed

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

Title:
  [meta-bug] Inverted Internal microphone (phase inversion)

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  This is a metabug for all machines that are having phase inverted
  internal microphones.

  If your internal mic is either completely silent (no signal), or you
  can possibly pick a very small sound, with much background noise, even
  though you have set gain to maximum, there is something you could try.

  Install the pavucontrol application, start it and go to the "Input Devices" 
tab. Unlock the channels (there is a keylock icon), then mute the right channel 
while keeping the left channel at the volume you want.
  If the internal mic is now working correctly, you have an inverted internal 
mic, so that your right channel cancels out the left one.

  (If you're not running PulseAudio, you can try doing the same through
  AlsaMixer instead (see https://wiki.ubuntu.com/Audio/Alsamixer ), try
  changing "Capture" level or "Internal Mic" or "Internal Mic Boost"
  using the Q,E,Z,C keys.)

  If so, please file a separate bug against the alsa-driver for your
  issue, make sure hardware info gets attached to it (either alsa-info
  as per https://wiki.ubuntu.com/Audio/AlsaInfo or the standard ones
  that follows when you do "ubuntu-bug alsa-driver" ), then write a
  comment in this bug, with your machine name and a pointer to the other
  bug.

  As time permits, I'll try to work on fixing them for the next Ubuntu release. 
Thanks!
   -- David Henningsson

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

-- 
Mailing list: https://launchpad.net/~touch-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

[Balint Reczey]

Verified binutils 2.33-2ubuntu1.2 by rebuilding gzip in the Bileto PPA
with new binutils and checking the rebuilt gzip binary:

root@ee-dwz:~# wget 
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3878/+build/18334107/+files/gzip_1.10-0ubuntu3.1_amd64.deb
--2019-12-20 17:50:02--  
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3878/+build/18334107/+files/gzip_1.10-0ubuntu3.1_amd64.deb
Resolving launchpad.net (launchpad.net)... 91.189.89.222, 91.189.89.223, 
2001:67c:1560:8003::8003, ...
Connecting to launchpad.net (launchpad.net)|91.189.89.222|:443... connected.
HTTP request sent, awaiting response... 303 See Other
Location: 
https://launchpadlibrarian.net/456546671/gzip_1.10-0ubuntu3.1_amd64.deb 
[following]
--2019-12-20 17:50:03--  
https://launchpadlibrarian.net/456546671/gzip_1.10-0ubuntu3.1_amd64.deb
Resolving launchpadlibrarian.net (launchpadlibrarian.net)... 91.189.89.228, 
91.189.89.229, 2001:67c:1560:8003::8007, ...
Connecting to launchpadlibrarian.net 
(launchpadlibrarian.net)|91.189.89.228|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 95292 (93K) [application/x-debian-package]
Saving to: ‘gzip_1.10-0ubuntu3.1_amd64.deb’

gzip_1.10-0ubuntu3.1_amd64.deb
100%[=>]
93.06K  --.-KB/sin 0.1s

2019-12-20 17:50:03 (715 KB/s) - ‘gzip_1.10-0ubuntu3.1_amd64.deb’ saved
[95292/95292]

root@ee-dwz:~# apt install ./gzip_1.10-0ubuntu3.1_amd64.deb 
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Note, selecting 'gzip' instead of './gzip_1.10-0ubuntu3.1_amd64.deb'
gzip is already the newest version (1.10-0ubuntu3.1).
The following package was automatically installed and is no longer required:
  libdumbnet1
Use 'apt autoremove' to remove it.
0 upgraded, 0 newly installed, 0 to remove and 8 not upgraded.
root@ee-dwz:~# 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;}}'
root@ee-dwz:~# echo $?
0
root@ee-dwz:~# FILE=/usr/bin/gzip; readelf -W --program-headers $FILE

Elf file type is DYN (Shared object file)
Entry point 0x4190
There are 14 program headers, starting at offset 64

Program Headers:
  Type   Offset   VirtAddr   PhysAddr   FileSiz  MemSiz 
  Flg Align
  PHDR   0x40 0x0040 0x0040 0x000310 
0x000310 R   0x8
  INTERP 0x000350 0x0350 0x0350 0x1c 
0x1c R   0x1
  [Requesting program interpreter: /lib64/ld-linux-x86-64.so.2]
  LOAD   0x00 0x 0x 0x0027a0 
0x0027a0 R   0x1000
  LOAD   0x003000 0x3000 0x3000 0x00ea05 
0x00ea05 R E 0x1000
  LOAD   0x012000 0x00012000 0x00012000 0x003e80 
0x003e80 R   0x1000
  LOAD   0x016690 0x00017690 0x00017690 0x000d70 
0x000d70 RW  0x1000
  LOAD   0x00 0x0001a000 0x0001a000 0x00 
0x0ca048 RW  0x1000
  DYNAMIC0x016b80 0x00017b80 0x00017b80 0x0001f0 
0x0001f0 RW  0x8
  NOTE   0x000370 0x0370 0x0370 0x20 
0x20 R   0x8
  NOTE   0x000390 0x0390 0x0390 0x44 
0x44 R   0x4
  GNU_PROPERTY   0x000370 0x0370 0x0370 0x20 
0x20 R   0x8
  GNU_EH_FRAME   0x01433c 0x0001433c 0x0001433c 0x000404 
0x000404 R   0x4
  GNU_STACK  0x00 0x 0x 0x00 
0x00 RW  0x10
  GNU_RELRO  0x016690 0x00017690 0x00017690 0x000970 
0x000970 R   0x1

 Section to Segment mapping:
  Segment Sections...
   00 
   01 .interp 
   02 .interp .note.gnu.property .note.gnu.build-id .note.ABI-tag .gnu.hash 
.dynsym .dynstr .gnu.version .gnu.version_r .rela.dyn .rela.plt 
   03 .init .plt .plt.got .plt.sec .text .fini 
   04 .rodata .eh_frame_hdr .eh_frame 
   05 .init_array .fini_array .data.rel.ro .dynamic .got .data 
   06 .bss 
   07 .dynamic 
   08 .note.gnu.property 
   09 .note.gnu.build-id .note.ABI-tag 
   10 .note.gnu.property 
   11 .eh_frame_hdr 
   12 
   13 .init_array .fini_array .data.rel.ro .dynamic .got 
root@ee-dwz:~# 


** Description changed:

- IMPORTANT: Binutils was accidentally built in -proposed instead of in a
- PPA. I'm rebuilding it in https://launchpad.net/~ci-train-ppa-
- service/+archive/ubuntu/3877 for the -security pocket.
- 
  [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 

[Touch-packages] [Bug 1857176] [NEW] [PLT V8200 Series, playback] Playback problem

[josh d]

Public bug reported:

Hi, what happened was - I changed my input device to this device and
when I did I noticed the output (to same device) became degraded. I was
able to fix by setting it from high fidelity, back to headset, and back
to high fidelity again. So, it seems setting the input device did some
sort of 'configuration reset' that was not shown in the UI.

Thanks! Wonderful OS :)

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
Uname: Linux 5.3.0-24-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  jdix   1978 F pulseaudio
 /dev/snd/controlC0:  jdix   1978 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Fri Dec 20 16:52:06 2019
InstallationDate: Installed on 2018-10-08 (438 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_Card: PLT V8200 Series
Symptom_Type: None of the above
Title: [PLT V8200 Series, playback] Playback problem
UpgradeStatus: Upgraded to eoan on 2019-10-31 (50 days ago)
dmi.bios.date: 06/04/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: L3.24
dmi.board.name: X470 Master SLI/ac
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrL3.24:bd06/04/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX470MasterSLI/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

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


** Tags: amd64 apport-bug eoan

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

Title:
  [PLT V8200 Series, playback] Playback problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Hi, what happened was - I changed my input device to this device and
  when I did I noticed the output (to same device) became degraded. I
  was able to fix by setting it from high fidelity, back to headset, and
  back to high fidelity again. So, it seems setting the input device did
  some sort of 'configuration reset' that was not shown in the UI.

  Thanks! Wonderful OS :)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jdix   1978 F pulseaudio
   /dev/snd/controlC0:  jdix   1978 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec 20 16:52:06 2019
  InstallationDate: Installed on 2018-10-08 (438 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: PLT V8200 Series
  Symptom_Type: None of the above
  Title: [PLT V8200 Series, playback] Playback problem
  UpgradeStatus: Upgraded to eoan on 2019-10-31 (50 days ago)
  dmi.bios.date: 06/04/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: L3.24
  dmi.board.name: X470 Master SLI/ac
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrL3.24:bd06/04/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX470MasterSLI/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Touch-packages] [Bug 1856703] Re: Return only PAM_IGNORE or error from pam_motd

[Launchpad Bug Tracker]

This bug was fixed in the package pam - 1.3.1-5ubuntu4

---
pam (1.3.1-5ubuntu4) focal; urgency=medium

  * Return only PAM_IGNORE or error from pam_motd (LP: #1856703)

 -- Balint Reczey   Tue, 17 Dec 2019 17:41:40 +0100

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

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

Title:
   Return only PAM_IGNORE or error from pam_motd

Status in pam package in Ubuntu:
  Fix Released
Status in pam source package in Eoan:
  New

Bug description:
  
  https://github.com/linux-pam/linux-pam/pull/157

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

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