[Touch-packages] [Bug 2065932] Re: Only adds the weak key for PPAs dual-signed with both weak and strong keys

[Anders Kaseorg]

There’s no misunderstanding.  The server’s behavior seems to have
changed since I reported this.

$ curl 
'https://ppa.launchpadcontent.net/git-core/ppa/ubuntu/dists/noble/InRelease' | 
gpgv
…
gpgv: Signature made Tue 30 Jul 2024 01:11:33 AM PDT
gpgv:using RSA key F911AB184317630C59970973E363C90F8F1B6217
gpgv: Good signature from "Launchpad PPA for Ubuntu Git Maintainers"
gpgv: Signature made Tue 30 Jul 2024 01:11:33 AM PDT
gpgv:using RSA key E1DD270288B4E6030699E45FA1715D88E1DF1F24
gpgv: Good signature from "Launchpad PPA for Ubuntu Git Maintainers"

Note that the two signatures are now in the other order.  Lacking any
input from the Launchpad team, I have no way to tell whether this was a
deliberate bugfix or just a random hash sorting fluctuation that could
regress at any time.

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

Title:
  Only adds the weak key for PPAs dual-signed with both weak and strong
  keys

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  After running ‘add-apt-repository ppa:git-core/ppa’ on Ubuntu 24.04,
  ‘apt update’ gives this warning:

  W: https://ppa.launchpadcontent.net/git-
  core/ppa/ubuntu/dists/noble/InRelease: Signature by key
  E1DD270288B4E6030699E45FA1715D88E1DF1F24 uses weak algorithm (rsa1024)

  But this PPA is dual-signed by two keys, only one of which is weak.
  add-apt-repository has chosen to install the rsa1024 key in
  sources.list.d.  It should choose the rsa4096 key instead.

  $ curl 
'https://ppa.launchpadcontent.net/git-core/ppa/ubuntu/dists/noble/InRelease' | 
gpgv
  …
  gpg: Signature made Thu 16 May 2024 05:22:18 AM PDT
  gpg:using RSA key F911AB184317630C59970973E363C90F8F1B6217
  gpg: Good signature from "Launchpad PPA for Ubuntu Git Maintainers" [unknown]
  gpg: WARNING: This key is not certified with a trusted signature!
  gpg:  There is no indication that the signature belongs to the owner.
  Primary key fingerprint: F911 AB18 4317 630C 5997  0973 E363 C90F 8F1B 6217
  gpg: Signature made Thu 16 May 2024 05:22:18 AM PDT
  gpg:using RSA key E1DD270288B4E6030699E45FA1715D88E1DF1F24
  gpg: Good signature from "Launchpad PPA for Ubuntu Git Maintainers" [unknown]
  gpg: WARNING: This key is not certified with a trusted signature!
  gpg:  There is no indication that the signature belongs to the owner.
  Primary key fingerprint: E1DD 2702 88B4 E603 0699  E45F A171 5D88 E1DF 1F24
  $ gpg --list-keys F911AB184317630C59970973E363C90F8F1B6217 
E1DD270288B4E6030699E45FA1715D88E1DF1F24
  pub   rsa1024 2009-01-22 [SC]
    E1DD270288B4E6030699E45FA1715D88E1DF1F24
  uid   [ unknown] Launchpad PPA for Ubuntu Git Maintainers

  pub   rsa4096 2024-04-24 [SC]
    F911AB184317630C59970973E363C90F8F1B6217
  uid   [ unknown] Launchpad PPA for Ubuntu Git Maintainers

  Context: https://discourse.ubuntu.com/t/new-requirements-for-apt-
  repository-signing-in-24-04/42854

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


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

[Touch-packages] [Bug 2059723] Re: Please delete libmagic1 1:5.45-2 from the archive (in favor of libmagic1t64 1:5.45-3)

[Anders Kaseorg]

Seems resolved.

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

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

Title:
  Please delete libmagic1 1:5.45-2 from the archive (in favor of
  libmagic1t64 1:5.45-3)

Status in file package in Ubuntu:
  Fix Released

Bug description:
  As part of the 64-bit time_t transition, libmagic1 was renamed to
  libmagic1t64 in https://bugs.debian.org/1063113.  However, libmagic1
  1:5.45-2 is still in the archive, despite being non-installable:

  
  # apt-get install libmagic1
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libmagic1 : Depends: libmagic-mgc (= 1:5.45-2) but 1:5.45-3 is to be 
installed
  E: Unable to correct problems, you have held broken packages.

  
  Please delete libmagic1 from the archive, so that libmagic1t64 1:5.45-3 can 
take over this role (it’s already marked Provides: libmagic1 (= 1:5.45-3)).

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


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

[Touch-packages] [Bug 2059723] Re: Please delete libmagic1 1:5.45-2 from the archive (in favor of libmagic1t64 1:5.45-3)

[Anders Kaseorg]

Same problem is back now that 1:5.45-3build1 is uploaded and 1:5.45-2
still isn’t deleted.

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

Title:
  Please delete libmagic1 1:5.45-2 from the archive (in favor of
  libmagic1t64 1:5.45-3)

Status in file package in Ubuntu:
  New

Bug description:
  As part of the 64-bit time_t transition, libmagic1 was renamed to
  libmagic1t64 in https://bugs.debian.org/1063113.  However, libmagic1
  1:5.45-2 is still in the archive, despite being non-installable:

  
  # apt-get install libmagic1
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libmagic1 : Depends: libmagic-mgc (= 1:5.45-2) but 1:5.45-3 is to be 
installed
  E: Unable to correct problems, you have held broken packages.

  
  Please delete libmagic1 from the archive, so that libmagic1t64 1:5.45-3 can 
take over this role (it’s already marked Provides: libmagic1 (= 1:5.45-3)).

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


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

[Touch-packages] [Bug 2059723] Re: Please delete libmagic1 1:5.45-2 from the archive (in favor of libmagic1t64 1:5.45-3)

[Anders Kaseorg]

It seems like 1:5.45-3 was deleted instead of 1:5.45-2? That resolves
the immediate issue, I guess, but it’s probably not the intended
resolution.

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

Title:
  Please delete libmagic1 1:5.45-2 from the archive (in favor of
  libmagic1t64 1:5.45-3)

Status in file package in Ubuntu:
  New

Bug description:
  As part of the 64-bit time_t transition, libmagic1 was renamed to
  libmagic1t64 in https://bugs.debian.org/1063113.  However, libmagic1
  1:5.45-2 is still in the archive, despite being non-installable:

  
  # apt-get install libmagic1
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libmagic1 : Depends: libmagic-mgc (= 1:5.45-2) but 1:5.45-3 is to be 
installed
  E: Unable to correct problems, you have held broken packages.

  
  Please delete libmagic1 from the archive, so that libmagic1t64 1:5.45-3 can 
take over this role (it’s already marked Provides: libmagic1 (= 1:5.45-3)).

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


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

[Touch-packages] [Bug 2059723] [NEW] Please delete libmagic1 1:5.45-2 from the archive (in favor of libmagic1t64 1:5.45-3)

[Anders Kaseorg]

Public bug reported:

As part of the 64-bit time_t transition, libmagic1 was renamed to
libmagic1t64 in https://bugs.debian.org/1063113.  However, libmagic1
1:5.45-2 is still in the archive, despite being non-installable:


# apt-get install libmagic1
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libmagic1 : Depends: libmagic-mgc (= 1:5.45-2) but 1:5.45-3 is to be installed
E: Unable to correct problems, you have held broken packages.


Please delete libmagic1 from the archive, so that libmagic1t64 1:5.45-3 can 
take over this role (it’s already marked Provides: libmagic1 (= 1:5.45-3)).

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

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

Title:
  Please delete libmagic1 1:5.45-2 from the archive (in favor of
  libmagic1t64 1:5.45-3)

Status in file package in Ubuntu:
  New

Bug description:
  As part of the 64-bit time_t transition, libmagic1 was renamed to
  libmagic1t64 in https://bugs.debian.org/1063113.  However, libmagic1
  1:5.45-2 is still in the archive, despite being non-installable:

  
  # apt-get install libmagic1
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libmagic1 : Depends: libmagic-mgc (= 1:5.45-2) but 1:5.45-3 is to be 
installed
  E: Unable to correct problems, you have held broken packages.

  
  Please delete libmagic1 from the archive, so that libmagic1t64 1:5.45-3 can 
take over this role (it’s already marked Provides: libmagic1 (= 1:5.45-3)).

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


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

[Touch-packages] [Bug 1960608] Re: python-pip >= 21.3.1+dfsg-3 fails pip3-root.sh autopkgtest with python3.10

[Anders Kaseorg]

This new sysconfig-debian-schemes.diff has broken virtual environments
(venv and virtualenv). Please take a look at the fix in
https://bugs.launchpad.net/ubuntu/+source/python3.10/+bug/1962791.

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

Title:
  python-pip >= 21.3.1+dfsg-3 fails pip3-root.sh autopkgtest with
  python3.10

Status in automake-1.16 package in Ubuntu:
  Fix Released
Status in dh-python package in Ubuntu:
  Fix Released
Status in python-pip package in Ubuntu:
  Fix Released
Status in python3.10 package in Ubuntu:
  Fix Released

Bug description:
  pip3-root.sh expects world package to be installed in
  /usr/local/lib/python3.*/dist-packages whereas it is actually
  installed into /usr/lib/python3.10/site-packages/.

  It even fails to uninstall the package right after installing it:

  ubuntu@autopkgtest:~$ sudo python3 -m pip install world
  Collecting world
Using cached world-4.1.1-py3-none-any.whl
  Collecting atpublic
Using cached atpublic-3.0.1-py3-none-any.whl (4.8 kB)
  Installing collected packages: atpublic, world
  Successfully installed atpublic-3.0.1 world-4.1.1
  WARNING: Running pip as the 'root' user can result in broken permissions and 
conflicting behaviour with the system package manager. It is recommended to use 
a virtual environment instead: https://pip.pypa.io/warnings/venv
  ubuntu@autopkgtest:~$ sudo python3 -m pip uninstall world
  WARNING: Skipping world as it is not installed.
  WARNING: Running pip as the 'root' user can result in broken permissions and 
conflicting behaviour with the system package manager. It is recommended to use 
a virtual environment instead: https://pip.pypa.io/warnings/venv

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


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

[Touch-packages] [Bug 1953301] Re: Segfault on AArch64 caused by OpenSSL affecting numerous packages

[Anders Kaseorg]

*** This bug is a duplicate of bug 1951279 ***
https://bugs.launchpad.net/bugs/1951279

** This bug has been marked a duplicate of bug 1951279
   OpenSSL 1.1.1f raise a segmentation faults on Arm64 builds

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

Title:
  Segfault on AArch64 caused by OpenSSL affecting numerous packages

Status in openssl package in Ubuntu:
  Incomplete

Bug description:
  OpenSSL causes crashes when reaching to some URLs on AArch64 platform,
  affecting Ubuntu, but not Fedora for instance.

  Initially reported in https://mediasoup.discourse.group/t/mediasoup-
  worker-default-make-failed/3647/12, more details and reproductions in
  https://github.com/mesonbuild/meson/issues/9690

  Affects curl, wget, python and probably everything else.

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


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

[Touch-packages] [Bug 47958] Re: ssh-agent clobbers LD_LIBRARY_PATH and other environment variables

[Anders Kaseorg]

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

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

Title:
  ssh-agent clobbers LD_LIBRARY_PATH and other environment variables

Status in openssh package in Ubuntu:
  Confirmed
Status in openssh package in Debian:
  New

Bug description:
  Since /usr/bin/ssh-agent is setgid ssh, it unsets LD_LIBRARY_PATH.
  This made it impossible to set this variable in my dotfiles
  (.gnomerc).

  My solution was to write a wrapper script that prefixes the command with 
/usr/bin/env VAR=val ... for each variable that gets unset:


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


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

[Touch-packages] [Bug 1782577] Re: docker: impossible to create image with python3 because tzdata

[Anders Kaseorg]

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

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

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

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

Title:
  docker: impossible to create image with python3 because tzdata

Status in cloud-images:
  New
Status in debconf package in Ubuntu:
  New
Status in debconf package in Debian:
  Unknown

Bug description:
  In my application I have to use both "supervisor" and some ML stuff,
  so I need to include python-3, numpy and pandas

  FROM ubuntu:latest
  RUN apt-get update
  RUN apt-get install -y supervisor python3 python3-pip python3-pymongo 
python3-numpy python3-pandas

  This appends with the current ubuntu:latest

  sha256:30e04ddada6eb09c12330c7df72cad1573916c7100168c34076808169ff6d805

  When I try to make a built of this, I seems that python3 depends on
  tzdata (and many other things), but then it stops waiting for a user
  input, and I unable to send an input by hand or other way

  Setting up libldap-common (2.4.45+dfsg-1ubuntu1) ...
  Setting up libreadline7:amd64 (7.0-3) ...
  Setting up tzdata (2018d-1) ...
  debconf: unable to initialize frontend: Dialog
  debconf: (TERM is not set, so the dialog frontend is not usable.)
  debconf: falling back to frontend: Readline
  Configuring tzdata
  --

  Please select the geographic area in which you live. Subsequent configuration
  questions will narrow this down by presenting a list of cities, representing
  the time zones in which they are located.

1. Africa  4. Australia  7. Atlantic  10. Pacific  13. Etc
2. America 5. Arctic 8. Europe11. SystemV
3. Antarctica  6. Asia   9. Indian12. US
  Geographic area: 

  So I am unable to create my docker image!!

  This is some kind of regression, 2 weeks ago it worked

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1782577/+subscriptions

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

[Anders Kaseorg]

The situation with apache2 is what I documented in
https://bugs.launchpad.net/ubuntu/+source/pcre3/+bug/1792544/comments/9:

“But since we’re apparently gathering information here: although Apache
2.4.x does not support PCRE2, Apache trunk does support PCRE2 as of
r1773454. (As you can see, this support was added by creating separate
conditionally compiled code paths for PCRE and PCRE2.)

https://github.com/apache/httpd/commit/b1a3338e011a17ad190fb7f66cf5ca9acf353570”

trunk is the 2.5.x branch, not 2.4.x.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/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:
  Incomplete
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:
  Triaged
Status in nginx package in Ubuntu:
  Incomplete
Status in nmap package in Ubuntu:
  Incomplete
Status in pcre3 package in Ubuntu:
  Confirmed
Status in php-defaults package in Ubuntu:
  Triaged
Status in php7.2 package in Ubuntu:
  Won't Fix
Status in postfix package in Ubuntu:
  Incomplete
Status in python-pyscss package in Ubuntu:
  Incomplete
Status in quagga package in Ubuntu:
  Invalid
Status in rasqal package in Ubuntu:
  Incomplete
Status in slang2 package in Ubuntu:
  Incomplete
Status in sssd package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Triaged
Status in 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:
  Fix Released

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 1792745] Re: NetworkManager crashed with SIGSEGV in _int_malloc()

[Anders Kaseorg]

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

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

Title:
  NetworkManager crashed with SIGSEGV in _int_malloc()

Status in NetworkManager:
  Unknown
Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  I’m seeing NetworkManager crash several times on startup and on resume
  from suspend. Apport doesn’t catch those for some reason, but this
  happened when I tried to reproduce by manually running NetworkManager
  --debug.

  (Different crash from bug 1792743?  Also apport-retrace didn’t seem to
  like that one.)

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: network-manager 1.12.2-0ubuntu4
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  Date: Sat Sep 15 14:04:50 2018
  EcryptfsInUse: Yes
  ExecutablePath: /usr/sbin/NetworkManager
  IfupdownConfig: # ifupdown has been replaced by netplan(5) on this system.  
Do not edit.
  InstallationDate: Installed on 2016-02-19 (939 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160218)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
  ProcCmdline: NetworkManager --debug
  SegvAnalysis:
   Segfault happened at: 0x7f79966ea378 <_int_malloc+3352>: cmp
%rcx,0x18(%rdx)
   PC (0x7f79966ea378) ok
   source "%rcx" ok
   destination "0x18(%rdx)" (0x0018) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: network-manager
  StacktraceTop:
   _int_malloc (av=av@entry=0x7f799683ac40 , 
bytes=bytes@entry=4096) at malloc.c:4014
   __libc_calloc (n=, elem_size=) at malloc.c:3420
   g_malloc0 () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   nlmsg_alloc_size (len=4096) at src/platform/nm-netlink.c:314
   _nl80211_alloc_msg (id=28, ifindex=2, phy=0, cmd=cmd@entry=32, 
flags=flags@entry=768) at src/platform/wifi/wifi-utils-nl80211.c:88
  Title: NetworkManager crashed with SIGSEGV in _int_malloc()
  UpgradeStatus: Upgraded to cosmic on 2018-08-17 (29 days ago)
  UserGroups:
   
  nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 
8: Error: NetworkManager is not running.
  nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 
8: Error: NetworkManager is not running.
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'gen'] failed with exit code 
8: Error: NetworkManager is not running.

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

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

[Touch-packages] [Bug 1792745] Re: NetworkManager crashed with SIGSEGV in _int_malloc()

[Anders Kaseorg]

1.12.4 is in cosmic-proposed now with the upstream fix.

** Changed in: network-manager (Ubuntu)
   Status: In Progress => Fix Committed

** Changed in: network-manager (Ubuntu)
 Assignee: Anders Kaseorg (andersk) => (unassigned)

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

Title:
  NetworkManager crashed with SIGSEGV in _int_malloc()

Status in NetworkManager:
  Unknown
Status in network-manager package in Ubuntu:
  Fix Committed

Bug description:
  I’m seeing NetworkManager crash several times on startup and on resume
  from suspend. Apport doesn’t catch those for some reason, but this
  happened when I tried to reproduce by manually running NetworkManager
  --debug.

  (Different crash from bug 1792743?  Also apport-retrace didn’t seem to
  like that one.)

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: network-manager 1.12.2-0ubuntu4
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  Date: Sat Sep 15 14:04:50 2018
  EcryptfsInUse: Yes
  ExecutablePath: /usr/sbin/NetworkManager
  IfupdownConfig: # ifupdown has been replaced by netplan(5) on this system.  
Do not edit.
  InstallationDate: Installed on 2016-02-19 (939 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160218)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
  ProcCmdline: NetworkManager --debug
  SegvAnalysis:
   Segfault happened at: 0x7f79966ea378 <_int_malloc+3352>: cmp
%rcx,0x18(%rdx)
   PC (0x7f79966ea378) ok
   source "%rcx" ok
   destination "0x18(%rdx)" (0x0018) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: network-manager
  StacktraceTop:
   _int_malloc (av=av@entry=0x7f799683ac40 , 
bytes=bytes@entry=4096) at malloc.c:4014
   __libc_calloc (n=, elem_size=) at malloc.c:3420
   g_malloc0 () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   nlmsg_alloc_size (len=4096) at src/platform/nm-netlink.c:314
   _nl80211_alloc_msg (id=28, ifindex=2, phy=0, cmd=cmd@entry=32, 
flags=flags@entry=768) at src/platform/wifi/wifi-utils-nl80211.c:88
  Title: NetworkManager crashed with SIGSEGV in _int_malloc()
  UpgradeStatus: Upgraded to cosmic on 2018-08-17 (29 days ago)
  UserGroups:
   
  nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 
8: Error: NetworkManager is not running.
  nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 
8: Error: NetworkManager is not running.
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'gen'] failed with exit code 
8: Error: NetworkManager is not running.

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

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

[Touch-packages] [Bug 1792745] Re: NetworkManager crashed with SIGSEGV in _int_malloc()

[Anders Kaseorg]

(Still waiting on sponsorship, but apparently “In Progress” is the right
status for that.)

** Changed in: network-manager (Ubuntu)
   Status: Confirmed => In Progress

** Changed in: network-manager (Ubuntu)
 Assignee: (unassigned) => Anders Kaseorg (andersk)

** Tags added: patch patch-accepted-upstream

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

Title:
  NetworkManager crashed with SIGSEGV in _int_malloc()

Status in NetworkManager:
  Unknown
Status in network-manager package in Ubuntu:
  In Progress

Bug description:
  I’m seeing NetworkManager crash several times on startup and on resume
  from suspend. Apport doesn’t catch those for some reason, but this
  happened when I tried to reproduce by manually running NetworkManager
  --debug.

  (Different crash from bug 1792743?  Also apport-retrace didn’t seem to
  like that one.)

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: network-manager 1.12.2-0ubuntu4
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  Date: Sat Sep 15 14:04:50 2018
  EcryptfsInUse: Yes
  ExecutablePath: /usr/sbin/NetworkManager
  IfupdownConfig: # ifupdown has been replaced by netplan(5) on this system.  
Do not edit.
  InstallationDate: Installed on 2016-02-19 (939 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160218)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
  ProcCmdline: NetworkManager --debug
  SegvAnalysis:
   Segfault happened at: 0x7f79966ea378 <_int_malloc+3352>: cmp
%rcx,0x18(%rdx)
   PC (0x7f79966ea378) ok
   source "%rcx" ok
   destination "0x18(%rdx)" (0x0018) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: network-manager
  StacktraceTop:
   _int_malloc (av=av@entry=0x7f799683ac40 , 
bytes=bytes@entry=4096) at malloc.c:4014
   __libc_calloc (n=, elem_size=) at malloc.c:3420
   g_malloc0 () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   nlmsg_alloc_size (len=4096) at src/platform/nm-netlink.c:314
   _nl80211_alloc_msg (id=28, ifindex=2, phy=0, cmd=cmd@entry=32, 
flags=flags@entry=768) at src/platform/wifi/wifi-utils-nl80211.c:88
  Title: NetworkManager crashed with SIGSEGV in _int_malloc()
  UpgradeStatus: Upgraded to cosmic on 2018-08-17 (29 days ago)
  UserGroups:
   
  nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 
8: Error: NetworkManager is not running.
  nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 
8: Error: NetworkManager is not running.
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'gen'] failed with exit code 
8: Error: NetworkManager is not running.

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

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

[Touch-packages] [Bug 1792745] Re: NetworkManager crashed with SIGSEGV in _int_malloc()

[Anders Kaseorg]

** Patch added: "rebased on 1.12.2-0ubuntu5"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1792745/+attachment/5192582/+files/network-manager_1.12.2-0ubuntu5_lp1792745.debdiff

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

Title:
  NetworkManager crashed with SIGSEGV in _int_malloc()

Status in NetworkManager:
  Unknown
Status in network-manager package in Ubuntu:
  New

Bug description:
  I’m seeing NetworkManager crash several times on startup and on resume
  from suspend. Apport doesn’t catch those for some reason, but this
  happened when I tried to reproduce by manually running NetworkManager
  --debug.

  (Different crash from bug 1792743?  Also apport-retrace didn’t seem to
  like that one.)

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: network-manager 1.12.2-0ubuntu4
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  Date: Sat Sep 15 14:04:50 2018
  EcryptfsInUse: Yes
  ExecutablePath: /usr/sbin/NetworkManager
  IfupdownConfig: # ifupdown has been replaced by netplan(5) on this system.  
Do not edit.
  InstallationDate: Installed on 2016-02-19 (939 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160218)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
  ProcCmdline: NetworkManager --debug
  SegvAnalysis:
   Segfault happened at: 0x7f79966ea378 <_int_malloc+3352>: cmp
%rcx,0x18(%rdx)
   PC (0x7f79966ea378) ok
   source "%rcx" ok
   destination "0x18(%rdx)" (0x0018) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: network-manager
  StacktraceTop:
   _int_malloc (av=av@entry=0x7f799683ac40 , 
bytes=bytes@entry=4096) at malloc.c:4014
   __libc_calloc (n=, elem_size=) at malloc.c:3420
   g_malloc0 () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   nlmsg_alloc_size (len=4096) at src/platform/nm-netlink.c:314
   _nl80211_alloc_msg (id=28, ifindex=2, phy=0, cmd=cmd@entry=32, 
flags=flags@entry=768) at src/platform/wifi/wifi-utils-nl80211.c:88
  Title: NetworkManager crashed with SIGSEGV in _int_malloc()
  UpgradeStatus: Upgraded to cosmic on 2018-08-17 (29 days ago)
  UserGroups:
   
  nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 
8: Error: NetworkManager is not running.
  nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 
8: Error: NetworkManager is not running.
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'gen'] failed with exit code 
8: Error: NetworkManager is not running.

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

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

[Touch-packages] [Bug 1792745] Re: NetworkManager crashed with SIGSEGV in _int_malloc()

[Anders Kaseorg]

** Patch added: "debdiff adding upstream patch"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1792745/+attachment/5191867/+files/network-manager_1.12.2-0ubuntu4_lp1792745.debdiff

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

Title:
  NetworkManager crashed with SIGSEGV in _int_malloc()

Status in NetworkManager:
  Unknown
Status in network-manager package in Ubuntu:
  New

Bug description:
  I’m seeing NetworkManager crash several times on startup and on resume
  from suspend. Apport doesn’t catch those for some reason, but this
  happened when I tried to reproduce by manually running NetworkManager
  --debug.

  (Different crash from bug 1792743?  Also apport-retrace didn’t seem to
  like that one.)

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: network-manager 1.12.2-0ubuntu4
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  Date: Sat Sep 15 14:04:50 2018
  EcryptfsInUse: Yes
  ExecutablePath: /usr/sbin/NetworkManager
  IfupdownConfig: # ifupdown has been replaced by netplan(5) on this system.  
Do not edit.
  InstallationDate: Installed on 2016-02-19 (939 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160218)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
  ProcCmdline: NetworkManager --debug
  SegvAnalysis:
   Segfault happened at: 0x7f79966ea378 <_int_malloc+3352>: cmp
%rcx,0x18(%rdx)
   PC (0x7f79966ea378) ok
   source "%rcx" ok
   destination "0x18(%rdx)" (0x0018) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: network-manager
  StacktraceTop:
   _int_malloc (av=av@entry=0x7f799683ac40 , 
bytes=bytes@entry=4096) at malloc.c:4014
   __libc_calloc (n=, elem_size=) at malloc.c:3420
   g_malloc0 () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   nlmsg_alloc_size (len=4096) at src/platform/nm-netlink.c:314
   _nl80211_alloc_msg (id=28, ifindex=2, phy=0, cmd=cmd@entry=32, 
flags=flags@entry=768) at src/platform/wifi/wifi-utils-nl80211.c:88
  Title: NetworkManager crashed with SIGSEGV in _int_malloc()
  UpgradeStatus: Upgraded to cosmic on 2018-08-17 (29 days ago)
  UserGroups:
   
  nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 
8: Error: NetworkManager is not running.
  nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 
8: Error: NetworkManager is not running.
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'gen'] failed with exit code 
8: Error: NetworkManager is not running.

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

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

[Touch-packages] [Bug 1792745] Re: NetworkManager crashed with SIGSEGV in _int_malloc()

[Anders Kaseorg]

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

Title:
  NetworkManager crashed with SIGSEGV in _int_malloc()

Status in NetworkManager:
  Unknown
Status in network-manager package in Ubuntu:
  New

Bug description:
  I’m seeing NetworkManager crash several times on startup and on resume
  from suspend. Apport doesn’t catch those for some reason, but this
  happened when I tried to reproduce by manually running NetworkManager
  --debug.

  (Different crash from bug 1792743?  Also apport-retrace didn’t seem to
  like that one.)

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: network-manager 1.12.2-0ubuntu4
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  Date: Sat Sep 15 14:04:50 2018
  EcryptfsInUse: Yes
  ExecutablePath: /usr/sbin/NetworkManager
  IfupdownConfig: # ifupdown has been replaced by netplan(5) on this system.  
Do not edit.
  InstallationDate: Installed on 2016-02-19 (939 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160218)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
  ProcCmdline: NetworkManager --debug
  SegvAnalysis:
   Segfault happened at: 0x7f79966ea378 <_int_malloc+3352>: cmp
%rcx,0x18(%rdx)
   PC (0x7f79966ea378) ok
   source "%rcx" ok
   destination "0x18(%rdx)" (0x0018) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: network-manager
  StacktraceTop:
   _int_malloc (av=av@entry=0x7f799683ac40 , 
bytes=bytes@entry=4096) at malloc.c:4014
   __libc_calloc (n=, elem_size=) at malloc.c:3420
   g_malloc0 () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   nlmsg_alloc_size (len=4096) at src/platform/nm-netlink.c:314
   _nl80211_alloc_msg (id=28, ifindex=2, phy=0, cmd=cmd@entry=32, 
flags=flags@entry=768) at src/platform/wifi/wifi-utils-nl80211.c:88
  Title: NetworkManager crashed with SIGSEGV in _int_malloc()
  UpgradeStatus: Upgraded to cosmic on 2018-08-17 (29 days ago)
  UserGroups:
   
  nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 
8: Error: NetworkManager is not running.
  nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 
8: Error: NetworkManager is not running.
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'gen'] failed with exit code 
8: Error: NetworkManager is not running.

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

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

[Touch-packages] [Bug 1792745] Re: NetworkManager crashed with SIGSEGV in _int_malloc()

[Anders Kaseorg]

** Bug watch added: GNOME Bug Tracker #797136
   https://bugzilla.gnome.org/show_bug.cgi?id=797136

** Also affects: network-manager via
   https://bugzilla.gnome.org/show_bug.cgi?id=797136
   Importance: Unknown
   Status: Unknown

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

Title:
  NetworkManager crashed with SIGSEGV in _int_malloc()

Status in NetworkManager:
  Unknown
Status in network-manager package in Ubuntu:
  New

Bug description:
  I’m seeing NetworkManager crash several times on startup and on resume
  from suspend. Apport doesn’t catch those for some reason, but this
  happened when I tried to reproduce by manually running NetworkManager
  --debug.

  (Different crash from bug 1792743?  Also apport-retrace didn’t seem to
  like that one.)

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: network-manager 1.12.2-0ubuntu4
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  Date: Sat Sep 15 14:04:50 2018
  EcryptfsInUse: Yes
  ExecutablePath: /usr/sbin/NetworkManager
  IfupdownConfig: # ifupdown has been replaced by netplan(5) on this system.  
Do not edit.
  InstallationDate: Installed on 2016-02-19 (939 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160218)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
  ProcCmdline: NetworkManager --debug
  SegvAnalysis:
   Segfault happened at: 0x7f79966ea378 <_int_malloc+3352>: cmp
%rcx,0x18(%rdx)
   PC (0x7f79966ea378) ok
   source "%rcx" ok
   destination "0x18(%rdx)" (0x0018) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: network-manager
  StacktraceTop:
   _int_malloc (av=av@entry=0x7f799683ac40 , 
bytes=bytes@entry=4096) at malloc.c:4014
   __libc_calloc (n=, elem_size=) at malloc.c:3420
   g_malloc0 () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   nlmsg_alloc_size (len=4096) at src/platform/nm-netlink.c:314
   _nl80211_alloc_msg (id=28, ifindex=2, phy=0, cmd=cmd@entry=32, 
flags=flags@entry=768) at src/platform/wifi/wifi-utils-nl80211.c:88
  Title: NetworkManager crashed with SIGSEGV in _int_malloc()
  UpgradeStatus: Upgraded to cosmic on 2018-08-17 (29 days ago)
  UserGroups:
   
  nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 
8: Error: NetworkManager is not running.
  nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 
8: Error: NetworkManager is not running.
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'gen'] failed with exit code 
8: Error: NetworkManager is not running.

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

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

[Anders Kaseorg]

Likewise, nginx does not support PCRE2:
https://trac.nginx.org/nginx/ticket/720

** Bug watch added: trac.nginx.org/nginx/ #720
   http://trac.nginx.org/nginx/ticket/720

** Changed in: nginx (Ubuntu)
   Status: Triaged => Incomplete

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

Title:
  demotion of pcre3 in favor of pcre2

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

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

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

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

  --

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

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

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

[Touch-packages] [Bug 1792544] Re: demotion of pcre3 in favor of pcre2

[Anders Kaseorg]

Note to those filing upstream bugs: probably don’t call the old library
“pcre3” since that’s not a thing outside Debian/Ubuntu.

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

Title:
  demotion of pcre3 in favor of pcre2

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

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

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

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

  --

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

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

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

[Touch-packages] [Bug 1792544] Re: demotion of pcre3 in favor of pcre2

[Anders Kaseorg]

I think that completes the analysis of the current state of things.
Although it seems infeasible to demote PCRE at this time, there’s no
reason that should block the promotion of PCRE2, especially seeing as a
bundled copy of PCRE2 is already in main (18.04 and 18.10) via
libqt5core5a.

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

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

Title:
  demotion of pcre3 in favor of pcre2

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

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

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

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

  --

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

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

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

[Touch-packages] [Bug 1792544] Re: demotion of pcre3 in favor of pcre2

[Anders Kaseorg]

• Quagga: no PCRE2 support
• Rasqal: no PCRE2 support
• S-Lang: no PCRE2 support

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

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

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

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

Title:
  demotion of pcre3 in favor of pcre2

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

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

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

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

  --

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

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

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

[Touch-packages] [Bug 1792544] Re: demotion of pcre3 in favor of pcre2

[Anders Kaseorg]

• pam_mount: no PCRE2 support
• nmap: no PCRE2 support
• postfix: no PCRE2 support, 
http://postfix.1071664.n5.nabble.com/Plans-for-using-PCRE-v2-in-Postfix-td83200.html
• pyScss: no PCRE2 support

** Changed in: libpam-mount (Ubuntu)
   Status: New => Incomplete

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

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

** Changed in: python-pyscss (Ubuntu)
   Status: New => Incomplete

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

Title:
  demotion of pcre3 in favor of pcre2

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

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

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

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

  --

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

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

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

[Touch-packages] [Bug 1792544] Re: demotion of pcre3 in favor of pcre2

[Anders Kaseorg]

• Aide: no PCRE2 support
• Exim: no PCRE2 support, upstream bug: 
https://bugs.exim.org/show_bug.cgi?id=1878
• FreeRADIUS: no PCRE2 support, mentioned in passing: 
https://github.com/FreeRADIUS/freeradius-server/issues/1865
• GLib: no PCRE2 support
• grep: no PCRE2 support

** Bug watch added: bugs.exim.org/ #1878
   http://bugs.exim.org/show_bug.cgi?id=1878

** Bug watch added: github.com/FreeRADIUS/freeradius-server/issues #1865
   https://github.com/FreeRADIUS/freeradius-server/issues/1865

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

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

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

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

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

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

Title:
  demotion of pcre3 in favor of pcre2

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

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

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

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

  --

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

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

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

[Touch-packages] [Bug 1792544] Re: demotion of pcre3 in favor of pcre2

[Anders Kaseorg]

Copying from
https://bugs.launchpad.net/ubuntu/+source/pcre2/+bug/163/comments/20,
HAProxy and SELinux upstream support PCRE2.

https://git.haproxy.org/?p=haproxy.git;a=commitdiff;h=f2592b29f13907ddf2bba42d00bc41cb8ee5b69b
https://github.com/SELinuxProject/selinux/commit/50f0910cf05bdc1d10710c7c3fb748a178473387

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

Title:
  demotion of pcre3 in favor of pcre2

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

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

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

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

  --

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

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

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

[Touch-packages] [Bug 1792544] Re: demotion of pcre3 in favor of pcre2

[Anders Kaseorg]

Andreas: No, it’s not a bug.  PCRE2 is a new project that’s not intended
to be compatible with the older PCRE (i.e. what Debian misnamed
“pcre3”).  The API is completely different and this is expected.  See
bug 163 for context, and specifically the PCRE2 release announcement
linked in the bug description:

https://lists.exim.org/lurker/message/20150105.162835.0666407a.en.html

That’s why getting rid of PCRE “in favor of” PCRE2 is a pointless way to
frame the issue.  PCRE2 neither replaces nor conflicts with PCRE, as was
pointed out many times in bug 163.

But since we’re apparently gathering information here: although Apache
2.4.x does not support PCRE2, Apache trunk does support PCRE2 as of
r1773454.  (As you can see, this support was added by creating separate
conditionally compiled code paths for PCRE and PCRE2.)

https://github.com/apache/httpd/commit/b1a3338e011a17ad190fb7f66cf5ca9acf353570

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

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

Title:
  demotion of pcre3 in favor of pcre2

Status in aide package in Ubuntu:
  New
Status in apache2 package in Ubuntu:
  New
Status in apr-util package in Ubuntu:
  New
Status in clamav package in Ubuntu:
  Triaged
Status in exim4 package in Ubuntu:
  New
Status in freeradius package in Ubuntu:
  New
Status in git package in Ubuntu:
  Triaged
Status in glib2.0 package in Ubuntu:
  New
Status in grep package in Ubuntu:
  New
Status in haproxy package in Ubuntu:
  New
Status in libpam-mount package in Ubuntu:
  New
Status in libselinux package in Ubuntu:
  New
Status in nginx package in Ubuntu:
  Triaged
Status in nmap package in Ubuntu:
  New
Status in pcre3 package in Ubuntu:
  Confirmed
Status in php7.2 package in Ubuntu:
  Triaged
Status in postfix package in Ubuntu:
  New
Status in python-pyscss package in Ubuntu:
  New
Status in quagga package in Ubuntu:
  New
Status in rasqal package in Ubuntu:
  New
Status in slang2 package in Ubuntu:
  New
Status in sssd package in Ubuntu:
  Triaged
Status in wget package in Ubuntu:
  Triaged
Status in zsh package in Ubuntu:
  Triaged

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

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

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

  --

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

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

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

[Touch-packages] [Bug 1792544] Re: demotion of pcre3 in favor of pcre2

[Anders Kaseorg]

apr-util has a false Build-Depends on libpcre3-dev; it should simply be
dropped.  A corresponding Depends was already dropped in
https://bugs.debian.org/757140.

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

Title:
  demotion of pcre3 in favor of pcre2

Status in aide package in Ubuntu:
  New
Status in apache2 package in Ubuntu:
  New
Status in apr-util package in Ubuntu:
  New
Status in clamav package in Ubuntu:
  Triaged
Status in exim4 package in Ubuntu:
  New
Status in freeradius package in Ubuntu:
  New
Status in git package in Ubuntu:
  Triaged
Status in glib2.0 package in Ubuntu:
  New
Status in grep package in Ubuntu:
  New
Status in haproxy package in Ubuntu:
  New
Status in libpam-mount package in Ubuntu:
  New
Status in libselinux package in Ubuntu:
  New
Status in nginx package in Ubuntu:
  Triaged
Status in nmap package in Ubuntu:
  New
Status in pcre3 package in Ubuntu:
  Confirmed
Status in php7.2 package in Ubuntu:
  Triaged
Status in postfix package in Ubuntu:
  New
Status in python-pyscss package in Ubuntu:
  New
Status in quagga package in Ubuntu:
  New
Status in rasqal package in Ubuntu:
  New
Status in slang2 package in Ubuntu:
  New
Status in sssd package in Ubuntu:
  Triaged
Status in wget package in Ubuntu:
  Triaged
Status in zsh package in Ubuntu:
  Triaged

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

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

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

  --

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

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

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

[Touch-packages] [Bug 1792745] Re: NetworkManager crashed with SIGSEGV in _int_malloc()

[Anders Kaseorg]

It seems suspicious that cb_data->concheck.curl_ehandle is cleaned up
here despite the comment a few lines above warning that it’s unsafe to
do so.

https://github.com/NetworkManager/NetworkManager/blob/1.12.2/src/nm-
connectivity.c#L190-L213

/* Contrary to what cURL manual claim it is *not* safe to remove
 * the easy handle "at any moment"; specifically not from the
 * write function. Thus here we just dissociate the cb_data from
 * the easy handle and the easy handle will be cleaned up when 
the
 * message goes to CURLMSG_DONE in 
_con_curl_check_connectivity(). */
…
curl_multi_remove_handle (priv->concheck.curl_mhandle, 
cb_data->concheck.curl_ehandle);
curl_easy_cleanup (cb_data->concheck.curl_ehandle);

This cleanup call was added in
https://github.com/NetworkManager/NetworkManager/pull/70.  The comment
was moved by that PR but was present before.

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

Title:
  NetworkManager crashed with SIGSEGV in _int_malloc()

Status in network-manager package in Ubuntu:
  New

Bug description:
  I’m seeing NetworkManager crash several times on startup and on resume
  from suspend. Apport doesn’t catch those for some reason, but this
  happened when I tried to reproduce by manually running NetworkManager
  --debug.

  (Different crash from bug 1792743?  Also apport-retrace didn’t seem to
  like that one.)

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: network-manager 1.12.2-0ubuntu4
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  Date: Sat Sep 15 14:04:50 2018
  EcryptfsInUse: Yes
  ExecutablePath: /usr/sbin/NetworkManager
  IfupdownConfig: # ifupdown has been replaced by netplan(5) on this system.  
Do not edit.
  InstallationDate: Installed on 2016-02-19 (939 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160218)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
  ProcCmdline: NetworkManager --debug
  SegvAnalysis:
   Segfault happened at: 0x7f79966ea378 <_int_malloc+3352>: cmp
%rcx,0x18(%rdx)
   PC (0x7f79966ea378) ok
   source "%rcx" ok
   destination "0x18(%rdx)" (0x0018) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: network-manager
  StacktraceTop:
   _int_malloc (av=av@entry=0x7f799683ac40 , 
bytes=bytes@entry=4096) at malloc.c:4014
   __libc_calloc (n=, elem_size=) at malloc.c:3420
   g_malloc0 () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   nlmsg_alloc_size (len=4096) at src/platform/nm-netlink.c:314
   _nl80211_alloc_msg (id=28, ifindex=2, phy=0, cmd=cmd@entry=32, 
flags=flags@entry=768) at src/platform/wifi/wifi-utils-nl80211.c:88
  Title: NetworkManager crashed with SIGSEGV in _int_malloc()
  UpgradeStatus: Upgraded to cosmic on 2018-08-17 (29 days ago)
  UserGroups:
   
  nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 
8: Error: NetworkManager is not running.
  nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 
8: Error: NetworkManager is not running.
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'gen'] failed with exit code 
8: Error: NetworkManager is not running.

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

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

[Touch-packages] [Bug 1792745] Re: NetworkManager crashed with SIGSEGV in _int_malloc()

[Anders Kaseorg]

Here’s a valgrlind log showing many invalid writes to freed addresses in
cb_data_free → curl_multi_remove_handle and nm_connectivity_check_start
→ curl_multi_add_handle, which could explain the heap corruption.

** Attachment added: "nm.19802.log"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1792745/+attachment/5189363/+files/nm.19802.log

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

Title:
  NetworkManager crashed with SIGSEGV in _int_malloc()

Status in network-manager package in Ubuntu:
  New

Bug description:
  I’m seeing NetworkManager crash several times on startup and on resume
  from suspend. Apport doesn’t catch those for some reason, but this
  happened when I tried to reproduce by manually running NetworkManager
  --debug.

  (Different crash from bug 1792743?  Also apport-retrace didn’t seem to
  like that one.)

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: network-manager 1.12.2-0ubuntu4
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  Date: Sat Sep 15 14:04:50 2018
  EcryptfsInUse: Yes
  ExecutablePath: /usr/sbin/NetworkManager
  IfupdownConfig: # ifupdown has been replaced by netplan(5) on this system.  
Do not edit.
  InstallationDate: Installed on 2016-02-19 (939 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160218)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
  ProcCmdline: NetworkManager --debug
  SegvAnalysis:
   Segfault happened at: 0x7f79966ea378 <_int_malloc+3352>: cmp
%rcx,0x18(%rdx)
   PC (0x7f79966ea378) ok
   source "%rcx" ok
   destination "0x18(%rdx)" (0x0018) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: network-manager
  StacktraceTop:
   _int_malloc (av=av@entry=0x7f799683ac40 , 
bytes=bytes@entry=4096) at malloc.c:4014
   __libc_calloc (n=, elem_size=) at malloc.c:3420
   g_malloc0 () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   nlmsg_alloc_size (len=4096) at src/platform/nm-netlink.c:314
   _nl80211_alloc_msg (id=28, ifindex=2, phy=0, cmd=cmd@entry=32, 
flags=flags@entry=768) at src/platform/wifi/wifi-utils-nl80211.c:88
  Title: NetworkManager crashed with SIGSEGV in _int_malloc()
  UpgradeStatus: Upgraded to cosmic on 2018-08-17 (29 days ago)
  UserGroups:
   
  nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 
8: Error: NetworkManager is not running.
  nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 
8: Error: NetworkManager is not running.
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'gen'] failed with exit code 
8: Error: NetworkManager is not running.

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

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

[Touch-packages] [Bug 1792745] Re: NetworkManager crashed with SIGSEGV in _int_malloc()

[Anders Kaseorg]

** Information type changed from Private to Public

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

Title:
  NetworkManager crashed with SIGSEGV in _int_malloc()

Status in network-manager package in Ubuntu:
  New

Bug description:
  I’m seeing NetworkManager crash several times on startup and on resume
  from suspend. Apport doesn’t catch those for some reason, but this
  happened when I tried to reproduce by manually running NetworkManager
  --debug.

  (Different crash from bug 1792743?  Also apport-retrace didn’t seem to
  like that one.)

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: network-manager 1.12.2-0ubuntu4
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  Date: Sat Sep 15 14:04:50 2018
  EcryptfsInUse: Yes
  ExecutablePath: /usr/sbin/NetworkManager
  IfupdownConfig: # ifupdown has been replaced by netplan(5) on this system.  
Do not edit.
  InstallationDate: Installed on 2016-02-19 (939 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160218)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
  ProcCmdline: NetworkManager --debug
  SegvAnalysis:
   Segfault happened at: 0x7f79966ea378 <_int_malloc+3352>: cmp
%rcx,0x18(%rdx)
   PC (0x7f79966ea378) ok
   source "%rcx" ok
   destination "0x18(%rdx)" (0x0018) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: network-manager
  StacktraceTop:
   _int_malloc (av=av@entry=0x7f799683ac40 , 
bytes=bytes@entry=4096) at malloc.c:4014
   __libc_calloc (n=, elem_size=) at malloc.c:3420
   g_malloc0 () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   nlmsg_alloc_size (len=4096) at src/platform/nm-netlink.c:314
   _nl80211_alloc_msg (id=28, ifindex=2, phy=0, cmd=cmd@entry=32, 
flags=flags@entry=768) at src/platform/wifi/wifi-utils-nl80211.c:88
  Title: NetworkManager crashed with SIGSEGV in _int_malloc()
  UpgradeStatus: Upgraded to cosmic on 2018-08-17 (29 days ago)
  UserGroups:
   
  nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 
8: Error: NetworkManager is not running.
  nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 
8: Error: NetworkManager is not running.
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'gen'] failed with exit code 
8: Error: NetworkManager is not running.

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

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

[Touch-packages] [Bug 1780680] Re: Older version in bionic than in xenial

[Anders Kaseorg]

Older versions in bionic than in xenial, as of now:

fuse-umfuse-ext2 0.4-1.1ubuntu0.1 < 0.4-1.1ubuntu0.16.04.1
linux-meta-azure 4.15.0.1021.21 < 4.15.0.1021.27
linux-meta-gcp 4.15.0.1017.19 < 4.15.0.1017.29


** Summary changed:

- Older version in artful than in xenial
+ Older version in bionic than in xenial

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

** Changed in: wireless-regdb (Ubuntu)
   Status: New => Fix Released

** Changed in: python-pyvmomi (Ubuntu)
   Status: New => Invalid

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

** Also affects: linux-meta-azure (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: linux-meta-gcp (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Older version in bionic than in xenial

Status in fuse-umfuse-ext2 package in Ubuntu:
  New
Status in libclc package in Ubuntu:
  Won't Fix
Status in libdrm package in Ubuntu:
  Won't Fix
Status in linux-meta-azure package in Ubuntu:
  New
Status in linux-meta-gcp package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  Won't Fix
Status in patch package in Ubuntu:
  Invalid
Status in python-pyvmomi package in Ubuntu:
  Invalid
Status in snapcraft package in Ubuntu:
  Fix Released
Status in wireless-regdb package in Ubuntu:
  Fix Released

Bug description:
  These packages have an older version in artful than in xenial.

  fuse-umfuse-ext2 0.4-1.1ubuntu0.1 < 0.4-1.1ubuntu0.16.04.1
  libclc 0.2.0+git20170330-3 < 0.2.0+git20180312-1~16.04.1
  libdrm 2.4.83-1 < 2.4.91-2~16.04.1
  mesa 17.2.8-0ubuntu0~17.10.1 < 18.0.5-0ubuntu0~16.04.1
  patch 2.7.5-1ubuntu0.2 < 2.7.5-1ubuntu0.16.04.1
  python-pyvmomi 5.5.0-2014.1.1-3 < 6.5.0.2017.5-0ubuntu1~16.04.1
  snapcraft 2.42+17.10 < 2.42.1
  wireless-regdb 2016.06.10-0ubuntu1 < 2018.05.09-0ubuntu1~16.04.1

  Some of these are older in bionic than in xenial too.

  Shouldn’t there be an automated check for this?  (See also: bug
  1780679, bug 1780681.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fuse-umfuse-ext2/+bug/1780680/+subscriptions

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

[Touch-packages] [Bug 1780680] Re: Older version in artful than in xenial

[Anders Kaseorg]

** Description changed:

  These packages have an older version in artful than in xenial.
  
  fuse-umfuse-ext2 0.4-1.1ubuntu0.1 < 0.4-1.1ubuntu0.16.04.1
  libclc 0.2.0+git20170330-3 < 0.2.0+git20180312-1~16.04.1
  libdrm 2.4.83-1 < 2.4.91-2~16.04.1
  mesa 17.2.8-0ubuntu0~17.10.1 < 18.0.5-0ubuntu0~16.04.1
  patch 2.7.5-1ubuntu0.2 < 2.7.5-1ubuntu0.16.04.1
  python-pyvmomi 5.5.0-2014.1.1-3 < 6.5.0.2017.5-0ubuntu1~16.04.1
  snapcraft 2.42+17.10 < 2.42.1
  wireless-regdb 2016.06.10-0ubuntu1 < 2018.05.09-0ubuntu1~16.04.1
  
  Some of these are older in bionic than in xenial too.
  
- Shouldn’t there be an automated check for this?
+ Shouldn’t there be an automated check for this?  (See also: bug 1780679,
+ bug 1780681.)

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

Title:
  Older version in artful than in xenial

Status in fuse-umfuse-ext2 package in Ubuntu:
  New
Status in libclc package in Ubuntu:
  New
Status in libdrm package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New
Status in patch package in Ubuntu:
  New
Status in python-pyvmomi package in Ubuntu:
  New
Status in snapcraft package in Ubuntu:
  New
Status in wireless-regdb package in Ubuntu:
  New

Bug description:
  These packages have an older version in artful than in xenial.

  fuse-umfuse-ext2 0.4-1.1ubuntu0.1 < 0.4-1.1ubuntu0.16.04.1
  libclc 0.2.0+git20170330-3 < 0.2.0+git20180312-1~16.04.1
  libdrm 2.4.83-1 < 2.4.91-2~16.04.1
  mesa 17.2.8-0ubuntu0~17.10.1 < 18.0.5-0ubuntu0~16.04.1
  patch 2.7.5-1ubuntu0.2 < 2.7.5-1ubuntu0.16.04.1
  python-pyvmomi 5.5.0-2014.1.1-3 < 6.5.0.2017.5-0ubuntu1~16.04.1
  snapcraft 2.42+17.10 < 2.42.1
  wireless-regdb 2016.06.10-0ubuntu1 < 2018.05.09-0ubuntu1~16.04.1

  Some of these are older in bionic than in xenial too.

  Shouldn’t there be an automated check for this?  (See also: bug
  1780679, bug 1780681.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fuse-umfuse-ext2/+bug/1780680/+subscriptions

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

[Touch-packages] [Bug 1772607] Re: Mesa 18.0.5 stable release

[Anders Kaseorg]

Until this is uploaded to bionic, the version in bionic is older than in
xenial (bug 1780680), which is going to interfere with upgrades.

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

Title:
  Mesa 18.0.5 stable release

Status in libglvnd package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in libglvnd source package in Bionic:
  Fix Committed
Status in mesa source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  Ubuntu 18.04 shipped with mesa 18.0.0~rc5, and deserves to get the last point 
release of the series.

  [Test Case]
  Check on intel/radeon hw that things still work fine.

  [Regression potential]
  Mesa stable releases are tested by vendor CI systems.

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

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

[Touch-packages] [Bug 1780680] [NEW] Older version in artful than in xenial

[Anders Kaseorg]

Public bug reported:

These packages have an older version in artful than in xenial.

fuse-umfuse-ext2 0.4-1.1ubuntu0.1 < 0.4-1.1ubuntu0.16.04.1
libclc 0.2.0+git20170330-3 < 0.2.0+git20180312-1~16.04.1
libdrm 2.4.83-1 < 2.4.91-2~16.04.1
mesa 17.2.8-0ubuntu0~17.10.1 < 18.0.5-0ubuntu0~16.04.1
patch 2.7.5-1ubuntu0.2 < 2.7.5-1ubuntu0.16.04.1
python-pyvmomi 5.5.0-2014.1.1-3 < 6.5.0.2017.5-0ubuntu1~16.04.1
snapcraft 2.42+17.10 < 2.42.1
wireless-regdb 2016.06.10-0ubuntu1 < 2018.05.09-0ubuntu1~16.04.1

Some of these are older in bionic than in xenial too.

Shouldn’t there be an automated check for this?

** Affects: fuse-umfuse-ext2 (Ubuntu)
 Importance: Undecided
 Status: New

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

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

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

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

** Affects: python-pyvmomi (Ubuntu)
 Importance: Undecided
 Status: New

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

** Affects: wireless-regdb (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: artful bionic

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

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

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

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

** Also affects: python-pyvmomi (Ubuntu)
   Importance: Undecided
   Status: New

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

** Also affects: wireless-regdb (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Older version in artful than in xenial

Status in fuse-umfuse-ext2 package in Ubuntu:
  New
Status in libclc package in Ubuntu:
  New
Status in libdrm package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New
Status in patch package in Ubuntu:
  New
Status in python-pyvmomi package in Ubuntu:
  New
Status in snapcraft package in Ubuntu:
  New
Status in wireless-regdb package in Ubuntu:
  New

Bug description:
  These packages have an older version in artful than in xenial.

  fuse-umfuse-ext2 0.4-1.1ubuntu0.1 < 0.4-1.1ubuntu0.16.04.1
  libclc 0.2.0+git20170330-3 < 0.2.0+git20180312-1~16.04.1
  libdrm 2.4.83-1 < 2.4.91-2~16.04.1
  mesa 17.2.8-0ubuntu0~17.10.1 < 18.0.5-0ubuntu0~16.04.1
  patch 2.7.5-1ubuntu0.2 < 2.7.5-1ubuntu0.16.04.1
  python-pyvmomi 5.5.0-2014.1.1-3 < 6.5.0.2017.5-0ubuntu1~16.04.1
  snapcraft 2.42+17.10 < 2.42.1
  wireless-regdb 2016.06.10-0ubuntu1 < 2018.05.09-0ubuntu1~16.04.1

  Some of these are older in bionic than in xenial too.

  Shouldn’t there be an automated check for this?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fuse-umfuse-ext2/+bug/1780680/+subscriptions

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

[Touch-packages] [Bug 520546] Re: Alt-f2 switches to virtual terminal 2

[Anders Kaseorg]

** Changed in: console-setup (Ubuntu)
   Status: Invalid => Confirmed

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

Title:
  Alt-f2 switches to virtual terminal 2

Status in console-cyrillic package in Ubuntu:
  Invalid
Status in console-setup package in Ubuntu:
  Confirmed

Bug description:
  I'm running Ubuntu Lucid development branch.

  Pressing alt-f2 switches the screen to the second virtual terminal.
  Alt-f3 does the same to the third and so on. I expected alt-f2 to open
  the run dialog.

  I'm pretty sure that my keyboard is not malfunctioning as I can use
  all my applications normally. (Pressing O and Ctrl-O do not have the
  same effect.)

  I'm not sure which package I should file this bug against. I'll
  happily do an apport-collect once I know.

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

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

[Touch-packages] [Bug 520546] Re: Alt-f2 switches to virtual terminal 2

[Anders Kaseorg]

Just because DISPLAY isn’t set for the current process doesn’t mean X or
Wayland aren’t running.  For example:

pkexec env DEBIAN_FRONTEND=noninteractive dpkg-reconfigure keyboard-
configuration

still triggers this bug (because pkexec does not propagate environment
variables), and you can imagine any number of other ways this might
happen, like packagekit or unattended-upgrades.

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

Title:
  Alt-f2 switches to virtual terminal 2

Status in console-cyrillic package in Ubuntu:
  Invalid
Status in console-setup package in Ubuntu:
  Invalid

Bug description:
  I'm running Ubuntu Lucid development branch.

  Pressing alt-f2 switches the screen to the second virtual terminal.
  Alt-f3 does the same to the third and so on. I expected alt-f2 to open
  the run dialog.

  I'm pretty sure that my keyboard is not malfunctioning as I can use
  all my applications normally. (Pressing O and Ctrl-O do not have the
  same effect.)

  I'm not sure which package I should file this bug against. I'll
  happily do an apport-collect once I know.

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

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

[Touch-packages] [Bug 1624320] Re: systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing entries

[Anders Kaseorg]

On my bionic system, I had to manually remove resolvconf on account of
bug 1713457.  I think it was not being autoremoved because other
packages like isc-dhcp-client, pppconfig, vpnc-scripts have Suggests:
resolvconf.

So I don’t think I’m seeing this particular issue.  However, the lack of
resolvconf cooperation means that openconnect run from the command line
fights with systemd-resolved over /etc/resolv.conf.  I’m sure that all
kinds of nonsense bugs like that are waiting to be rediscovered.

For the record, I’m still really quite angry at systemd-resolved for a
number of issues that upstream seems to have no interest in addressing.
Its own DNSSEC validation is disabled in Ubuntu because it’s broken (bug
1628778), yet it also breaks DNSSEC validation in applications
downstream of it (https://github.com/systemd/systemd/issues/4621).  It
breaks ‘dig +trace’ (https://github.com/systemd/systemd/issues/5897).
It doesn’t work with resolvconf in a sane way.  The many previous issues
I’ve had with it took way too long to be addressed.  And it does nothing
useful that dnsmasq didn’t do!  (I even had NetworkManager’s dnsmasq
configured to to DNSSEC validation and it worked just fine.)  I’m not
one of those anti-systemd people who hates change for the sake of hating
change.  But systemd-resolved is an actual flaming garbage pile that
needs to be vitrified and launched into the sun.

** Bug watch added: github.com/systemd/systemd/issues #5897
   https://github.com/systemd/systemd/issues/5897

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

Title:
  systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing
  entries

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  systemd-resolved, or more precisely the hook script
  /lib/systemd/system/systemd-resolved.service.d/resolvconf.conf, causes
  resolvconf to add 127.0.0.53 to the set of nameservers in
  /etc/resolv.conf alongside the other nameservers.  That makes no sense
  because systemd-resolved sets up 127.0.0.53 as a proxy for those other
  nameservers.  The effect is similar to bug 1624071 but for
  applications doing their own DNS lookups.  It breaks any DNSSEC
  validation that systemd-resolved tries to do; applications will
  failover to the other nameservers, bypassing validation failures.  And
  it makes failing queries take twice as long.

  /etc/resolv.conf should have only 127.0.0.53 when systemd-resolved is
  active.

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

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

[Touch-packages] [Bug 1449001] Re: systemd-resolved: please do not use Google public DNS by default

[Anders Kaseorg]

Verified using ubuntu-17.04-desktop-amd64.iso.

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

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

Title:
  systemd-resolved: please do not use Google public DNS by default

Status in systemd:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Zesty:
  Fix Committed
Status in systemd source package in Artful:
  Fix Released
Status in systemd package in Debian:
  Fix Released

Bug description:
  [Impact]
  systemd-resolved will fall back to Google public DNS (8.8.8.8, etc.) in the 
absence of other configured DNS servers.

  systemd-resolved is not enabled by default in Ubuntu 15.04, but it is
  installed by default and will behave in this way if enabled by the
  user.

  $ cat /etc/systemd/resolved.conf
  (...)
  # Entries in this file show the compile time defaults.
  (...)
  #FallbackDNS=8.8.8.8 8.8.4.4 2001:4860:4860:: 2001:4860:4860::8844

  This raises privacy concerns since in the event of accidental
  misconfiguration DNS queries will be sent unencrypted across the
  internet, and potentially also security concerns given systemd-
  resolved does not perform DNSSEC validation and is not particularly
  well hardened against malicious responses e.g. from a MITM
  (http://www.openwall.com/lists/oss-security/2014/11/12/5).

  I believe that it would be better to fail safe if no DNS server is
  configured -- i.e. have DNS lookups fail; it's better that the user is
  aware of their misconfiguration, rather than silently sending their
  queries to Google.  The user can intentionally opt to use Google
  public DNS if they wish.

  [Testcase]
  Steps to reproduce:
  1. Remove existing DNS configuration (from /etc/network/interfaces, 
/etc/resolv.conf, /etc/resolvconf/resolv.conf.d/*)
  2. Reboot, or otherwise clear relevant state
  3. sudo service systemd-resolved start
  4. Note that Google's servers are listed in /run/systemd/resolve/resolv.conf
  5. If systemd-resolved is enabled in /etc/nsswitch.conf (it isn't by 
default), observe that DNS lookups probably still work, and queries are being 
sent to one of Google's servers

  Possible workaround/bugfix: ship a resolved.conf which clears the
  FallbackDNS parameter.

  [Solution]
  In ubuntu, we disable fallback DNS at build time, via build system 
configuration flags.

  This issue has been discussed in the Debian BTS
  (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761658).  My
  interpretation of the Debian package maintainer's position is that a
  user concerned with the privacy implications shouldn't let systemd get
  into a state where it uses the fallback DNS servers (quoting Marco
  d'Itri: "Short summary: have a resolv.conf file or use DHCP").  I
  would argue that it's safest not to have fallback DNS servers
  configured at all by default.

  [Regression Potential]
  Missconfigured networks, that do not have a DNS server would previously 
magically work due to having Google DNS preconfigured regardless. With this 
change, such network configurations will fail to work, and one will have to 
properly fix network config to point at the right/existing name server.

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

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

[Touch-packages] [Bug 1713457] [NEW] DNS search domain not removed from resolv.conf on disconnect

[Anders Kaseorg]

Public bug reported:

When I connect to a wireless network that sets a DNS search domain name
via DHCP, the line 'search ' is added to /etc/resolv.conf as
expected.  But if I then disconnect and connect to a different network,
it is not removed from resolv.conf.  If the second network also sets a
search domain name, that one gets appended to resolv.conf along with the
first one, and so on.  Depending on the network, this can cause DNS
leaks, name resolution failures, or other misbehavior.

To be sure this wasn't some kind of user configuration issue, I
reproduced this on the artful daily live image (artful-desktop-
amd64.iso, 2017-08-27), from which I'm writing this report.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: network-manager 1.8.2-1ubuntu3
ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
Uname: Linux 4.12.0-11-generic x86_64
ApportVersion: 2.20.6-0ubuntu7
Architecture: amd64
CasperVersion: 1.384
CurrentDesktop: ubuntu:GNOME
Date: Mon Aug 28 10:34:22 2017
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
IpRoute:
 default via 172.20.20.1 dev wlp3s0 proto static metric 600
 169.254.0.0/16 dev wlp3s0 scope link metric 1000
 172.20.20.0/24 dev wlp3s0 proto kernel scope link src 172.20.20.20 metric 600
LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170827)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-dev:
 DEVICE TYPE  STATEDBUS-PATH  
CONNECTION   CON-UUID  CON-PATH
 wlp3s0 wifi  connected/org/freedesktop/NetworkManager/Devices/3  
xfinitywifi  39ffbbfc-1c1e-41c9-b3eb-c513065c3ea6  
/org/freedesktop/NetworkManager/ActiveConnection/2
 enp0s31f6  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  
--   ----
 lo loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  
--   ----
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.8.2connected  started  full  enabled enabled  
enabled  enabled  enabled

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug artful regression-release

** Description changed:

  When I connect to a wireless network that sets a DNS search domain name
- via DHCP, the line 'search domain' is added to /etc/resolv.conf as
+ via DHCP, the line 'search ' is added to /etc/resolv.conf as
  expected.  But if I then disconnect and connect to a different network,
  it is not removed from resolv.conf.  If the second network also sets a
  search domain name, that one gets appended to resolv.conf along with the
  first one, and so on.  Depending on the network, this can cause name
  resolution failures or other misbehavior.
  
  To be sure this wasn't some kind of user configuration issue, I
  reproduced this on the artful daily live image (artful-desktop-
  amd64.iso, 2017-08-27), from which I'm writing this report.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.2-1ubuntu3
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.384
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 28 10:34:22 2017
  IfupdownConfig:
-  # interfaces(5) file used by ifup(8) and ifdown(8)
-  auto lo
-  iface lo inet loopback
+  # interfaces(5) file used by ifup(8) and ifdown(8)
+  auto lo
+  iface lo inet loopback
  IpRoute:
-  default via 172.20.20.1 dev wlp3s0 proto static metric 600 
-  169.254.0.0/16 dev wlp3s0 scope link metric 1000 
-  172.20.20.0/24 dev wlp3s0 proto kernel scope link src 172.20.20.20 metric 600
+  default via 172.20.20.1 dev wlp3s0 proto static metric 600
+  169.254.0.0/16 dev wlp3s0 scope link metric 1000
+  172.20.20.0/24 dev wlp3s0 proto kernel scope link src 172.20.20.20 metric 600
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170827)
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
-  DEVICE TYPE  STATEDBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
-  wlp3s0 wifi  connected/org/freedesktop/NetworkManager/Devices/3  
xfinitywifi  39ffbbfc-1c1e-41c9-b3eb-c513065c3ea6  
/org/freedesktop/NetworkManager/ActiveConn

[Touch-packages] [Bug 1449001] Re: systemd-resolved: please do not use Google public DNS by default

[Anders Kaseorg]

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

** Changed in: systemd
   Importance: Unknown => Undecided

** Changed in: systemd
   Status: Fix Released => New

** Changed in: systemd
 Remote watch: Debian Bug tracker #761658 => None

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

Title:
  systemd-resolved: please do not use Google public DNS by default

Status in systemd:
  New
Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Xenial:
  New
Status in systemd source package in Yakkety:
  New
Status in systemd source package in Zesty:
  New
Status in systemd source package in Artful:
  Fix Committed
Status in systemd package in Debian:
  Unknown

Bug description:
  systemd-resolved will fall back to Google public DNS (8.8.8.8, etc.)
  in the absence of other configured DNS servers.

  systemd-resolved is not enabled by default in Ubuntu 15.04, but it is
  installed by default and will behave in this way if enabled by the
  user.

  $ cat /etc/systemd/resolved.conf 
  (...)
  # Entries in this file show the compile time defaults.
  (...)
  #FallbackDNS=8.8.8.8 8.8.4.4 2001:4860:4860:: 2001:4860:4860::8844

  This raises privacy concerns since in the event of accidental
  misconfiguration DNS queries will be sent unencrypted across the
  internet, and potentially also security concerns given systemd-
  resolved does not perform DNSSEC validation and is not particularly
  well hardened against malicious responses e.g. from a MITM
  (http://www.openwall.com/lists/oss-security/2014/11/12/5).

  I believe that it would be better to fail safe if no DNS server is
  configured -- i.e. have DNS lookups fail; it's better that the user is
  aware of their misconfiguration, rather than silently sending their
  queries to Google.  The user can intentionally opt to use Google
  public DNS if they wish.


  Steps to reproduce:
  1. Remove existing DNS configuration (from /etc/network/interfaces, 
/etc/resolv.conf, /etc/resolvconf/resolv.conf.d/*)
  2. Reboot, or otherwise clear relevant state
  3. sudo service systemd-resolved start
  4. Note that Google's servers are listed in /run/systemd/resolve/resolv.conf
  5. If systemd-resolved is enabled in /etc/nsswitch.conf (it isn't by 
default), observe that DNS lookups probably still work, and queries are being 
sent to one of Google's servers

  
  Possible workaround/bugfix: ship a resolved.conf which clears the FallbackDNS 
parameter.

  
  This issue has been discussed in the Debian BTS 
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761658).  My interpretation 
of the Debian package maintainer's position is that a user concerned with the 
privacy implications shouldn't let systemd get into a state where it uses the 
fallback DNS servers (quoting Marco d'Itri: "Short summary: have a resolv.conf 
file or use DHCP").  I would argue that it's safest not to have fallback DNS 
servers configured at all by default.

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

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

[Touch-packages] [Bug 1537635] Re: Reduce zlib compression level for massive performance increase

[Anders Kaseorg]

Ping?  It’s still really frustrating to have the entire system go
unresponsive for a minute just because gnome-shell crashed and apport
won’t let it restart until it’s finished compressing the core dump.

If you’re not willing to go all the way to zlib level 1, can we at least
proceed with going down to 5 like you suggested?

Alternatively, python3-brotli entered Ubuntu shortly after my original
report.  brotli level 2 compresses faster than zlib level 1 with smaller
output than zlib level 9, while brotli level 1 is as almost as fast as
lz4 with output size like zlib level 5!

I don’t have the crash dump I used for the tests above, so here are some
tests on a somewhat smaller one.

zlib.compressobj(level=1) time=7.1 size=41822029
zlib.compressobj(level=2) time=7.1 size=40718379
zlib.compressobj(level=3) time=7.4 size=39638807
zlib.compressobj(level=4) time=13.1 size=31197301
zlib.compressobj(level=5) time=13.9 size=30423373
zlib.compressobj(level=6) time=15.1 size=29763741
zlib.compressobj(level=7) time=16.3 size=29526183
zlib.compressobj(level=8) time=25.6 size=29191955
zlib.compressobj(level=9) time=39.2 size=29067237

bz2.BZ2Compressor(compresslevel=1) time=25.0 size=25198553
bz2.BZ2Compressor(compresslevel=9) time=30.6 size=23280287

lz4.compress time=0.9 size=50649857
lz4.compressHC time=5.4 size=40462669

brotli.Compressor(quality=1) time=1.2 size=30559841
brotli.Compressor(quality=2) time=3.8 size=26162317
brotli.Compressor(quality=3) time=6.2 size=26256343
brotli.Compressor(quality=4) time=8.7 size=24982273
brotli.Compressor(quality=5) time=29.2 size=21744749
brotli.Compressor(quality=6) time=45.5 size=21502521
brotli.Compressor(quality=7) time=81.7 size=21355153
brotli.Compressor(quality=8) time=145.9 size=21249997

If a crash could be recorded in a second instead of a minute with almost
no size difference, I’d call that a win.

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

Title:
  Reduce zlib compression level for massive performance increase

Status in Apport:
  New
Status in apport package in Ubuntu:
  Confirmed

Bug description:
  When apport takes a core dump of a large application, it uses 100% CPU
  for a _long_ time (often 30 seconds or more) to compress the core
  dump. The system is virtually unusable during this time, especially if
  the application was the window manager and won’t be restarted until
  the core dump is complete.

  This is a longstanding known problem; it motivated the switch from
  bzip2 to zlib level 9 back in apport 0.24. That made it much better,
  but it’s still quite bad. So why not switch from zlib level 9 to zlib
  level 1?

  I tested this on a core dump of gnome-shell, and while it increased
  the size of the .crash file by 24% (68.5 MB to 85.0 MB), it decreased
  the needed CPU time by a FACTOR OF EIGHT (58.6 seconds to 7.3
  seconds). This tradeoff seems more than worthwhile for this use case.

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

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

[Touch-packages] [Bug 1449001] Re: systemd-resolved: please do not use Google public DNS by default

[Anders Kaseorg]

In fact, having recently disabled FallbackDNS for myself, I find that I
get no DNS at all maybe a quarter of the time I reboot my system.  This
suggests that systemd-resolved might be silently relying on the 8.8.8.8
fallback much more often than even I suggested above.

Can we try disabling FallbackDNS for this development cycle?  (Then,
once it becomes clear exactly how broken the DNS situation in Ubuntu has
become, can we please get rid of this systemd-resolved nonsense for
good?)

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

Title:
  systemd-resolved: please do not use Google public DNS by default

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Triaged

Bug description:
  systemd-resolved will fall back to Google public DNS (8.8.8.8, etc.)
  in the absence of other configured DNS servers.

  systemd-resolved is not enabled by default in Ubuntu 15.04, but it is
  installed by default and will behave in this way if enabled by the
  user.

  $ cat /etc/systemd/resolved.conf 
  (...)
  # Entries in this file show the compile time defaults.
  (...)
  #FallbackDNS=8.8.8.8 8.8.4.4 2001:4860:4860:: 2001:4860:4860::8844

  This raises privacy concerns since in the event of accidental
  misconfiguration DNS queries will be sent unencrypted across the
  internet, and potentially also security concerns given systemd-
  resolved does not perform DNSSEC validation and is not particularly
  well hardened against malicious responses e.g. from a MITM
  (http://www.openwall.com/lists/oss-security/2014/11/12/5).

  I believe that it would be better to fail safe if no DNS server is
  configured -- i.e. have DNS lookups fail; it's better that the user is
  aware of their misconfiguration, rather than silently sending their
  queries to Google.  The user can intentionally opt to use Google
  public DNS if they wish.


  Steps to reproduce:
  1. Remove existing DNS configuration (from /etc/network/interfaces, 
/etc/resolv.conf, /etc/resolvconf/resolv.conf.d/*)
  2. Reboot, or otherwise clear relevant state
  3. sudo service systemd-resolved start
  4. Note that Google's servers are listed in /run/systemd/resolve/resolv.conf
  5. If systemd-resolved is enabled in /etc/nsswitch.conf (it isn't by 
default), observe that DNS lookups probably still work, and queries are being 
sent to one of Google's servers

  
  Possible workaround/bugfix: ship a resolved.conf which clears the FallbackDNS 
parameter.

  
  This issue has been discussed in the Debian BTS 
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761658).  My interpretation 
of the Debian package maintainer's position is that a user concerned with the 
privacy implications shouldn't let systemd get into a state where it uses the 
fallback DNS servers (quoting Marco d'Itri: "Short summary: have a resolv.conf 
file or use DHCP").  I would argue that it's safest not to have fallback DNS 
servers configured at all by default.

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

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

[Touch-packages] [Bug 1685045] Re: stop using libnss_resolve.so for name resolution

[Anders Kaseorg]

Dimitri: It is not merely difficult, but in fact fundamentally
impossible, to make everyone use nss_resolve for DNS resolution.  Many
programs cannot use nsswitch for DNS at all.  This includes anything
that needs to lookup record types other than A and  (e.g. SRV, TXT,
MX, SSHFP, AFSDB), anything that needs an asynchronous API, anything
running on a non-primary architecture (e.g. nothing automatically pulls
in libnss-resolve:i386 on amd64), and anything that doesn’t use libc.

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

Title:
  stop using libnss_resolve.so for name resolution

Status in systemd package in Ubuntu:
  Triaged

Bug description:
  Once we have systemd-resolved's stub DNS resolver on a solid footing
  everywhere (LP: #1682499; LP: #1647031), we should stop using
  libnss_resolve.so for name resolution and *only* use the DNS stub
  resolver via libnss_dns.so.

  The reason is that libnss_resolve.so is non-standard, depends on more
  moving parts (dbus+added NSS module), and consistently masks bugs in
  the stub DNS resolver or its configuration that are only discovered
  when someone tries to use software that does not use the NSS
  configuration of the host (including, but not limited to, chroots;
  containers; software written in languages that don't use libc).

  Since systemd-resolved *must* continue to provide a robust stub DNS
  resolver for the foreseeable future, having the dbus service in use
  /as well/ is unwelcome complexity that causes bugs to manifest far
  from the point of introduction.

  Since the systemd-resolved service is currently only enabled if the
  libnss-resolve package is installed, this enablement logic would need
  to be migrated into the base systemd package.

  I believe we should consider making this change even in SRU due to the
  pernicious effects of the current behavior.  However, that will
  require some thought to come up with a reasonable SRU test case with
  low risk of regression.

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

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

[Touch-packages] [Bug 1647031] Re: systemd-resolved’s 127.0.0.53 server does not follow CNAME records

[Anders Kaseorg]

Martin, was the DNSSEC=allow-downgrade default not switched off for the
17.04 stable release like you said it would?

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

Title:
  systemd-resolved’s 127.0.0.53 server does not follow CNAME records

Status in Nextcloud:
  Unknown
Status in systemd:
  New
Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in network-manager source package in Yakkety:
  Invalid
Status in systemd source package in Yakkety:
  Fix Committed

Bug description:
  [SRU Justification]
  Ubuntu 16.10 server uses systemd-resolved by default, configured both as a 
DNS stub resolver on 127.0.0.53 and as an NSS module via libnss-resolved 
talking to the dbus service.  The DNS stub resolver has a bug that causes it to 
fail to resolve CNAME records.  This went unnoticed before release because by 
default the NSS module is used.  But a chroot or container on the system that 
does not include libnss-resolved and is configured to use the stub resolver 
will experience DNS failures.

  [Test case]
  1. On a yakkety server system, create a xenial chroot with mk-sbuild (or 
equivalent).
  2. Make sure that the host system has /etc/resolv.conf pointed at 127.0.0.53.
  2. Enter the chroot with 'sudo schroot -c xenial-amd64' or such.
  3. Install the iputils-ping package.
  4. ping www.freedesktop.org
  5. Confirm that the hostname does not resolve.
  6. Install the systemd package from yakkety-proposed onto the host system.
  7. ping www.freedesktop.org
  8. Confirm that the hostname does now resolve.

  [Regression potential]
  With a 247-line patch to a key service, there is some risk of regression.  
Regression risk is mitigated because this patch is already present in zesty and 
upstream, where no regressions have been reported, and because it only touches 
the DNS stub resolver which is not the code path used by default on host 
systems.

  
  $ systemd-resolve www.freedesktop.org
  www.freedesktop.org: 131.252.210.176
   2610:10:20:722:a800:ff:feda:470f
   (annarchy.freedesktop.org)

  -- Information acquired via protocol DNS in 673.6ms.
  -- Data is authenticated: no
  $ ping www.freedesktop.org
  ping: www.freedesktop.org: Name or service not known
  $ cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.

  nameserver 127.0.0.53
  $ dig +no{cmd,comments,stats} www.freedesktop.org @127.0.0.53
  ;www.freedesktop.org. IN  A
  www.freedesktop.org.  7146IN  CNAME   annarchy.freedesktop.org.
  $ dig +no{cmd,comments,stats} www.freedesktop.org @8.8.8.8
  ;www.freedesktop.org. IN  A
  www.freedesktop.org.  14399   IN  CNAME   annarchy.freedesktop.org.
  annarchy.freedesktop.org. 14399   IN  A   131.252.210.176

  I trust it needn’t be explained why this makes the internet almost
  completely useless in zesty.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nextcloud-snap/+bug/1647031/+subscriptions

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

[Touch-packages] [Bug 1676115] Re: systemd-resolved spams the system log with useless “Processing query...” messages

[Anders Kaseorg]

Ah, zesty still has 232-19 but this is presumably fixed in zesty-
proposed’s 232-21ubuntu1.

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

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

Title:
  systemd-resolved spams the system log with useless “Processing
  query...” messages

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  Fix Committed

Bug description:
  If you are running ‘journalctl -f’ to try to debug some other problem,
  you are constantly interrupted by zillions of these messages from
  systemd-resolved:

  Mar 26 00:53:27 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:27 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:30 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:30 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:30 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query...

  This was fixed upstream in v233 by downgrading this message from log_info to 
log_debug:
  https://github.com/systemd/systemd/pull/5233

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

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

[Touch-packages] [Bug 1676115] [NEW] systemd-resolved spams the system log with useless “Processing query...” messages

[Anders Kaseorg]

Public bug reported:

If you are running ‘journalctl -f’ to try to debug some other problem,
you are constantly interrupted by zillions of these messages from
systemd-resolved:

Mar 26 00:53:27 change-mode systemd-resolved[1391]: Processing query...
Mar 26 00:53:27 change-mode systemd-resolved[1391]: Processing query...
Mar 26 00:53:30 change-mode systemd-resolved[1391]: Processing query...
Mar 26 00:53:30 change-mode systemd-resolved[1391]: Processing query...
Mar 26 00:53:30 change-mode systemd-resolved[1391]: Processing query...
Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query...
Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query...
Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query...
Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query...
Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query...
Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query...
Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query...
Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query...
Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query...
Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query...
Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query...
Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query...
Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query...
Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query...

This was fixed upstream in v233 by downgrading this message from log_info to 
log_debug:
https://github.com/systemd/systemd/pull/5233

** Affects: systemd
 Importance: Unknown
 Status: Unknown

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

** Bug watch added: github.com/systemd/systemd/issues #5233
   https://github.com/systemd/systemd/issues/5233

** Also affects: systemd via
   https://github.com/systemd/systemd/issues/5233
   Importance: Unknown
   Status: Unknown

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

Title:
  systemd-resolved spams the system log with useless “Processing
  query...” messages

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  New

Bug description:
  If you are running ‘journalctl -f’ to try to debug some other problem,
  you are constantly interrupted by zillions of these messages from
  systemd-resolved:

  Mar 26 00:53:27 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:27 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:30 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:30 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:30 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query...

  This was fixed upstream in v233 by downgrading this message from log_info to 
log_debug:
  https://github.com/systemd/systemd/pull/5233

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

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

[Touch-packages] [Bug 520546] Re: Alt-f2 switches to virtual terminal 2

[Anders Kaseorg]

Carl: I’m not sure whether that “@Andres” was directed at Andreas or me
(I’m Anders), but I still believe the situation is explained by my
comments #31 and #33; it is not a mystery why this is seen only
occasionally.  The bug is triggered every time the console-setup package
is installed or upgraded: specifically, when dpkg runs console-
setup.postinst which runs ‘setupcon --force’.  You can reproduce either
by running ‘sudo apt install --reinstall console-setup’ or by running
‘sudo setupcon --force’ directly.  The problem is cleared by rebooting
or by logging out and in again.

** Tags added: zesty

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

Title:
  Alt-f2 switches to virtual terminal 2

Status in console-cyrillic package in Ubuntu:
  Confirmed
Status in console-setup package in Ubuntu:
  Confirmed

Bug description:
  I'm running Ubuntu Lucid development branch.

  Pressing alt-f2 switches the screen to the second virtual terminal.
  Alt-f3 does the same to the third and so on. I expected alt-f2 to open
  the run dialog.

  I'm pretty sure that my keyboard is not malfunctioning as I can use
  all my applications normally. (Pressing O and Ctrl-O do not have the
  same effect.)

  I'm not sure which package I should file this bug against. I'll
  happily do an apport-collect once I know.

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

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

[Touch-packages] [Bug 1647031] Re: systemd-resolved’s 127.0.0.53 server does not follow CNAME records

[Anders Kaseorg]

Steve: I didn’t test yakkety since I thought it had gone back to the
configuration with dnsmasq on 127.0.0.1 rather than systemd-resolved on
127.0.0.53.  If that’s not the case, then yeah, it would be affected
too.

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

Title:
  systemd-resolved’s 127.0.0.53 server does not follow CNAME records

Status in systemd:
  New
Status in systemd package in Ubuntu:
  Triaged

Bug description:
  $ systemd-resolve www.freedesktop.org
  www.freedesktop.org: 131.252.210.176
   2610:10:20:722:a800:ff:feda:470f
   (annarchy.freedesktop.org)

  -- Information acquired via protocol DNS in 673.6ms.
  -- Data is authenticated: no
  $ ping www.freedesktop.org
  ping: www.freedesktop.org: Name or service not known
  $ cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.

  nameserver 127.0.0.53
  $ dig +no{cmd,comments,stats} www.freedesktop.org @127.0.0.53
  ;www.freedesktop.org. IN  A
  www.freedesktop.org.  7146IN  CNAME   annarchy.freedesktop.org.
  $ dig +no{cmd,comments,stats} www.freedesktop.org @8.8.8.8
  ;www.freedesktop.org. IN  A
  www.freedesktop.org.  14399   IN  CNAME   annarchy.freedesktop.org.
  annarchy.freedesktop.org. 14399   IN  A   131.252.210.176

  I trust it needn’t be explained why this makes the internet almost
  completely useless in zesty.

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

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

[Touch-packages] [Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

[Anders Kaseorg]

Ognjen, Vincent: This bug is marked with the “resolved” _tag_, as in
“systemd-resolved”, not as in “fixed”.  The bug _status_ is still open
(Confirmed).

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

Title:
  systemd-resolved breaks VPN with split-horizon DNS

Status in systemd:
  New
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I use a VPN configured with network-manager-openconnect-gnome in which
  a split-horizon DNS setup assigns different addresses to some names
  inside the remote network than the addresses seen for those names from
  outside the remote network.  However, systemd-resolved often decides
  to ignore the VPN’s DNS servers and use the local network’s DNS
  servers to resolve names (whether in the remote domain or not),
  breaking the split-horizon DNS.

  This related bug, reported by Lennart Poettering himself, was closed with the 
current Fedora release at the time reaching EOL:
  https://bugzilla.redhat.com/show_bug.cgi?id=1151544

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

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

[Touch-packages] [Bug 1647031] Re: systemd-resolved’s 127.0.0.53 server does not follow CNAME records

[Anders Kaseorg]

Or virtual machines: a VM running in virt-manager on a zesty host can’t
resolve CNAMEs (not even a zesty VM with libnss-resolve inside!).

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

Title:
  systemd-resolved’s 127.0.0.53 server does not follow CNAME records

Status in systemd:
  New
Status in systemd package in Ubuntu:
  Triaged

Bug description:
  $ systemd-resolve www.freedesktop.org
  www.freedesktop.org: 131.252.210.176
   2610:10:20:722:a800:ff:feda:470f
   (annarchy.freedesktop.org)

  -- Information acquired via protocol DNS in 673.6ms.
  -- Data is authenticated: no
  $ ping www.freedesktop.org
  ping: www.freedesktop.org: Name or service not known
  $ cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.

  nameserver 127.0.0.53
  $ dig +no{cmd,comments,stats} www.freedesktop.org @127.0.0.53
  ;www.freedesktop.org. IN  A
  www.freedesktop.org.  7146IN  CNAME   annarchy.freedesktop.org.
  $ dig +no{cmd,comments,stats} www.freedesktop.org @8.8.8.8
  ;www.freedesktop.org. IN  A
  www.freedesktop.org.  14399   IN  CNAME   annarchy.freedesktop.org.
  annarchy.freedesktop.org. 14399   IN  A   131.252.210.176

  I trust it needn’t be explained why this makes the internet almost
  completely useless in zesty.

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

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

[Touch-packages] [Bug 1647031] Re: systemd-resolved’s 127.0.0.53 server does not follow CNAME records

[Anders Kaseorg]

Another case that now necessarily relies on 127.0.0.53 is anything
inside a chroot (e.g. sbuild).  libnss-resolve can’t help there: you
can’t talk to the host D-Bus from inside, and also you might want to
chroot a distro that’s too old for libnss-resolve anyway.

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

Title:
  systemd-resolved’s 127.0.0.53 server does not follow CNAME records

Status in systemd:
  New
Status in systemd package in Ubuntu:
  Triaged

Bug description:
  $ systemd-resolve www.freedesktop.org
  www.freedesktop.org: 131.252.210.176
   2610:10:20:722:a800:ff:feda:470f
   (annarchy.freedesktop.org)

  -- Information acquired via protocol DNS in 673.6ms.
  -- Data is authenticated: no
  $ ping www.freedesktop.org
  ping: www.freedesktop.org: Name or service not known
  $ cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.

  nameserver 127.0.0.53
  $ dig +no{cmd,comments,stats} www.freedesktop.org @127.0.0.53
  ;www.freedesktop.org. IN  A
  www.freedesktop.org.  7146IN  CNAME   annarchy.freedesktop.org.
  $ dig +no{cmd,comments,stats} www.freedesktop.org @8.8.8.8
  ;www.freedesktop.org. IN  A
  www.freedesktop.org.  14399   IN  CNAME   annarchy.freedesktop.org.
  annarchy.freedesktop.org. 14399   IN  A   131.252.210.176

  I trust it needn’t be explained why this makes the internet almost
  completely useless in zesty.

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

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

[Touch-packages] [Bug 1649370] [NEW] libnss-{resolve,myhostname} don’t install correctly if previously removed without being purged

[Anders Kaseorg]

Public bug reported:

# grep hosts /etc/nsswitch.conf
hosts:  files myhostname dns
# apt install libnss-resolve
# grep hosts /etc/nsswitch.conf
hosts:  files myhostname resolve [!UNAVAIL=return] dns
# apt remove libnss-resolve
# grep hosts /etc/nsswitch.conf
hosts:  files myhostname dns
# apt install libnss-resolve
# grep hosts /etc/nsswitch.conf
hosts:  files myhostname dns

libnss-resolve.postinst and libnss-myhostname.postinst only update
/etc/nsswitch.conf if [ "$1" = configure ] && [ -z "$2" ].  If the
package was previously removed but not purged (it is in the Config-Files
state), dpkg passes the previous version as $2, so this fails.

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


** Tags: zesty

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

Title:
  libnss-{resolve,myhostname} don’t install correctly if previously
  removed without being purged

Status in systemd package in Ubuntu:
  New

Bug description:
  # grep hosts /etc/nsswitch.conf
  hosts:  files myhostname dns
  # apt install libnss-resolve
  # grep hosts /etc/nsswitch.conf
  hosts:  files myhostname resolve [!UNAVAIL=return] dns
  # apt remove libnss-resolve
  # grep hosts /etc/nsswitch.conf
  hosts:  files myhostname dns
  # apt install libnss-resolve
  # grep hosts /etc/nsswitch.conf
  hosts:  files myhostname dns

  libnss-resolve.postinst and libnss-myhostname.postinst only update
  /etc/nsswitch.conf if [ "$1" = configure ] && [ -z "$2" ].  If the
  package was previously removed but not purged (it is in the Config-
  Files state), dpkg passes the previous version as $2, so this fails.

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

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

[Touch-packages] [Bug 1647031] Re: systemd-resolved’s 127.0.0.53 server does not follow CNAME records

[Anders Kaseorg]

Whether or not it’s enabled, it is started automatically via D-BUS
activation (/lib/systemd/system/dbus-org.freedesktop.resolve1.service ->
systemd-resolved.service).

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

Title:
  systemd-resolved’s 127.0.0.53 server does not follow CNAME records

Status in systemd:
  New
Status in systemd package in Ubuntu:
  Triaged

Bug description:
  $ systemd-resolve www.freedesktop.org
  www.freedesktop.org: 131.252.210.176
   2610:10:20:722:a800:ff:feda:470f
   (annarchy.freedesktop.org)

  -- Information acquired via protocol DNS in 673.6ms.
  -- Data is authenticated: no
  $ ping www.freedesktop.org
  ping: www.freedesktop.org: Name or service not known
  $ cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.

  nameserver 127.0.0.53
  $ dig +no{cmd,comments,stats} www.freedesktop.org @127.0.0.53
  ;www.freedesktop.org. IN  A
  www.freedesktop.org.  7146IN  CNAME   annarchy.freedesktop.org.
  $ dig +no{cmd,comments,stats} www.freedesktop.org @8.8.8.8
  ;www.freedesktop.org. IN  A
  www.freedesktop.org.  14399   IN  CNAME   annarchy.freedesktop.org.
  annarchy.freedesktop.org. 14399   IN  A   131.252.210.176

  I trust it needn’t be explained why this makes the internet almost
  completely useless in zesty.

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

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

[Touch-packages] [Bug 1647031] Re: systemd-resolved’s 127.0.0.53 server does not follow CNAME records

[Anders Kaseorg]

Firefox, wget, ping, and Chrome do not work unless libnss-resolve is
installed.  (Perhaps Chrome recently started using NSS in some cases?)

Maybe this isn’t quite as critical as I thought given that ubuntu-
standard Recommends libnss-resolve.  Still, it’s not just an
“implementation detail”.  DNS lookups that cannot go through NSS (e.g.
SRV/TXT/MX/SSHFP/AFSDB records or any program that needs an asynchronous
API) are broken with or without libnss-resolve installed.  And nothing
pulls in libnss-resolve:i386 on amd64.

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

Title:
  systemd-resolved’s 127.0.0.53 server does not follow CNAME records

Status in systemd:
  New
Status in systemd package in Ubuntu:
  Triaged

Bug description:
  $ systemd-resolve www.freedesktop.org
  www.freedesktop.org: 131.252.210.176
   2610:10:20:722:a800:ff:feda:470f
   (annarchy.freedesktop.org)

  -- Information acquired via protocol DNS in 673.6ms.
  -- Data is authenticated: no
  $ ping www.freedesktop.org
  ping: www.freedesktop.org: Name or service not known
  $ cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.

  nameserver 127.0.0.53
  $ dig +no{cmd,comments,stats} www.freedesktop.org @127.0.0.53
  ;www.freedesktop.org. IN  A
  www.freedesktop.org.  7146IN  CNAME   annarchy.freedesktop.org.
  $ dig +no{cmd,comments,stats} www.freedesktop.org @8.8.8.8
  ;www.freedesktop.org. IN  A
  www.freedesktop.org.  14399   IN  CNAME   annarchy.freedesktop.org.
  annarchy.freedesktop.org. 14399   IN  A   131.252.210.176

  I trust it needn’t be explained why this makes the internet almost
  completely useless in zesty.

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

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

[Touch-packages] [Bug 1624320] Re: systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing entries

[Anders Kaseorg]

Martin: I still wonder what the point of having resolvconf is, if it’s
only ever supposed to be used to manage 127.0.0.53, and every other use
of resolvconf will lead to this bug resurfacing.  I still propose that
systemd-resolved should read from /run/resolvconf/resolv.conf without
adding 127.0.0.53 to it, and /etc/resolv.conf should be a symlink to
/lib/systemd/resolv.conf rather than /run/resolvconf/resolv.conf.


Willem: If systemd-resolved isn’t suitable to be the only nameserver in 
resolv.conf, then it isn’t suitable to be in resolv.conf at all.  I would 
rather either see these bugs worked out during the zesty cycle, or have 
systemd-resolved removed entirely, than leave the system in a half-broken state 
where the bugs in systemd-resolved get (probabilistically?) masked by the 
presence of other nameservers in resolv.conf.

In its current state, systemd-resolved is thoroughly broken on account
of (at least) bug 1647031.  I had to downgrade network-manager because
switching to a resolver that doesn’t follow CNAME records breaks way too
much of the internet.  This might not have been noticed with other
nameservers in resolv.conf.  (Although now that it has, I’m getting
increasingly concerned by the switch not having been reverted yet…)

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

Title:
  systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing
  entries

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  systemd-resolved, or more precisely the hook script
  /lib/systemd/system/systemd-resolved.service.d/resolvconf.conf, causes
  resolvconf to add 127.0.0.53 to the set of nameservers in
  /etc/resolv.conf alongside the other nameservers.  That makes no sense
  because systemd-resolved sets up 127.0.0.53 as a proxy for those other
  nameservers.  The effect is similar to bug 1624071 but for
  applications doing their own DNS lookups.  It breaks any DNSSEC
  validation that systemd-resolved tries to do; applications will
  failover to the other nameservers, bypassing validation failures.  And
  it makes failing queries take twice as long.

  /etc/resolv.conf should have only 127.0.0.53 when systemd-resolved is
  active.

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

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

[Touch-packages] [Bug 1647178] Re: systemd-resolved unable to resolve certain subdomains

[Anders Kaseorg]

Possible duplicate of bug 1647031.

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

Title:
  systemd-resolved unable to resolve certain subdomains

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  After upgrade to systemd-resolved, certain very well known subdomains
  are no longer resolved. Their TLD do resolve correctly. Example given
  with mail.google.com and google.com

  On xenial :
  $ nslookup mail.google.com
  Server: 192.168.1.1
  Address:192.168.1.1#53

  Non-authoritative answer:
  mail.google.com canonical name = googlemail.l.google.com.
  Name:   googlemail.l.google.com
  Address: 216.58.198.197

  $ dig mail.google.com

  ; <<>> DiG 9.10.3-P4-Ubuntu <<>> mail.google.com
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 57929
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 4000
  ;; QUESTION SECTION:
  ;mail.google.com.   IN  A

  ;; ANSWER SECTION:
  mail.google.com.441512  IN  CNAME   googlemail.l.google.com.
  googlemail.l.google.com. 274IN  A   216.58.198.197

  ;; Query time: 14 msec
  ;; SERVER: 192.168.1.1#53(192.168.1.1)
  ;; WHEN: Sun Dec 04 18:12:43 CET 2016
  ;; MSG SIZE  rcvd: 87

  On Zesty using systemd-resolved :

  # nslookup mail.google.com
  Server: 10.0.3.1
  Address:10.0.3.1#53

  Non-authoritative answer:
  mail.google.com canonical name = googlemail.l.google.com.

  # nslookup google.com
  Server: 10.0.3.1
  Address:10.0.3.1#53

  Non-authoritative answer:
  Name:   google.com
  Address: 216.58.198.206

  # dig mail.google.com

  ; <<>> DiG 9.10.3-P4-Ubuntu <<>> mail.google.com
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10775
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 4096
  ;; QUESTION SECTION:
  ;mail.google.com.   IN  A

  ;; ANSWER SECTION:
  mail.google.com.441414  IN  CNAME   googlemail.l.google.com.

  ;; Query time: 0 msec
  ;; SERVER: 10.0.3.1#53(10.0.3.1)
  ;; WHEN: Sun Dec 04 17:14:21 UTC 2016
  ;; MSG SIZE  rcvd: 81

  # dig google.com

  ; <<>> DiG 9.10.3-P4-Ubuntu <<>> google.com
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 25303
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 4096
  ;; QUESTION SECTION:
  ;google.com.IN  A

  ;; ANSWER SECTION:
  google.com. 160 IN  A   216.58.198.206

  ;; Query time: 0 msec
  ;; SERVER: 10.0.3.1#53(10.0.3.1)
  ;; WHEN: Sun Dec 04 17:14:37 UTC 2016
  ;; MSG SIZE  rcvd: 55

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

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

[Touch-packages] [Bug 1647178] Re: systemd-resolved unable to resolve certain subdomains

[Anders Kaseorg]

For example, I see

$ dig +no{cmd,comments,stats} mail.google.com @8.8.8.8
;mail.google.com.   IN  A
mail.google.com.86312   IN  CNAME   googlemail.l.google.com.
googlemail.l.google.com. 212IN  A   216.58.219.229
$ dig +no{cmd,comments,stats} mail.google.com @127.0.0.53
;mail.google.com.   IN  A
mail.google.com.321204  IN  CNAME   googlemail.l.google.com.

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

Title:
  systemd-resolved unable to resolve certain subdomains

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  After upgrade to systemd-resolved, certain very well known subdomains
  are no longer resolved. Their TLD do resolve correctly. Example given
  with mail.google.com and google.com

  On xenial :
  $ nslookup mail.google.com
  Server: 192.168.1.1
  Address:192.168.1.1#53

  Non-authoritative answer:
  mail.google.com canonical name = googlemail.l.google.com.
  Name:   googlemail.l.google.com
  Address: 216.58.198.197

  $ dig mail.google.com

  ; <<>> DiG 9.10.3-P4-Ubuntu <<>> mail.google.com
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 57929
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 4000
  ;; QUESTION SECTION:
  ;mail.google.com.   IN  A

  ;; ANSWER SECTION:
  mail.google.com.441512  IN  CNAME   googlemail.l.google.com.
  googlemail.l.google.com. 274IN  A   216.58.198.197

  ;; Query time: 14 msec
  ;; SERVER: 192.168.1.1#53(192.168.1.1)
  ;; WHEN: Sun Dec 04 18:12:43 CET 2016
  ;; MSG SIZE  rcvd: 87

  On Zesty using systemd-resolved :

  # nslookup mail.google.com
  Server: 10.0.3.1
  Address:10.0.3.1#53

  Non-authoritative answer:
  mail.google.com canonical name = googlemail.l.google.com.

  # nslookup google.com
  Server: 10.0.3.1
  Address:10.0.3.1#53

  Non-authoritative answer:
  Name:   google.com
  Address: 216.58.198.206

  # dig mail.google.com

  ; <<>> DiG 9.10.3-P4-Ubuntu <<>> mail.google.com
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10775
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 4096
  ;; QUESTION SECTION:
  ;mail.google.com.   IN  A

  ;; ANSWER SECTION:
  mail.google.com.441414  IN  CNAME   googlemail.l.google.com.

  ;; Query time: 0 msec
  ;; SERVER: 10.0.3.1#53(10.0.3.1)
  ;; WHEN: Sun Dec 04 17:14:21 UTC 2016
  ;; MSG SIZE  rcvd: 81

  # dig google.com

  ; <<>> DiG 9.10.3-P4-Ubuntu <<>> google.com
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 25303
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 4096
  ;; QUESTION SECTION:
  ;google.com.IN  A

  ;; ANSWER SECTION:
  google.com. 160 IN  A   216.58.198.206

  ;; Query time: 0 msec
  ;; SERVER: 10.0.3.1#53(10.0.3.1)
  ;; WHEN: Sun Dec 04 17:14:37 UTC 2016
  ;; MSG SIZE  rcvd: 55

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

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

[Touch-packages] [Bug 1648037] Re: Ubuntu 16.10: systemd-resolved does not resolve some domains

[Anders Kaseorg]

Possible duplicate of bug 1647031.  For example, I see

$ dig +no{cmd,comments,stats} buy.ubuntu.com @8.8.8.8
;buy.ubuntu.com.IN  A
buy.ubuntu.com. 599 IN  CNAME   
ubuntu-advantage-cloud-guest.myshopify.com.
ubuntu-advantage-cloud-guest.myshopify.com. 3599 IN CNAME shops.myshopify.com.
shops.myshopify.com.1799IN  A   23.227.38.32
$ dig +no{cmd,comments,stats} buy.ubuntu.com @127.0.0.53
;buy.ubuntu.com.IN  A
buy.ubuntu.com. 557 IN  CNAME   
ubuntu-advantage-cloud-guest.myshopify.com.

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

Title:
  Ubuntu 16.10: systemd-resolved does not resolve some domains

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Some domains are not resolved with default systemd-resolved set up on
  Ubuntu 16.10. This set up is querying the DNS server given by DHCP,
  and is my ISP's router.

  Now, checking with `dig` directly against 192.168.1.1 (the router),
  dig complains that "Warning: Message parser reports malformed message
  packet.". And indeed, for the domains that do not resolve, this
  warning is always given by dig, when I query the router.

  It would appear that the router or its upstream is somehow breaking
  the DNS packets/responses and I'll have to figure that one out
  separately.

  The bug here is that systemd-resolved is failing on those while every
  other resolver seems to be working fine with those (supposedly
  malformed) replies. All other devices in the network, phones, windows,
  ubuntu 16.04, etc...  are resolving with those just fine.

  Most notably, I can't resolve  "buy.ubuntu.com". I've captured the
  packet/reply I get from my router, it's attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-9ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Dec  7 11:17:43 2016
  InstallationDate: Installed on 2016-11-28 (8 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-30-generic 
root=UUID=eb750983-a34c-4b58-b5f0-a0cfa1130d1b ro
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/04/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0504
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-R
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0504:bd06/04/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH81M-R:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  modified.conffile..etc.systemd.resolved.conf: [modified]
  mtime.conffile..etc.systemd.resolved.conf: 2016-12-07T10:46:19.412121

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

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

[Touch-packages] [Bug 1647105] Re: Merge vim 2:8.0.0095-1 from Debian testing/unstable

[Anders Kaseorg]

** Patch added: "Debdiff from vim 2:8.0.0095-1 in Debian testing/unstable"
   
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1647105/+attachment/4787466/+files/vim_8.0.0095-1_1ubuntu1.debdiff

** Patch removed: "Debdiff from vim 2:8.0.0095-1 in Debian testing/unstable"
   
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1647105/+attachment/4787109/+files/vim_8.0.0095-1_1ubuntu1.debdiff

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

Title:
  Merge vim 2:8.0.0095-1 from Debian testing/unstable

Status in vim package in Ubuntu:
  Confirmed

Bug description:
  Since Debian has now migrated vim from Python 2 to Python 3, this
  drops the Python 2 variants.

  Test build: https://launchpad.net/~andersk/+archive/ubuntu/ppa

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

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

[Touch-packages] [Bug 1624039] Re: Vim 8.0 should be backported in

[Anders Kaseorg]

*** This bug is a duplicate of bug 1647105 ***
https://bugs.launchpad.net/bugs/1647105

** This bug has been marked a duplicate of bug 1647105
   Merge vim 2:8.0.0095-1 from Debian testing/unstable

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

Title:
  Vim 8.0 should be backported in

Status in vim package in Ubuntu:
  New

Bug description:
  As Vim 8.0 has now been released:
  https://groups.google.com/forum/m/#!topic/vim_announce/EKTuhjF3ET0
  This version should be backported into currently supported releases.

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

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

[Touch-packages] [Bug 1647105] [NEW] Merge vim 2:8.0.0095-1 from Debian testing/unstable

[Anders Kaseorg]

Public bug reported:

Since Debian has now migrated vim from Python 2 to Python 3, this drops
the Python 2 variants.

Test build: https://launchpad.net/~andersk/+archive/ubuntu/ppa

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


** Tags: patch

** Patch added: "Debdiff from vim 2:8.0.0095-1 in Debian testing/unstable"
   
https://bugs.launchpad.net/bugs/1647105/+attachment/4787109/+files/vim_8.0.0095-1_1ubuntu1.debdiff

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

Title:
  Merge vim 2:8.0.0095-1 from Debian testing/unstable

Status in vim package in Ubuntu:
  New

Bug description:
  Since Debian has now migrated vim from Python 2 to Python 3, this
  drops the Python 2 variants.

  Test build: https://launchpad.net/~andersk/+archive/ubuntu/ppa

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

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

[Touch-packages] [Bug 1647031] [NEW] systemd-resolved’s 127.0.0.53 server does not follow CNAME records

[Anders Kaseorg]

Public bug reported:

$ systemd-resolve www.freedesktop.org
www.freedesktop.org: 131.252.210.176
 2610:10:20:722:a800:ff:feda:470f
 (annarchy.freedesktop.org)

-- Information acquired via protocol DNS in 673.6ms.
-- Data is authenticated: no
$ ping www.freedesktop.org
ping: www.freedesktop.org: Name or service not known
$ cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual nameservers.

nameserver 127.0.0.53
$ dig +no{cmd,comments,stats} www.freedesktop.org @127.0.0.53
;www.freedesktop.org.   IN  A
www.freedesktop.org.7146IN  CNAME   annarchy.freedesktop.org.
$ dig +no{cmd,comments,stats} www.freedesktop.org @8.8.8.8
;www.freedesktop.org.   IN  A
www.freedesktop.org.14399   IN  CNAME   annarchy.freedesktop.org.
annarchy.freedesktop.org. 14399 IN  A   131.252.210.176

I trust it needn’t be explained why this makes the internet almost
completely useless in zesty.

** Affects: systemd
 Importance: Unknown
 Status: Unknown

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

** Bug watch added: github.com/systemd/systemd/issues #3826
   https://github.com/systemd/systemd/issues/3826

** Also affects: systemd via
   https://github.com/systemd/systemd/issues/3826
   Importance: Unknown
   Status: Unknown

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

Title:
  systemd-resolved’s 127.0.0.53 server does not follow CNAME records

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  New

Bug description:
  $ systemd-resolve www.freedesktop.org
  www.freedesktop.org: 131.252.210.176
   2610:10:20:722:a800:ff:feda:470f
   (annarchy.freedesktop.org)

  -- Information acquired via protocol DNS in 673.6ms.
  -- Data is authenticated: no
  $ ping www.freedesktop.org
  ping: www.freedesktop.org: Name or service not known
  $ cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.

  nameserver 127.0.0.53
  $ dig +no{cmd,comments,stats} www.freedesktop.org @127.0.0.53
  ;www.freedesktop.org. IN  A
  www.freedesktop.org.  7146IN  CNAME   annarchy.freedesktop.org.
  $ dig +no{cmd,comments,stats} www.freedesktop.org @8.8.8.8
  ;www.freedesktop.org. IN  A
  www.freedesktop.org.  14399   IN  CNAME   annarchy.freedesktop.org.
  annarchy.freedesktop.org. 14399   IN  A   131.252.210.176

  I trust it needn’t be explained why this makes the internet almost
  completely useless in zesty.

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

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

[Touch-packages] [Bug 1577460] Re: mkinitramfs --help > Core dumped

[Anders Kaseorg]

Upstream applied an equivalent patch:
http://git.kernel.org/cgit/utils/util-linux/util-linux.git/commit/?id=e1164591f7927402af8d73d340e75dbfeb06a288

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

Title:
  mkinitramfs --help > Core dumped

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in glibc package in Ubuntu:
  Fix Released
Status in util-linux package in Ubuntu:
  New
Status in glibc source package in Xenial:
  Fix Committed
Status in util-linux source package in Xenial:
  New

Bug description:
  Problem Description
  ==
  root@zlin060:~# mkinitramfs --help
  Segmentation fault (core dumped)
  W: non-GNU getopt
  root@zlin060:~#

  == Comment: #9 - Heinz-Werner Seeck  - 
2016-05-02 10:09:34 ==
  With Ubuntu 14.40 login via ssh:

  Following cmd :
  'getopt -o c:d:ko:r:v -n /usr/sbin/mkinitramfs -- --help'

  Following call-stack occured (creates coredump):

  #0  __strncmp_c (s1=0x2e6575634a500a6d , 
  s1@entry=0x2e6575634a500a6a , 
  s2=0x3fff7fff7ae "p", s2@entry=0x3fff7fff7ab "gelp", n=n@entry=4) at 
../string/strncmp.c:44
  #1  0x03ff7e9d4252 in _getopt_internal_r (argc=, 
argv=0x40, 
  optstring=0x20030 , longopts=, 
  longind=, long_only=0, d=0x3ff7ea8c330 , 
posixly_correct=0) at getopt.c:546
  #2  0x03ff7e9d51f2 in _getopt_internal (argc=, 
argv=, 
  optstring=, longopts=, 
longind=0x3fff7ffe674, long_only=0, posixly_correct=0)
  at getopt.c:1175
  #3  0x03ff7e9d52b6 in getopt_long (argc=, argv=, options=, 
  long_options=, opt_index=0x3fff7ffe674) at getopt1.c:65
  #4  0x02aa236821d8 in ?? ()
  #5  0x02aa23681c22 in main ()

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

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

[Touch-packages] [Bug 1577460] Re: mkinitramfs --help > Core dumped

[Anders Kaseorg]

Upstream submission: http://marc.info/?l=util-linux-
ng&m=147691687505965&w=2

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

Title:
  mkinitramfs --help > Core dumped

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in glibc package in Ubuntu:
  Fix Released
Status in util-linux package in Ubuntu:
  New
Status in glibc source package in Xenial:
  Fix Committed
Status in util-linux source package in Xenial:
  New

Bug description:
  Problem Description
  ==
  root@zlin060:~# mkinitramfs --help
  Segmentation fault (core dumped)
  W: non-GNU getopt
  root@zlin060:~#

  == Comment: #9 - Heinz-Werner Seeck  - 
2016-05-02 10:09:34 ==
  With Ubuntu 14.40 login via ssh:

  Following cmd :
  'getopt -o c:d:ko:r:v -n /usr/sbin/mkinitramfs -- --help'

  Following call-stack occured (creates coredump):

  #0  __strncmp_c (s1=0x2e6575634a500a6d , 
  s1@entry=0x2e6575634a500a6a , 
  s2=0x3fff7fff7ae "p", s2@entry=0x3fff7fff7ab "gelp", n=n@entry=4) at 
../string/strncmp.c:44
  #1  0x03ff7e9d4252 in _getopt_internal_r (argc=, 
argv=0x40, 
  optstring=0x20030 , longopts=, 
  longind=, long_only=0, d=0x3ff7ea8c330 , 
posixly_correct=0) at getopt.c:546
  #2  0x03ff7e9d51f2 in _getopt_internal (argc=, 
argv=, 
  optstring=, longopts=, 
longind=0x3fff7ffe674, long_only=0, posixly_correct=0)
  at getopt.c:1175
  #3  0x03ff7e9d52b6 in getopt_long (argc=, argv=, options=, 
  long_options=, opt_index=0x3fff7ffe674) at getopt1.c:65
  #4  0x02aa236821d8 in ?? ()
  #5  0x02aa23681c22 in main ()

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

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

[Touch-packages] [Bug 1577460] Re: mkinitramfs --help > Core dumped

[Anders Kaseorg]

This is a util-linux bug, not a glibc bug.  I have sent this patch
upstream.

** Also affects: util-linux (Ubuntu)
   Importance: Undecided
   Status: New

** Patch added: 
"0001-getopt-Terminate-long_options-even-if-add_long_optio.patch"
   
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1577460/+attachment/4763969/+files/0001-getopt-Terminate-long_options-even-if-add_long_optio.patch

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

Title:
  mkinitramfs --help > Core dumped

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in glibc package in Ubuntu:
  Fix Released
Status in util-linux package in Ubuntu:
  New
Status in glibc source package in Xenial:
  Fix Committed
Status in util-linux source package in Xenial:
  New

Bug description:
  Problem Description
  ==
  root@zlin060:~# mkinitramfs --help
  Segmentation fault (core dumped)
  W: non-GNU getopt
  root@zlin060:~#

  == Comment: #9 - Heinz-Werner Seeck  - 
2016-05-02 10:09:34 ==
  With Ubuntu 14.40 login via ssh:

  Following cmd :
  'getopt -o c:d:ko:r:v -n /usr/sbin/mkinitramfs -- --help'

  Following call-stack occured (creates coredump):

  #0  __strncmp_c (s1=0x2e6575634a500a6d , 
  s1@entry=0x2e6575634a500a6a , 
  s2=0x3fff7fff7ae "p", s2@entry=0x3fff7fff7ab "gelp", n=n@entry=4) at 
../string/strncmp.c:44
  #1  0x03ff7e9d4252 in _getopt_internal_r (argc=, 
argv=0x40, 
  optstring=0x20030 , longopts=, 
  longind=, long_only=0, d=0x3ff7ea8c330 , 
posixly_correct=0) at getopt.c:546
  #2  0x03ff7e9d51f2 in _getopt_internal (argc=, 
argv=, 
  optstring=, longopts=, 
longind=0x3fff7ffe674, long_only=0, posixly_correct=0)
  at getopt.c:1175
  #3  0x03ff7e9d52b6 in getopt_long (argc=, argv=, options=, 
  long_options=, opt_index=0x3fff7ffe674) at getopt1.c:65
  #4  0x02aa236821d8 in ?? ()
  #5  0x02aa23681c22 in main ()

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

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

[Touch-packages] [Bug 1449001] Re: systemd-resolved: please do not use Google public DNS by default

[Anders Kaseorg]

The 8.8.8.8 fallback is not only used on misconfigured systems!  It’s
also used for a short period while initially connecting or reconnecting
to totally healthy networks with DHCP.  So the excuse that privacy-
conscious users should just use DHCP holds no water.

https://github.com/systemd/systemd/issues/4175#issuecomment-252571482

** Bug watch added: github.com/systemd/systemd/issues #4175
   https://github.com/systemd/systemd/issues/4175

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

Title:
  systemd-resolved: please do not use Google public DNS by default

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Triaged

Bug description:
  systemd-resolved will fall back to Google public DNS (8.8.8.8, etc.)
  in the absence of other configured DNS servers.

  systemd-resolved is not enabled by default in Ubuntu 15.04, but it is
  installed by default and will behave in this way if enabled by the
  user.

  $ cat /etc/systemd/resolved.conf 
  (...)
  # Entries in this file show the compile time defaults.
  (...)
  #FallbackDNS=8.8.8.8 8.8.4.4 2001:4860:4860:: 2001:4860:4860::8844

  This raises privacy concerns since in the event of accidental
  misconfiguration DNS queries will be sent unencrypted across the
  internet, and potentially also security concerns given systemd-
  resolved does not perform DNSSEC validation and is not particularly
  well hardened against malicious responses e.g. from a MITM
  (http://www.openwall.com/lists/oss-security/2014/11/12/5).

  I believe that it would be better to fail safe if no DNS server is
  configured -- i.e. have DNS lookups fail; it's better that the user is
  aware of their misconfiguration, rather than silently sending their
  queries to Google.  The user can intentionally opt to use Google
  public DNS if they wish.


  Steps to reproduce:
  1. Remove existing DNS configuration (from /etc/network/interfaces, 
/etc/resolv.conf, /etc/resolvconf/resolv.conf.d/*)
  2. Reboot, or otherwise clear relevant state
  3. sudo service systemd-resolved start
  4. Note that Google's servers are listed in /run/systemd/resolve/resolv.conf
  5. If systemd-resolved is enabled in /etc/nsswitch.conf (it isn't by 
default), observe that DNS lookups probably still work, and queries are being 
sent to one of Google's servers

  
  Possible workaround/bugfix: ship a resolved.conf which clears the FallbackDNS 
parameter.

  
  This issue has been discussed in the Debian BTS 
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761658).  My interpretation 
of the Debian package maintainer's position is that a user concerned with the 
privacy implications shouldn't let systemd get into a state where it uses the 
fallback DNS servers (quoting Marco d'Itri: "Short summary: have a resolv.conf 
file or use DHCP").  I would argue that it's safest not to have fallback DNS 
servers configured at all by default.

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

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

[Touch-packages] [Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

[Anders Kaseorg]

** Tags removed: regression-release

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

Title:
  systemd-resolved breaks VPN with split-horizon DNS

Status in systemd:
  New
Status in systemd package in Ubuntu:
  Triaged

Bug description:
  I use a VPN configured with network-manager-openconnect-gnome in which
  a split-horizon DNS setup assigns different addresses to some names
  inside the remote network than the addresses seen for those names from
  outside the remote network.  However, systemd-resolved often decides
  to ignore the VPN’s DNS servers and use the local network’s DNS
  servers to resolve names (whether in the remote domain or not),
  breaking the split-horizon DNS.

  This related bug, reported by Lennart Poettering himself, was closed with the 
current Fedora release at the time reaching EOL:
  https://bugzilla.redhat.com/show_bug.cgi?id=1151544

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

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

[Touch-packages] [Bug 1628778] Re: systemd-resolved: after network reconnection, DNSSEC unsigned zones treated as bogus, stop resolving

[Anders Kaseorg]

** Description changed:

  On the MIT network (which runs some ancient version of BIND 9), systemd-
  resolved stops resolving anything that isn’t DNSSEC-signed after I
  disconnect and reconnect the network. Signed zones continue to resolve.
  
  This happens with either DNSSEC=yes or the default DNSSEC=allow-
  downgrade.
  
  $ systemd-resolve github.com
  github.com: 192.30.253.113
  
  -- Information acquired via protocol DNS in 15.6ms.
  -- Data is authenticated: no
  $ # (disconnect and reconnect wifi)
  $ systemd-resolve github.com
  github.com: resolve call failed: DNSSEC validation failed: no-signature
  
  More debug information is available in my upstream report
  (https://github.com/systemd/systemd/issues/4175), which has gotten no
  response in the last week and a half.
  
  I’m refiling this here because I believe that this regression and others
  (bug 1588230, bug 1624071, bug 1624317, bug 1449001) indicate that
  systemd-resolved is not ready for production, and with final freeze just
  a week away, leaving systemd-resolved enabled for the yakkety release
- would be reckless.
+ would be reckless.  [Edit: Oh, I see that conclusion was already reached
+ yesterday.]

** Tags removed: regression-release

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

Title:
  systemd-resolved: after network reconnection, DNSSEC unsigned zones
  treated as bogus, stop resolving

Status in systemd package in Ubuntu:
  New

Bug description:
  On the MIT network (which runs some ancient version of BIND 9),
  systemd-resolved stops resolving anything that isn’t DNSSEC-signed
  after I disconnect and reconnect the network. Signed zones continue to
  resolve.

  This happens with either DNSSEC=yes or the default DNSSEC=allow-
  downgrade.

  $ systemd-resolve github.com
  github.com: 192.30.253.113

  -- Information acquired via protocol DNS in 15.6ms.
  -- Data is authenticated: no
  $ # (disconnect and reconnect wifi)
  $ systemd-resolve github.com
  github.com: resolve call failed: DNSSEC validation failed: no-signature

  More debug information is available in my upstream report
  (https://github.com/systemd/systemd/issues/4175), which has gotten no
  response in the last week and a half.

  I’m refiling this here because I believe that this regression and
  others (bug 1588230, bug 1624071, bug 1624317, bug 1449001) indicate
  that systemd-resolved is not ready for production, and with final
  freeze just a week away, leaving systemd-resolved enabled for the
  yakkety release would be reckless.  [Edit: Oh, I see that conclusion
  was already reached yesterday.]

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

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

[Touch-packages] [Bug 1628778] [NEW] systemd-resolved: after network reconnection, DNSSEC unsigned zones treated as bogus, stop resolving

[Anders Kaseorg]

Public bug reported:

On the MIT network (which runs some ancient version of BIND 9), systemd-
resolved stops resolving anything that isn’t DNSSEC-signed after I
disconnect and reconnect the network. Signed zones continue to resolve.

This happens with either DNSSEC=yes or the default DNSSEC=allow-
downgrade.

$ systemd-resolve github.com
github.com: 192.30.253.113

-- Information acquired via protocol DNS in 15.6ms.
-- Data is authenticated: no
$ # (disconnect and reconnect wifi)
$ systemd-resolve github.com
github.com: resolve call failed: DNSSEC validation failed: no-signature

More debug information is available in my upstream report
(https://github.com/systemd/systemd/issues/4175), which has gotten no
response in the last week and a half.

I’m refiling this here because I believe that this regression and others
(bug 1588230, bug 1624071, bug 1624317, bug 1449001) indicate that
systemd-resolved is not ready for production, and with final freeze just
a week away, leaving systemd-resolved enabled for the yakkety release
would be reckless.

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


** Tags: regression-release yakkety

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

Title:
  systemd-resolved: after network reconnection, DNSSEC unsigned zones
  treated as bogus, stop resolving

Status in systemd package in Ubuntu:
  New

Bug description:
  On the MIT network (which runs some ancient version of BIND 9),
  systemd-resolved stops resolving anything that isn’t DNSSEC-signed
  after I disconnect and reconnect the network. Signed zones continue to
  resolve.

  This happens with either DNSSEC=yes or the default DNSSEC=allow-
  downgrade.

  $ systemd-resolve github.com
  github.com: 192.30.253.113

  -- Information acquired via protocol DNS in 15.6ms.
  -- Data is authenticated: no
  $ # (disconnect and reconnect wifi)
  $ systemd-resolve github.com
  github.com: resolve call failed: DNSSEC validation failed: no-signature

  More debug information is available in my upstream report
  (https://github.com/systemd/systemd/issues/4175), which has gotten no
  response in the last week and a half.

  I’m refiling this here because I believe that this regression and
  others (bug 1588230, bug 1624071, bug 1624317, bug 1449001) indicate
  that systemd-resolved is not ready for production, and with final
  freeze just a week away, leaving systemd-resolved enabled for the
  yakkety release would be reckless.

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

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

[Touch-packages] [Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

[Anders Kaseorg]

** Tags added: regression-release

** Tags added: yakkety

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

Title:
  systemd-resolved breaks VPN with split-horizon DNS

Status in systemd:
  New
Status in systemd package in Ubuntu:
  Triaged

Bug description:
  I use a VPN configured with network-manager-openconnect-gnome in which
  a split-horizon DNS setup assigns different addresses to some names
  inside the remote network than the addresses seen for those names from
  outside the remote network.  However, systemd-resolved often decides
  to ignore the VPN’s DNS servers and use the local network’s DNS
  servers to resolve names (whether in the remote domain or not),
  breaking the split-horizon DNS.

  This related bug, reported by Lennart Poettering himself, was closed with the 
current Fedora release at the time reaching EOL:
  https://bugzilla.redhat.com/show_bug.cgi?id=1151544

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

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

[Touch-packages] [Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

[Anders Kaseorg]

I want to be clear that in my situation the VPN’s DNS servers are _not_
marked as domain-restricted.

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

Title:
  systemd-resolved breaks VPN with split-horizon DNS

Status in systemd:
  New
Status in systemd package in Ubuntu:
  Triaged

Bug description:
  I use a VPN configured with network-manager-openconnect-gnome in which
  a split-horizon DNS setup assigns different addresses to some names
  inside the remote network than the addresses seen for those names from
  outside the remote network.  However, systemd-resolved often decides
  to ignore the VPN’s DNS servers and use the local network’s DNS
  servers to resolve names (whether in the remote domain or not),
  breaking the split-horizon DNS.

  This related bug, reported by Lennart Poettering himself, was closed with the 
current Fedora release at the time reaching EOL:
  https://bugzilla.redhat.com/show_bug.cgi?id=1151544

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

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

[Touch-packages] [Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

[Anders Kaseorg]

(I believe the requested information has been provided.)

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

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

Title:
  systemd-resolved breaks VPN with split-horizon DNS

Status in systemd:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  I use a VPN configured with network-manager-openconnect-gnome in which
  a split-horizon DNS setup assigns different addresses to some names
  inside the remote network than the addresses seen for those names from
  outside the remote network.  However, systemd-resolved often decides
  to ignore the VPN’s DNS servers and use the local network’s DNS
  servers to resolve names (whether in the remote domain or not),
  breaking the split-horizon DNS.

  This related bug, reported by Lennart Poettering himself, was closed with the 
current Fedora release at the time reaching EOL:
  https://bugzilla.redhat.com/show_bug.cgi?id=1151544

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

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

[Touch-packages] [Bug 1624320] Re: systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing entries

[Anders Kaseorg]

DNS resolution outside NSS shouldn’t be dismissed as an edge case for
software that’s too conceited to use NSS.  NSS only exposes A, , and
PTR records.  There’s plenty of software in the official archive that
needs other records from DNS (off the top of my head: SRV, TXT, MX,
SSHFP, AFSDB) and cannot get them from NSS.

> resolved reads their DNS servers *from* resolv.conf.

Right, so perhaps when resolvconf is in use, systemd-resolved should
read those from /run/resolvconf/resolv.conf directly, and
/etc/resolv.conf should be a symlink to /lib/systemd/resolv.conf rather
than /run/resolvconf/resolv.conf?

> you can't both chose to *not* use NSS *and* rely on NSS to do DNSSEC
for you.

Why not?  It was working with NetworkManager managing a dnsmasq, since
NetworkManager installed the local proxy as the only nameserver visible
in resolv.conf, and it would work again if systemd-resolved did the
same.

This will also be needed to fix problems like
https://github.com/systemd/systemd/issues/3421 for programs that cannot
use NSS.

** Bug watch added: github.com/systemd/systemd/issues #3421
   https://github.com/systemd/systemd/issues/3421

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

Title:
  systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing
  entries

Status in systemd package in Ubuntu:
  Triaged

Bug description:
  systemd-resolved, or more precisely the hook script
  /lib/systemd/system/systemd-resolved.service.d/resolvconf.conf, causes
  resolvconf to add 127.0.0.53 to the set of nameservers in
  /etc/resolv.conf alongside the other nameservers.  That makes no sense
  because systemd-resolved sets up 127.0.0.53 as a proxy for those other
  nameservers.  The effect is similar to bug 1624071 but for
  applications doing their own DNS lookups.  It breaks any DNSSEC
  validation that systemd-resolved tries to do; applications will
  failover to the other nameservers, bypassing validation failures.  And
  it makes failing queries take twice as long.

  /etc/resolv.conf should have only 127.0.0.53 when systemd-resolved is
  active.

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

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

[Touch-packages] [Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

[Anders Kaseorg]

3421 seems like the opposite of this problem.  There, queries that
belong on the local network instead go to the domain-limited VPN
servers.  Here, queries that should go to the VPN servers (which in my
case are not domain-limited) instead go to the local servers.  Also,
here I am using NetworkManager, not systemd-networkd.

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

Title:
  systemd-resolved breaks VPN with split-horizon DNS

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  I use a VPN configured with network-manager-openconnect-gnome in which
  a split-horizon DNS setup assigns different addresses to some names
  inside the remote network than the addresses seen for those names from
  outside the remote network.  However, systemd-resolved often decides
  to ignore the VPN’s DNS servers and use the local network’s DNS
  servers to resolve names (whether in the remote domain or not),
  breaking the split-horizon DNS.

  This related bug, reported by Lennart Poettering himself, was closed with the 
current Fedora release at the time reaching EOL:
  https://bugzilla.redhat.com/show_bug.cgi?id=1151544

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

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

[Touch-packages] [Bug 1624320] [NEW] systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing entries

[Anders Kaseorg]

Public bug reported:

systemd-resolved, or more precisely the hook script /lib/systemd/system
/systemd-resolved.service.d/resolvconf.conf, causes resolvconf to add
127.0.0.53 to the set of nameservers in /etc/resolv.conf alongside the
other nameservers.  That makes no sense because systemd-resolved sets up
127.0.0.53 as a proxy for those other nameservers.  The effect is
similar to bug 1624071 but for applications doing their own DNS lookups.
It breaks any DNSSEC validation that systemd-resolved tries to do;
applications will failover to the other nameservers, bypassing
validation failures.  And it makes failing queries take twice as long.

/etc/resolv.conf should have only 127.0.0.53 when systemd-resolved is
active.

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

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

Title:
  systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing
  entries

Status in systemd package in Ubuntu:
  New

Bug description:
  systemd-resolved, or more precisely the hook script
  /lib/systemd/system/systemd-resolved.service.d/resolvconf.conf, causes
  resolvconf to add 127.0.0.53 to the set of nameservers in
  /etc/resolv.conf alongside the other nameservers.  That makes no sense
  because systemd-resolved sets up 127.0.0.53 as a proxy for those other
  nameservers.  The effect is similar to bug 1624071 but for
  applications doing their own DNS lookups.  It breaks any DNSSEC
  validation that systemd-resolved tries to do; applications will
  failover to the other nameservers, bypassing validation failures.  And
  it makes failing queries take twice as long.

  /etc/resolv.conf should have only 127.0.0.53 when systemd-resolved is
  active.

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

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

[Touch-packages] [Bug 1624317] [NEW] systemd-resolved breaks VPN with split-horizon DNS

[Anders Kaseorg]

Public bug reported:

I use a VPN configured with network-manager-openconnect-gnome in which a
split-horizon DNS setup assigns different addresses to some names inside
the remote network than the addresses seen for those names from outside
the remote network.  However, systemd-resolved often decides to ignore
the VPN’s DNS servers and use the local network’s DNS servers to resolve
names (whether in the remote domain or not), breaking the split-horizon
DNS.

This related bug, reported by Lennart Poettering himself, was closed with the 
current Fedora release at the time reaching EOL:
https://bugzilla.redhat.com/show_bug.cgi?id=1151544

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

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

Title:
  systemd-resolved breaks VPN with split-horizon DNS

Status in systemd package in Ubuntu:
  New

Bug description:
  I use a VPN configured with network-manager-openconnect-gnome in which
  a split-horizon DNS setup assigns different addresses to some names
  inside the remote network than the addresses seen for those names from
  outside the remote network.  However, systemd-resolved often decides
  to ignore the VPN’s DNS servers and use the local network’s DNS
  servers to resolve names (whether in the remote domain or not),
  breaking the split-horizon DNS.

  This related bug, reported by Lennart Poettering himself, was closed with the 
current Fedora release at the time reaching EOL:
  https://bugzilla.redhat.com/show_bug.cgi?id=1151544

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

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

[Touch-packages] [Bug 1624071] Re: libnss-resolve: Fallback from resolve to dns breaks DNSSEC validation

[Anders Kaseorg]

Filed https://github.com/systemd/systemd/issues/4157 upstream for the
NOTFOUND vs. UNAVAIL problem.

** Bug watch added: github.com/systemd/systemd/issues #4157
   https://github.com/systemd/systemd/issues/4157

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

Title:
  libnss-resolve: Fallback from resolve to dns breaks DNSSEC validation

Status in systemd package in Ubuntu:
  Triaged

Bug description:
  The libnss-resolve postinst script inserts ‘resolve’ before ‘dns’ in
  the hosts line of /etc/nsswitch.conf.  This makes DNSSEC validation
  impossible, even with DNSSEC=yes in /etc/systemd/resolved.conf,
  because if libnss_resolve returns a validation failure, glibc will
  simply fall back to libnss_dns.  It also makes NXDOMAIN lookups twice
  as slow.

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

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

[Touch-packages] [Bug 1624071] Re: libnss-resolve: Fallback from resolve to dns breaks DNSSEC validation

[Anders Kaseorg]

** Description changed:

  The libnss-resolve postinst script inserts ‘resolve’ before ‘dns’ in the
  hosts line of /etc/nsswitch.conf.  This makes DNSSEC validation
  impossible, even with DNSSEC=yes in /etc/systemd/resolved.conf, because
  if libnss_resolve returns a validation failure, glibc will simply fall
  back to libnss_dns.  It also makes NXDOMAIN lookups twice as slow.
- 
- The following syntax would preserve the fallback in the case that
- systemd-resolved is not running at all, but allow systemd-resolved to
- fail lookups that should fail when it is running:
- 
- hosts:  files resolve [!TRYAGAIN=return] dns

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

Title:
  libnss-resolve: Fallback from resolve to dns breaks DNSSEC validation

Status in systemd package in Ubuntu:
  Triaged

Bug description:
  The libnss-resolve postinst script inserts ‘resolve’ before ‘dns’ in
  the hosts line of /etc/nsswitch.conf.  This makes DNSSEC validation
  impossible, even with DNSSEC=yes in /etc/systemd/resolved.conf,
  because if libnss_resolve returns a validation failure, glibc will
  simply fall back to libnss_dns.  It also makes NXDOMAIN lookups twice
  as slow.

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

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

[Touch-packages] [Bug 1624071] Re: libnss-resolve: Fallback from resolve to dns breaks DNSSEC validation

[Anders Kaseorg]

You’re right: glibc seems to treat the absence of libnss-resolve itself
as UNAVAIL, which is the same code returned on DNSSEC validation
failures when libnss-resolve is working.  I don’t see a way around this
other than patching libnss-resolve to return NOTFOUND (or TRYAGAIN?) on
validation failure.

It looks like there may be other ways for an active attacker to force a
TRYAGAIN code (with a response that doesn’t fit in the caller-provided
buffer), which suggests that the right configuration is
[!UNAVAIL=return], not merely [NOTFOUND=return].

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

Title:
  libnss-resolve: Fallback from resolve to dns breaks DNSSEC validation

Status in systemd package in Ubuntu:
  Triaged

Bug description:
  The libnss-resolve postinst script inserts ‘resolve’ before ‘dns’ in
  the hosts line of /etc/nsswitch.conf.  This makes DNSSEC validation
  impossible, even with DNSSEC=yes in /etc/systemd/resolved.conf,
  because if libnss_resolve returns a validation failure, glibc will
  simply fall back to libnss_dns.  It also makes NXDOMAIN lookups twice
  as slow.

  The following syntax would preserve the fallback in the case that
  systemd-resolved is not running at all, but allow systemd-resolved to
  fail lookups that should fail when it is running:

  hosts:  files resolve [!TRYAGAIN=return] dns

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

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

[Touch-packages] [Bug 1624071] Re: libnss-resolve: Fallback from resolve to dns breaks DNSSEC validation

[Anders Kaseorg]

I also worry that, by masking systemd-resolved failures, this fallback
has meant that systemd-resolved is not really getting adequate testing.
If there were widespread problems causing systemd-resolved lookups to
fail, would anyone have noticed?

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

Title:
  libnss-resolve: Fallback from resolve to dns breaks DNSSEC validation

Status in systemd package in Ubuntu:
  New

Bug description:
  The libnss-resolve postinst script inserts ‘resolve’ before ‘dns’ in
  the hosts line of /etc/nsswitch.conf.  This makes DNSSEC validation
  impossible, even with DNSSEC=yes in /etc/systemd/resolved.conf,
  because if libnss_resolve returns a validation failure, glibc will
  simply fall back to libnss_dns.  It also makes NXDOMAIN lookups twice
  as slow.

  The following syntax would preserve the fallback in the case that
  systemd-resolved is not running at all, but allow systemd-resolved to
  fail lookups that should fail when it is running:

  hosts:  files resolve [!TRYAGAIN=return] dns

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

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

[Touch-packages] [Bug 1624071] [NEW] libnss-resolve: Fallback from resolve to dns breaks DNSSEC validation

[Anders Kaseorg]

Public bug reported:

The libnss-resolve postinst script inserts ‘resolve’ before ‘dns’ in the
hosts line of /etc/nsswitch.conf.  This makes DNSSEC validation
impossible, even with DNSSEC=yes in /etc/systemd/resolved.conf, because
if libnss_resolve returns a validation failure, glibc will simply fall
back to libnss_dns.  It also makes NXDOMAIN lookups twice as slow.

The following syntax would preserve the fallback in the case that
systemd-resolved is not running at all, but allow systemd-resolved to
fail lookups that should fail when it is running:

hosts:  files resolve [!TRYAGAIN=return] dns

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

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

Title:
  libnss-resolve: Fallback from resolve to dns breaks DNSSEC validation

Status in systemd package in Ubuntu:
  New

Bug description:
  The libnss-resolve postinst script inserts ‘resolve’ before ‘dns’ in
  the hosts line of /etc/nsswitch.conf.  This makes DNSSEC validation
  impossible, even with DNSSEC=yes in /etc/systemd/resolved.conf,
  because if libnss_resolve returns a validation failure, glibc will
  simply fall back to libnss_dns.  It also makes NXDOMAIN lookups twice
  as slow.

  The following syntax would preserve the fallback in the case that
  systemd-resolved is not running at all, but allow systemd-resolved to
  fail lookups that should fail when it is running:

  hosts:  files resolve [!TRYAGAIN=return] dns

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

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

[Touch-packages] [Bug 520546] Re: Alt-f2 switches to virtual terminal 2

[Anders Kaseorg]

I’m running Ubuntu Gnome 16.04.

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

Title:
  Alt-f2 switches to virtual terminal 2

Status in console-cyrillic package in Ubuntu:
  Confirmed
Status in console-setup package in Ubuntu:
  Confirmed

Bug description:
  I'm running Ubuntu Lucid development branch.

  Pressing alt-f2 switches the screen to the second virtual terminal.
  Alt-f3 does the same to the third and so on. I expected alt-f2 to open
  the run dialog.

  I'm pretty sure that my keyboard is not malfunctioning as I can use
  all my applications normally. (Pressing O and Ctrl-O do not have the
  same effect.)

  I'm not sure which package I should file this bug against. I'll
  happily do an apport-collect once I know.

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

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

[Touch-packages] [Bug 520546] Re: Alt-f2 switches to virtual terminal 2

[Anders Kaseorg]

When console-setup is configured, it runs ‘setupcon --force’, which
breaks the running X server in exactly this way.

** Also affects: console-setup (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Alt-f2 switches to virtual terminal 2

Status in console-cyrillic package in Ubuntu:
  Confirmed
Status in console-setup package in Ubuntu:
  Confirmed

Bug description:
  I'm running Ubuntu Lucid development branch.

  Pressing alt-f2 switches the screen to the second virtual terminal.
  Alt-f3 does the same to the third and so on. I expected alt-f2 to open
  the run dialog.

  I'm pretty sure that my keyboard is not malfunctioning as I can use
  all my applications normally. (Pressing O and Ctrl-O do not have the
  same effect.)

  I'm not sure which package I should file this bug against. I'll
  happily do an apport-collect once I know.

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

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

[Touch-packages] [Bug 520546] Re: Alt-f2 switches to virtual terminal 2

[Anders Kaseorg]

This might have something to with the default setting
ACTIVE_CONSOLES="/dev/tty[1-6]" in /etc/default/console-setup
conflicting with the recent move of X from console 7 to console 2.

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

Title:
  Alt-f2 switches to virtual terminal 2

Status in console-cyrillic package in Ubuntu:
  Confirmed
Status in console-setup package in Ubuntu:
  Confirmed

Bug description:
  I'm running Ubuntu Lucid development branch.

  Pressing alt-f2 switches the screen to the second virtual terminal.
  Alt-f3 does the same to the third and so on. I expected alt-f2 to open
  the run dialog.

  I'm pretty sure that my keyboard is not malfunctioning as I can use
  all my applications normally. (Pressing O and Ctrl-O do not have the
  same effect.)

  I'm not sure which package I should file this bug against. I'll
  happily do an apport-collect once I know.

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

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

[Touch-packages] [Bug 1537635] Re: Reduce zlib compression level for massive performance increase

[Anders Kaseorg]

Level 5 isn’t crazy, though it’s still some 70% slower than level 1.

zlib.compressobj(level=1) time=7.6 size=84869397
zlib.compressobj(level=2) time=7.8 size=82465461
zlib.compressobj(level=3) time=8.4 size=79576183
zlib.compressobj(level=4) time=12.2 size=74672475
zlib.compressobj(level=5) time=13.2 size=72642875
zlib.compressobj(level=6) time=15.7 size=69988031
zlib.compressobj(level=7) time=17.9 size=69281853
zlib.compressobj(level=8) time=30.4 size=68666299
zlib.compressobj(level=9) time=59.0 size=68326007

bz2.BZ2Compressor(compresslevel=1) time=30.6 size=61319073
bz2.BZ2Compressor(compresslevel=9) time=40.0 size=54246781

lz4.compress time=2.4 size=108683033

Sizes are after base64 encoding.

(If you’re worried about upload size, why not recompress the report at
upload time, when it’s not going to take the user by surprise?)

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

Title:
  Reduce zlib compression level for massive performance increase

Status in Apport:
  New
Status in apport package in Ubuntu:
  Confirmed

Bug description:
  When apport takes a core dump of a large application, it uses 100% CPU
  for a _long_ time (often 30 seconds or more) to compress the core
  dump. The system is virtually unusable during this time, especially if
  the application was the window manager and won’t be restarted until
  the core dump is complete.

  This is a longstanding known problem; it motivated the switch from
  bzip2 to zlib level 9 back in apport 0.24. That made it much better,
  but it’s still quite bad. So why not switch from zlib level 9 to zlib
  level 1?

  I tested this on a core dump of gnome-shell, and while it increased
  the size of the .crash file by 24% (68.5 MB to 85.0 MB), it decreased
  the needed CPU time by a FACTOR OF EIGHT (58.6 seconds to 7.3
  seconds). This tradeoff seems more than worthwhile for this use case.

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

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

[Touch-packages] [Bug 1537635] [NEW] Reduce zlib compression level for massive performance increase

[Anders Kaseorg]

Public bug reported:

When apport takes a core dump of a large application, it uses 100% CPU
for a _long_ time (often 30 seconds or more) to compress the core dump.
The system is virtually unusable during this time, especially if the
application was the window manager and won’t be restarted until the core
dump is complete.

This is a longstanding known problem; it motivated the switch from bzip2
to zlib level 9 back in apport 0.24. That made it much better, but it’s
still quite bad. So why not switch from zlib level 9 to zlib level 1?

I tested this on a core dump of gnome-shell, and while it increased the
size of the .crash file by 24% (68.5 MB to 85.0 MB), it decreased the
needed CPU time by a FACTOR OF EIGHT (58.6 seconds to 7.3 seconds). This
tradeoff seems more than worthwhile for this use case.

** Affects: apport
 Importance: Undecided
 Status: New

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


** Tags: patch

** Patch added: "apport_2.19.3-0ubuntu3_zlib-level-1.debdiff"
   
https://bugs.launchpad.net/bugs/1537635/+attachment/4556055/+files/apport_2.19.3-0ubuntu3_zlib-level-1.debdiff

** Tags added: patch

** Also affects: apport
   Importance: Undecided
   Status: New

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

Title:
  Reduce zlib compression level for massive performance increase

Status in Apport:
  New
Status in apport package in Ubuntu:
  New

Bug description:
  When apport takes a core dump of a large application, it uses 100% CPU
  for a _long_ time (often 30 seconds or more) to compress the core
  dump. The system is virtually unusable during this time, especially if
  the application was the window manager and won’t be restarted until
  the core dump is complete.

  This is a longstanding known problem; it motivated the switch from
  bzip2 to zlib level 9 back in apport 0.24. That made it much better,
  but it’s still quite bad. So why not switch from zlib level 9 to zlib
  level 1?

  I tested this on a core dump of gnome-shell, and while it increased
  the size of the .crash file by 24% (68.5 MB to 85.0 MB), it decreased
  the needed CPU time by a FACTOR OF EIGHT (58.6 seconds to 7.3
  seconds). This tradeoff seems more than worthwhile for this use case.

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

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

[Touch-packages] [Bug 1512209] Re: update-manager crashed with SyntaxError in find_cookie(): invalid or missing encoding declaration for '/usr/bin/sys'

[Anders Kaseorg]

This is a combination of two problems. One is that starting update-
manager results in these warnings:

/usr/bin/update-manager:28: PyGIWarning: Gtk was imported without specifying a 
version first. Use gi.require_version('Gtk', '3.0') before import to ensure 
that the right version gets loaded.
  from gi.repository import Gtk
/usr/lib/python3/dist-packages/UpdateManager/UpdateManager.py:26: PyGIWarning: 
GdkX11 was imported without specifying a version first. Use 
gi.require_version('GdkX11', '3.0') before import to ensure that the right 
version gets loaded.
  from gi.repository import Gdk, GdkX11
/usr/lib/python3/dist-packages/UpdateManager/UnitySupport.py:29: PyGIWarning: 
Dbusmenu was imported without specifying a version first. Use 
gi.require_version('Dbusmenu', '0.4') before import to ensure that the right 
version gets loaded.
  from gi.repository import Dbusmenu, Unity
/usr/lib/python3/dist-packages/UpdateManager/UnitySupport.py:29: PyGIWarning: 
Unity was imported without specifying a version first. Use 
gi.require_version('Unity', '7.0') before import to ensure that the right 
version gets loaded.
  from gi.repository import Dbusmenu, Unity

The other is that when openafs-client is installed, the presence of
/usr/bin/sys causes Python to crash while displaying these warnings (see
linked bugs).

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

Title:
  update-manager crashed with SyntaxError in find_cookie(): invalid or
  missing encoding declaration for '/usr/bin/sys'

Status in pygobject:
  Fix Released
Status in Python:
  Won't Fix
Status in pygobject package in Ubuntu:
  New
Status in update-manager package in Ubuntu:
  New

Bug description:
  update-manager crashed with SyntaxError in find_cookie(): invalid or
  missing encoding declaration for '/usr/bin/sys'

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: update-manager 1:15.10.3
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.19.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME-Classic:GNOME
  Date: Sun Nov  1 22:34:22 2015
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/update-manager
  GsettingsChanges:
   b'com.ubuntu.update-manager' b'show-details' b'true'
   b'com.ubuntu.update-manager' b'window-height' b'813'
   b'com.ubuntu.update-manager' b'first-run' b'false'
   b'com.ubuntu.update-manager' b'window-width' b'500'
   b'com.ubuntu.update-manager' b'launch-time' b'1445601355'
  InstallationDate: Installed on 2015-06-02 (152 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  InterpreterPath: /usr/bin/python3.5
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/update-manager --no-update 
--no-focus-on-map
  PythonArgs: ['/usr/bin/update-manager', '--no-update', '--no-focus-on-map']
  SourcePackage: update-manager
  Title: update-manager crashed with SyntaxError in find_cookie(): invalid or 
missing encoding declaration for '/usr/bin/sys'
  UpgradeStatus: Upgraded to xenial on 2015-10-28 (4 days ago)
  UserGroups: adm bumblebee cdrom dip libvirtd lpadmin plugdev sambashare 
sbuild sudo wireshark

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

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

[Touch-packages] [Bug 1512209] Re: update-manager crashed with SyntaxError in find_cookie(): invalid or missing encoding declaration for '/usr/bin/sys'

[Anders Kaseorg]

** Bug watch added: Python Roundup #25493
   http://bugs.python.org/issue25493

** Also affects: python via
   http://bugs.python.org/issue25493
   Importance: Unknown
   Status: Unknown

** Bug watch added: GNOME Bug Tracker #757184
   https://bugzilla.gnome.org/show_bug.cgi?id=757184

** Also affects: pygobject via
   https://bugzilla.gnome.org/show_bug.cgi?id=757184
   Importance: Unknown
   Status: Unknown

** Attachment removed: "CurrentDmesg.txt.txt"
   
https://bugs.launchpad.net/pygobject/+bug/1512209/+attachment/4510908/+files/CurrentDmesg.txt.txt

** Attachment removed: "JournalErrors.txt"
   
https://bugs.launchpad.net/pygobject/+bug/1512209/+attachment/4510912/+files/JournalErrors.txt

** Information type changed from Private to Public

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

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

Title:
  update-manager crashed with SyntaxError in find_cookie(): invalid or
  missing encoding declaration for '/usr/bin/sys'

Status in pygobject:
  Unknown
Status in Python:
  Unknown
Status in pygobject package in Ubuntu:
  New
Status in update-manager package in Ubuntu:
  New

Bug description:
  update-manager crashed with SyntaxError in find_cookie(): invalid or
  missing encoding declaration for '/usr/bin/sys'

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: update-manager 1:15.10.3
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.19.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME-Classic:GNOME
  Date: Sun Nov  1 22:34:22 2015
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/update-manager
  GsettingsChanges:
   b'com.ubuntu.update-manager' b'show-details' b'true'
   b'com.ubuntu.update-manager' b'window-height' b'813'
   b'com.ubuntu.update-manager' b'first-run' b'false'
   b'com.ubuntu.update-manager' b'window-width' b'500'
   b'com.ubuntu.update-manager' b'launch-time' b'1445601355'
  InstallationDate: Installed on 2015-06-02 (152 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  InterpreterPath: /usr/bin/python3.5
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/update-manager --no-update 
--no-focus-on-map
  PythonArgs: ['/usr/bin/update-manager', '--no-update', '--no-focus-on-map']
  SourcePackage: update-manager
  Title: update-manager crashed with SyntaxError in find_cookie(): invalid or 
missing encoding declaration for '/usr/bin/sys'
  UpgradeStatus: Upgraded to xenial on 2015-10-28 (4 days ago)
  UserGroups: adm bumblebee cdrom dip libvirtd lpadmin plugdev sambashare 
sbuild sudo wireshark

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

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

[Touch-packages] [Bug 1489050] Re: Option -servername not described in manpage

[Anders Kaseorg]

I did not write the fix, but you should be checking the 1.0.2 manpages,
not the 1.0.1 manpages.

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

Title:
  Option -servername not described in manpage

Status in openssl package in Ubuntu:
  Fix Released

Bug description:
  Documentation for eg option -servername is missing on the man page.

  Ubuntu 14.04.3 LTS / openssl 1.0.1f-1ubuntu2.15

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

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

[Touch-packages] [Bug 1489050] Re: Option -servername not described in manpage

[Anders Kaseorg]

Fixed in OpenSSL 1.0.2 in wily.

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

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

Title:
  Option -servername not described in manpage

Status in openssl package in Ubuntu:
  Fix Released

Bug description:
  Documentation for eg option -servername is missing on the man page.

  Ubuntu 14.04.3 LTS / openssl 1.0.1f-1ubuntu2.15

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

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

[Touch-packages] [Bug 1489207] [NEW] /usr/share/doc/openssl/changelog.gz is a broken symlink

[Anders Kaseorg]

Public bug reported:

$ zcat /usr/share/doc/openssl/changelog.gz
gzip: /usr/share/doc/openssl/changelog.gz: No such file or directory
$ ls -l /usr/share/doc/openssl/changelog.gz
lrwxrwxrwx 1 root root 27 Jul  9 10:06 /usr/share/doc/openssl/changelog.gz -> 
../libssl1.0.0/changelog.gz
$ ls -l /usr/share/doc/libssl1.0.0/changelog.gz
ls: cannot access /usr/share/doc/libssl1.0.0/changelog.gz: No such file or 
directory
$ dpkg -l openssl libssl1.0.0
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version ArchitectureDescription
+++--===-===-=
ii  libssl1.0.0:amd641.0.2d-0ubuntu1 amd64   Secure Sockets Layer 
toolkit - shared librari
ii  openssl  1.0.2d-0ubuntu1 amd64   Secure Sockets Layer 
toolkit - cryptographic

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

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

Title:
  /usr/share/doc/openssl/changelog.gz is a broken symlink

Status in openssl package in Ubuntu:
  New

Bug description:
  $ zcat /usr/share/doc/openssl/changelog.gz
  gzip: /usr/share/doc/openssl/changelog.gz: No such file or directory
  $ ls -l /usr/share/doc/openssl/changelog.gz
  lrwxrwxrwx 1 root root 27 Jul  9 10:06 /usr/share/doc/openssl/changelog.gz -> 
../libssl1.0.0/changelog.gz
  $ ls -l /usr/share/doc/libssl1.0.0/changelog.gz
  ls: cannot access /usr/share/doc/libssl1.0.0/changelog.gz: No such file or 
directory
  $ dpkg -l openssl libssl1.0.0
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name Version ArchitectureDescription
  
+++--===-===-=
  ii  libssl1.0.0:amd641.0.2d-0ubuntu1 amd64   Secure Sockets Layer 
toolkit - shared librari
  ii  openssl  1.0.2d-0ubuntu1 amd64   Secure Sockets Layer 
toolkit - cryptographic

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

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

[Touch-packages] [Bug 1483975] Re: update-initramfs complains about missing /sbin/fsck.btrfs

[Anders Kaseorg]

You might think that, but in fact the hook shipped with btrfs-tools only
copies in /bin/fsck.btrfs if /usr/share/initramfs-tools/hooks/fsck is
not executable. It is executable, so this has no effect.

I have checked on current wily with / on btrfs that my initramfs really
is missing fsck.btrfs (in either /bin or /sbin).

** Changed in: initramfs-tools (Ubuntu)
   Status: Invalid => New

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

Title:
  update-initramfs complains about missing /sbin/fsck.btrfs

Status in btrfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  New
Status in btrfs-tools package in Debian:
  New
Status in initramfs-tools package in Debian:
  New

Bug description:
  /sbin/fsck.btrfs moved to /bin/fsck.btrfs with btrfs-tools 4.0-2
  (http://bugs.debian.org/784234), which causes

  $ sudo update-initramfs -u
  update-initramfs: Generating /boot/initrd.img-4.1.0-3-generic
  Warning: /sbin/fsck.btrfs doesn't exist, can't install to initramfs, ignoring.

  I assume this means that fsck won’t run on a btrfs /, which seems bad.

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

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

[Touch-packages] [Bug 1482439] Re: wpa_supplicant crashed with SIGSEGV in get_iface_by_dbus_path()

[Anders Kaseorg]

** Information type changed from Private to Public

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

Title:
  wpa_supplicant crashed with SIGSEGV in get_iface_by_dbus_path()

Status in wpa package in Ubuntu:
  New

Bug description:
  wpa_supplicant crashed with SIGSEGV in dbus_connection_dispatch()

  ProblemType: Crash
  DistroRelease: Ubuntu 15.10
  Package: wpasupplicant 2.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.18-0ubuntu5
  Architecture: amd64
  Date: Wed Aug  5 00:08:21 2015
  ExecutablePath: /sbin/wpa_supplicant
  InstallationDate: Installed on 2015-06-02 (65 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  ProcCmdline: /sbin/wpa_supplicant -u -s -O /run/wpa_supplicant
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  SegvAnalysis:
   Segfault happened at: 0x7f8880818cba <__strcmp_sse2_unaligned+26>:   movdqu 
(%rdi),%xmm1
   PC (0x7f8880818cba) ok
   source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%xmm1" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: wpa
  StacktraceTop:
   ?? ()
   ?? ()
   ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
   dbus_connection_dispatch () from /lib/x86_64-linux-gnu/libdbus-1.so.3
   ?? ()
  Title: wpa_supplicant crashed with SIGSEGV in dbus_connection_dispatch()
  UpgradeStatus: Upgraded to wily on 2015-06-17 (50 days ago)
  UserGroups:

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

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

[Touch-packages] [Bug 1483975] [NEW] update-initramfs complains about missing /sbin/fsck.btrfs

[Anders Kaseorg]

Public bug reported:

/sbin/fsck.btrfs moved to /bin/fsck.btrfs with btrfs-tools 4.0-2
(http://bugs.debian.org/784234), which causes

$ sudo update-initramfs -u
update-initramfs: Generating /boot/initrd.img-4.1.0-3-generic
Warning: /sbin/fsck.btrfs doesn't exist, can't install to initramfs, ignoring.

I assume this means that fsck won’t run on a btrfs /, which seems bad.

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: btrfs-tools (Debian)
 Importance: Unknown
 Status: Unknown

** Affects: initramfs-tools (Debian)
 Importance: Unknown
 Status: Unknown

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

** Also affects: initramfs-tools (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784368
   Importance: Unknown
   Status: Unknown

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

** Also affects: btrfs-tools (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786893
   Importance: Unknown
   Status: Unknown

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

Title:
  update-initramfs complains about missing /sbin/fsck.btrfs

Status in initramfs-tools package in Ubuntu:
  New
Status in btrfs-tools package in Debian:
  Unknown
Status in initramfs-tools package in Debian:
  Unknown

Bug description:
  /sbin/fsck.btrfs moved to /bin/fsck.btrfs with btrfs-tools 4.0-2
  (http://bugs.debian.org/784234), which causes

  $ sudo update-initramfs -u
  update-initramfs: Generating /boot/initrd.img-4.1.0-3-generic
  Warning: /sbin/fsck.btrfs doesn't exist, can't install to initramfs, ignoring.

  I assume this means that fsck won’t run on a btrfs /, which seems bad.

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

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

[Touch-packages] [Bug 1468832] Re: lightdm sources .profile

[Anders Kaseorg]

Aha, I was confusing ~/.xsessionrc with ~/.xsession. ~/.xsessionrc is
sourced using /bin/sh. A default Ubuntu session does not invoke
~/.xsession at all. Creating one that works correctly with Unity or
GNOME or whatever, as well as configuring LightDM to invoke it it,
requires a very pointy hat.

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

Title:
  lightdm sources .profile

Status in lightdm package in Ubuntu:
  New

Bug description:
  It is a bug for any display manager to read .profile--you guys are
  absolutely killing me with this.  The user's .profile is to be read by
  the shell, on interactive shell (i.e. terminal) logins ONLY.  The man
  page for bash explains this in detail; it's also discussed in the dash
  man page.  The problem with display managers reading .profile is that
  it is the place where commands to set up your terminal (i.e. stty) go
  --this is the entire point of differentiating interactive shells from
  non-interactive shells, and it's the reason only interactive shells
  read .profile at all.  Currently, if you have any such commands in
  your .profile, lightdm barfs on them, delaying the login session and
  forcing you to click on a prompt.  This is extremely annoying (and
  wrong)!

  It would be satisfactory to make lightdm not display the errors, but
  that's the wrong solution.  There's already a decades-established
  method of getting X display managers to source your environment
  settings: the .xsession file.  It should be read by ALL display
  managers (or the session file that starts them).  If you have common
  environment settings you want set in all your shells, the correct way
  to handle this is:

  .bashrc:
  # set all common environment vars here
  ENV_VAR=foo
  ...

  .profile:
  # set up terminal
  stty erase
  # BASH already sources .bashrc by default on interactive sessions

  .xsession:
  if [ -f .bashrc ] source .bashrc

  If you're not using BASH, you can still use this method without
  changing anything, except in .profile you need to explicitly source
  the .bashrc file.  Of course you can change the name of the file that
  contains the common settings to reflect that your shell is not BASH;
  since the file is sourced by your other files explicitly, it does not
  matter what the user calls it.

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

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

[Touch-packages] [Bug 1468832] Re: lightdm sources .profile

[Anders Kaseorg]

No, you misunderstand my comment. It doesn’t matter whether or not your
shell is bash. ~/.xsession file is sourced using /bin/sh, not using your
shell. You cannot expect to be able to source ~/.bashrc from
~/.xsession, no matter what your preferred shell is.

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

Title:
  lightdm sources .profile

Status in lightdm package in Ubuntu:
  New

Bug description:
  It is a bug for any display manager to read .profile--you guys are
  absolutely killing me with this.  The user's .profile is to be read by
  the shell, on interactive shell (i.e. terminal) logins ONLY.  The man
  page for bash explains this in detail; it's also discussed in the dash
  man page.  The problem with display managers reading .profile is that
  it is the place where commands to set up your terminal (i.e. stty) go
  --this is the entire point of differentiating interactive shells from
  non-interactive shells, and it's the reason only interactive shells
  read .profile at all.  Currently, if you have any such commands in
  your .profile, lightdm barfs on them, delaying the login session and
  forcing you to click on a prompt.  This is extremely annoying (and
  wrong)!

  It would be satisfactory to make lightdm not display the errors, but
  that's the wrong solution.  There's already a decades-established
  method of getting X display managers to source your environment
  settings: the .xsession file.  It should be read by ALL display
  managers (or the session file that starts them).  If you have common
  environment settings you want set in all your shells, the correct way
  to handle this is:

  .bashrc:
  # set all common environment vars here
  ENV_VAR=foo
  ...

  .profile:
  # set up terminal
  stty erase
  # BASH already sources .bashrc by default on interactive sessions

  .xsession:
  if [ -f .bashrc ] source .bashrc

  If you're not using BASH, you can still use this method without
  changing anything, except in .profile you need to explicitly source
  the .bashrc file.  Of course you can change the name of the file that
  contains the common settings to reflect that your shell is not BASH;
  since the file is sourced by your other files explicitly, it does not
  matter what the user calls it.

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

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

[Touch-packages] [Bug 1468832] Re: lightdm sources .profile

[Anders Kaseorg]

.xsession is sourced within /bin/sh, not /bin/bash. It wouldn’t make
sense to source .bashrc from it (unless you happened to write a .bashrc
that doesn’t use any bash features).

Also, .bashrc is sourced by _every_ interactive shell, so if you were to add 
things to environment variables from .bashrc, e.g.
  PATH="$HOME/bin:$PATH"
then they would show up multiple times in shells launched inside shells. This 
is just an annoyance for $PATH, but it might be an important problem for other 
variables, so you would need to add code to test whether the variable had 
already been changed, etc.

This is why Ubuntu’s default .profile (see /etc/skel/.profile) sets up
$PATH and the default .bashrc (see /etc/skel/.bashrc) does not.

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

Title:
  lightdm sources .profile

Status in lightdm package in Ubuntu:
  New

Bug description:
  It is a bug for any display manager to read .profile--you guys are
  absolutely killing me with this.  The user's .profile is to be read by
  the shell, on interactive shell (i.e. terminal) logins ONLY.  The man
  page for bash explains this in detail; it's also discussed in the dash
  man page.  The problem with display managers reading .profile is that
  it is the place where commands to set up your terminal (i.e. stty) go
  --this is the entire point of differentiating interactive shells from
  non-interactive shells, and it's the reason only interactive shells
  read .profile at all.  Currently, if you have any such commands in
  your .profile, lightdm barfs on them, delaying the login session and
  forcing you to click on a prompt.  This is extremely annoying (and
  wrong)!

  It would be satisfactory to make lightdm not display the errors, but
  that's the wrong solution.  There's already a decades-established
  method of getting X display managers to source your environment
  settings: the .xsession file.  It should be read by ALL display
  managers (or the session file that starts them).  If you have common
  environment settings you want set in all your shells, the correct way
  to handle this is:

  .bashrc:
  # set all common environment vars here
  ENV_VAR=foo
  ...

  .profile:
  # set up terminal
  stty erase
  # BASH already sources .bashrc by default on interactive sessions

  .xsession:
  if [ -f .bashrc ] source .bashrc

  If you're not using BASH, you can still use this method without
  changing anything, except in .profile you need to explicitly source
  the .bashrc file.  Of course you can change the name of the file that
  contains the common settings to reflect that your shell is not BASH;
  since the file is sourced by your other files explicitly, it does not
  matter what the user calls it.

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

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

[Touch-packages] [Bug 1452099] Re: unshare -r is broken

[Anders Kaseorg]

** Patch added: "Fix by merging util-linux 2.25.2-6 from Debian"
   
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1452099/+attachment/4391896/+files/util-linux_2.25.2-4ubuntu2_lp1452099.debdiff

** Tags added: patch patch-accepted-debian

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

Title:
  unshare -r is broken

Status in util-linux package in Ubuntu:
  New
Status in util-linux package in Debian:
  Unknown

Bug description:
  After CVE-2014-8989 was fixed in Linux v3.19-rc1~41, ‘unshare -r’ no
  longer works.

  $ unshare -Ur
  unshare: write failed /proc/self/gid_map: Operation not permitted
  $ sudo -i
  # unshare -r
  unshare: write failed /proc/self/gid_map: Operation not permitted

  This was fixed in Debian’s util-linux 2.25.2-6.

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

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

[Touch-packages] [Bug 1452099] [NEW] unshare -r is broken

[Anders Kaseorg]

Public bug reported:

After CVE-2014-8989 was fixed in Linux v3.19-rc1~41, ‘unshare -r’ no
longer works.

$ unshare -Ur
unshare: write failed /proc/self/gid_map: Operation not permitted
$ sudo -i
# unshare -r
unshare: write failed /proc/self/gid_map: Operation not permitted

This was fixed in Debian’s util-linux 2.25.2-6.

** Affects: util-linux (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: util-linux (Debian)
 Importance: Unknown
 Status: Unknown

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

** Also affects: util-linux (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780841
   Importance: Unknown
   Status: Unknown

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

Title:
  unshare -r is broken

Status in util-linux package in Ubuntu:
  New
Status in util-linux package in Debian:
  Unknown

Bug description:
  After CVE-2014-8989 was fixed in Linux v3.19-rc1~41, ‘unshare -r’ no
  longer works.

  $ unshare -Ur
  unshare: write failed /proc/self/gid_map: Operation not permitted
  $ sudo -i
  # unshare -r
  unshare: write failed /proc/self/gid_map: Operation not permitted

  This was fixed in Debian’s util-linux 2.25.2-6.

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

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

[Touch-packages] [Bug 1426588] Re: systemctl assert failure: *** Error in `systemctl': double free or corruption (fasttop): 0x00007fa04bf00910 ***

[Anders Kaseorg]

Sure, here it is.

** Attachment added: "vmware-USBArbitrator"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1426588/+attachment/4381963/+files/vmware-USBArbitrator

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

Title:
  systemctl assert failure: *** Error in `systemctl': double free or
  corruption (fasttop): 0x7fa04bf00910 ***

Status in systemd:
  Won't Fix
Status in systemd package in Ubuntu:
  Fix Committed

Bug description:
  root@file-control:~# systemctl disable vmware-USBArbitrator
  Synchronizing state for vmware-USBArbitrator.service with sysvinit using 
update-rc.d...
  Executing /usr/sbin/update-rc.d vmware-USBArbitrator defaults
  insserv: Service localfs has to be enabled to start service 
vmware-USBArbitrator
  insserv: exiting now!
  update-rc.d: error: insserv rejected the script header
  *** Error in `systemctl': double free or corruption (fasttop): 
0x7f4ad5bff910 ***
  Aborted (core dumped)

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-4ubuntu1
  Uname: Linux 4.0.0-04rc1-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  AssertionMessage: *** Error in `systemctl': double free or corruption 
(fasttop): 0x7fa04bf00910 ***
  Date: Fri Feb 27 18:12:48 2015
  ExecutablePath: /bin/systemctl
  InstallationDate: Installed on 2014-08-22 (189 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 
(20140730)
  MachineType: LENOVO 20349
  ProcCmdline: systemctl disable vmware-USBArbitrator
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.0.0-04rc1-generic 
root=/dev/mapper/fcntl-ubuntu ro rootflags=subvol=@ quiet splash 
init=/lib/systemd/systemd vt.handoff=7
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   __libc_message (do_abort=do_abort@entry=1, fmt=fmt@entry=0x7fa049a247a0 "*** 
Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175
   malloc_printerr (ptr=, str=0x7fa049a24968 "double free or 
corruption (fasttop)", action=1) at malloc.c:4996
   _int_free (av=, p=, have_lock=0) at 
malloc.c:3840
   ?? ()
   ?? ()
  Title: systemctl assert failure: *** Error in `systemctl': double free or 
corruption (fasttop): 0x7fa04bf00910 ***
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sbuild
  dmi.bios.date: 08/18/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9ECN31WW(V1.14)
  dmi.board.asset.tag: 31900058Std
  dmi.board.name: Lenovo Y50-70 Touch
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058Std
  dmi.chassis.asset.tag: 31900058Std
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Y50-70 Touch
  dmi.modalias: 
dmi:bvnLENOVO:bvr9ECN31WW(V1.14):bd08/18/2014:svnLENOVO:pn20349:pvrLenovoY50-70Touch:rvnLENOVO:rnLenovoY50-70Touch:rvr31900058Std:cvnLENOVO:ct10:cvrLenovoY50-70Touch:
  dmi.product.name: 20349
  dmi.product.version: Lenovo Y50-70 Touch
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 807303] Re: "bizarre error - file size is not what the server reported" with private ppa

[Anders Kaseorg]

I submitted a patch to https://bugs.debian.org/781509.

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

** Also affects: apt (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781509
   Importance: Unknown
   Status: Unknown

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

Title:
  "bizarre error - file size is not what the server reported" with
  private ppa

Status in Launchpad itself:
  Triaged
Status in apt package in Ubuntu:
  New
Status in apt package in Debian:
  Unknown

Bug description:
  My natty desktop machine has been happily subscribed to a private ppa
  for a long time.  When I updated it today (for the first time in a
  month) it showed this error:

  
  Fetched 262 MB in 3min 47s (1,150 kB/s)   
 
  Failed to fetch 
https://mbp:elided-passw...@private-ppa.launchpad.net/canonical-ux/walled-garden/ubuntu/pool/main/u/ubuntu-font-family-sources/ttf-ubuntu-font-family_0.71.2-0ubuntu5+phasedbeta3~natty_all.deb
 Size mismatch
  W: Bizarre Error - File size is not what the server reported 1728827 1712444
  E: Unable to fetch some archives, maybe run apt-get update or try with 
--fix-missing?

  It's possible this is some local error but it seems unlikely any
  network problem could interfere with a file served over https.

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

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