[Touch-packages] [Bug 1736705] Re: [19.10 FEAT] openssl: SIMD implementation of chacha20

2019-08-29 Thread Frank Heimes
** Changed in: ubuntu-z-systems
   Status: Triaged => 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/1736705

Title:
  [19.10 FEAT] openssl: SIMD implementation of chacha20

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in openssl package in Ubuntu:
  Fix Released

Bug description:
  Enable support for TLS 1.3 with  chacha20poly1305 cipher suites using SIMD 
instructions
  Planned for openssl 1.2

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

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


[Touch-packages] [Bug 1736704] Re: [19.10 FEAT] openssl: SIMD implementation of poly1305

2019-08-29 Thread Frank Heimes
** Changed in: ubuntu-z-systems
   Status: In Progress => 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/1736704

Title:
  [19.10 FEAT] openssl: SIMD implementation of poly1305

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in openssl package in Ubuntu:
  Fix Released

Bug description:
  Enable support for TLS 1.3 with  chacha20poly1305 cipher suites 
  using SIMD instructions
  Planned with openssl 1.2

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

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


[Touch-packages] [Bug 1834794] Re: Uses too much memory (6Gbyte process)

2019-08-29 Thread Launchpad Bug Tracker
[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

** Changed in: pulseaudio (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Uses too much memory (6Gbyte process)

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  So, my pulseaudio process is 6Gbyte large, 3.5Gb of that resident in
  memory.

  version: 1:11.1-1ubuntu7.2

  OS: Ubuntu 18.04.2 LTS

  System uptime: 11 days

  Desktop: GNOME

  pmap output:

  $ pmap 25499
  25499:   /usr/bin/pulseaudio --start --log-target=syslog
  55e3bb805000 84K r-x-- pulseaudio
  55e3bba1a000  4K r pulseaudio
  55e3bba1b000  4K rw--- pulseaudio
  55e3bd1b9000132K rw---   [ anon ]
  55e3bd1da000 3671036K rw---   [ anon ]
  7f705c00  65536K rw-s- memfd:pulseaudio (deleted)
  7f706000  65536K rw-s- memfd:pulseaudio (deleted)
  7f706400  65536K rw-s- memfd:pulseaudio (deleted)
  7f706800  65536K rw-s- memfd:pulseaudio (deleted)
  7f706c00  65536K rw-s- memfd:pulseaudio (deleted)
  7f707000  65536K rw-s- memfd:pulseaudio (deleted)
  7f707400  65536K rw-s- memfd:pulseaudio (deleted)
  7f707800  65536K rw-s- memfd:pulseaudio (deleted)
  7f707c00  65536K rw-s- memfd:pulseaudio (deleted)
  7f708000  65536K rw-s- memfd:pulseaudio (deleted)
  7f708400  65536K rw-s- memfd:pulseaudio (deleted)
  7f708800  65536K rw-s- memfd:pulseaudio (deleted)
  7f70bc00  65536K rw-s- memfd:pulseaudio (deleted)
  7f70c000  65536K rw-s- memfd:pulseaudio (deleted)
  7f70c400  65536K rw-s- memfd:pulseaudio (deleted)
  7f70c800  65536K rw-s- memfd:pulseaudio (deleted)
  7f70ec00  65536K rw-s- memfd:pulseaudio (deleted)
  7f70f000  65536K rw-s- memfd:pulseaudio (deleted)
  7f70f400  65536K rw-s- memfd:pulseaudio (deleted)
  7f70f800  65536K rw-s- memfd:pulseaudio (deleted)
  7f70fc00  65536K rw-s- memfd:pulseaudio (deleted)
  7f71  65536K rw-s- memfd:pulseaudio (deleted)
  7f710400  65536K rw-s- memfd:pulseaudio (deleted)
  7f710800  65536K rw-s- memfd:pulseaudio (deleted)
  7f710c00  65536K rw-s- memfd:pulseaudio (deleted)
  7f711000  65536K rw-s- memfd:pulseaudio (deleted)
  7f711400  65536K rw-s- memfd:pulseaudio (deleted)
  7f711800  65536K rw-s- memfd:pulseaudio (deleted)
  7f711c00172K rw---   [ anon ]
  7f711c02b000  65364K -   [ anon ]
  7f7120957000 24K r-x-- libuuid.so.1.3.0
  7f712095d000   2044K - libuuid.so.1.3.0
  7f7120b5c000  4K r libuuid.so.1.3.0
  7f7120b5d000  4K rw--- libuuid.so.1.3.0
  7f7120b5e000 28K r-x-- libSM.so.6.0.1
  7f7120b65000   2044K - libSM.so.6.0.1
  7f7120d64000  4K r libSM.so.6.0.1
  7f7120d65000  4K rw--- libSM.so.6.0.1
  7f7120d66000 92K r-x-- libICE.so.6.3.0
  7f7120d7d000   2044K - libICE.so.6.3.0
  7f7120f7c000  4K r libICE.so.6.3.0
  7f7120f7d000  4K rw--- libICE.so.6.3.0
  7f7120f7e000 12K rw---   [ anon ]
  7f7120f81000  8K r-x-- module-x11-xsmp.so
  7f7120f83000   2048K - module-x11-xsmp.so
  7f7121183000  4K r module-x11-xsmp.so
  7f7121184000  4K rw--- module-x11-xsmp.so
  7f7121185000 68K r-x-- libXext.so.6.4.0
  7f7121196000   2044K - libXext.so.6.4.0
  7f7121395000  4K r libXext.so.6.4.0
  7f7121396000  4K rw--- libXext.so.6.4.0
  7f7121397000 20K r-x-- libXtst.so.6.1.0
  7f712139c000   2044K - libXtst.so.6.1.0
  7f712159b000  4K r libXtst.so.6.1.0
  7f712159c000  4K rw--- libXtst.so.6.1.0
  7f712159d000  8K r-x-- module-x11-cork-request.so
  7f712159f000   2044K - module-x11-cork-request.so
  7f712179e000  4K r module-x11-cork-request.so
  7f712179f000  4K rw--- module-x11-cork-request.so
  7f71217a  8K r-x-- module-x11-bell.so
  7f71217a2000   2044K - module-x11-bell.so
  7f71219a1000  4K r module-x11-bell.so
  7f71219a2000  4K rw--- module-x11-bell.so
  7f71219a3000 12K r-x-- module-x11-publish.so
  7f71219a6000   2044K - module-x11-publish.so
  7f7121ba5000  4K r module-x11-publish.so
  7f7121ba6000  4K rw--- module-x11-publish.so
  7f7121ba7000  8K r-x-- libcli.so
  7f7121ba9000   2044K - libcli.so
  7f7121da8000  4K r libcli.so
  7f7121da9000  4K rw--- libcli.so
  7f7121daa000  8K r-x-- libprotocol-cli.so
  7f7121dac000   2044K - libprotocol-cli.so
  7f7121fab000  4K r libprotocol-cli.so
  7f7121fac000  4K rw--- 

[Touch-packages] [Bug 1736704] Re: [19.10 FEAT] openssl: SIMD implementation of poly1305

2019-08-29 Thread Launchpad Bug Tracker
This bug was fixed in the package openssl - 1.1.1c-1ubuntu4

---
openssl (1.1.1c-1ubuntu4) eoan; urgency=medium

  * Cherrypick s390x SIMD acceleration patches for poly1305 and chacha20
from master. LP: #1736705 LP: #1736704

 -- Dimitri John Ledkov   Tue, 20 Aug 2019 12:46:33
+0100

** Changed in: openssl (Ubuntu)
   Status: Incomplete => 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/1736704

Title:
  [19.10 FEAT] openssl: SIMD implementation of poly1305

Status in Ubuntu on IBM z Systems:
  In Progress
Status in openssl package in Ubuntu:
  Fix Released

Bug description:
  Enable support for TLS 1.3 with  chacha20poly1305 cipher suites 
  using SIMD instructions
  Planned with openssl 1.2

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

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


[Touch-packages] [Bug 1736705] Re: [19.10 FEAT] openssl: SIMD implementation of chacha20

2019-08-29 Thread Launchpad Bug Tracker
This bug was fixed in the package openssl - 1.1.1c-1ubuntu4

---
openssl (1.1.1c-1ubuntu4) eoan; urgency=medium

  * Cherrypick s390x SIMD acceleration patches for poly1305 and chacha20
from master. LP: #1736705 LP: #1736704

 -- Dimitri John Ledkov   Tue, 20 Aug 2019 12:46:33
+0100

** Changed in: openssl (Ubuntu)
   Status: Incomplete => 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/1736705

Title:
  [19.10 FEAT] openssl: SIMD implementation of chacha20

Status in Ubuntu on IBM z Systems:
  Triaged
Status in openssl package in Ubuntu:
  Fix Released

Bug description:
  Enable support for TLS 1.3 with  chacha20poly1305 cipher suites using SIMD 
instructions
  Planned for openssl 1.2

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

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


[Touch-packages] [Bug 1815172] Autopkgtest regression report (mesa/19.0.8-0ubuntu0~18.04.2)

2019-08-29 Thread Ubuntu SRU Bot
All autopkgtests for the newly accepted mesa (19.0.8-0ubuntu0~18.04.2) for 
bionic have finished running.
The following regressions have been reported in tests triggered by the package:

vtk6/unknown (armhf)
kf5-messagelib/4:17.12.3-0ubuntu3 (armhf)
firefox/68.0.2+build1-0ubuntu0.18.04.1 (armhf)
openjdk-8/8u222-b10-1ubuntu1~18.04.1 (i386, s390x, arm64, armhf, ppc64el, amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#mesa

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  [bionic] drm/i915: softpin broken, needs to be fixed for 32bit mesa

Status in Mesa:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Committed
Status in mesa source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Won't Fix
Status in mesa source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  Several schools reported black screens after normally updating their Ubuntu 
boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1.

  Downgrading mesa fixes the problem.

  lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD
  Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer
  Inc. HD Graphics 530 [1043:8694]Kernel modules: i915

  Unfortunately I can't find a lot of useful information, here are some bits:
   * systemctl --failed says "gpu-manager" and "lightdm" have failed
   * Xorg.log is clean: https://termbin.com/6l2b
   * dmesg too: https://termbin.com/ip4e
   * It happens on lightdm/MATE, I don't know about Ubuntu GNOME.
   * If one runs `xinit` from ssh, it fails with:
  i965: Failed to submit batchbuffer: Invalid argument

  This is caused by mesa assuming that soft-pinning on GEN8+ is working
  since kernel 4.5, but in fact this issue wasn't fixed until 4.19.3. So
  a proper fix would be to backport commits from 4.19.3/4.20 to fix GTT
  sizes/pin flags, but that's left for future.

  [Test case]
  install fixed mesa or kernel, check that the regression is fixed

  [Regression potential]
  mesa: shouldn't be any, it just reverts the change to always soft-pin
  (TODO kernel: adds commits from upstream stable, which have been well tested 
upstream by now)

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

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


[Touch-packages] [Bug 1841412] Autopkgtest regression report (mesa/19.0.8-0ubuntu0~18.04.2)

2019-08-29 Thread Ubuntu SRU Bot
All autopkgtests for the newly accepted mesa (19.0.8-0ubuntu0~18.04.2) for 
bionic have finished running.
The following regressions have been reported in tests triggered by the package:

vtk6/unknown (armhf)
kf5-messagelib/4:17.12.3-0ubuntu3 (armhf)
firefox/68.0.2+build1-0ubuntu0.18.04.1 (armhf)
openjdk-8/8u222-b10-1ubuntu1~18.04.1 (i386, s390x, arm64, armhf, ppc64el, amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#mesa

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Build with NDEBUG again

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

Bug description:
  [Impact]
  Mesa is now built with meson, and it turns out that meson < 0.47.0 (commit 
7c4736d27f4c5d7 to be exact) doesn't handle command line options properly which 
means that -Db_ndebug=true didn't have any effect when mesa is built on bionic. 
This means that some asserts are enabled, and at least nouveau is affected.

  [Test case]
  chech the build log that -DNDEBUG is passed

  [Regression potential]
  none really, it just adds a build flag which should've been there

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

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


[Touch-packages] [Bug 1841790] Re: [FFe] Please accept systemd 241 to Eoan

2019-08-29 Thread Łukasz Zemczak
Ok, the bileto systemd package seems to look sane, although it's a
really hard thing to review. The tests not being green seems reassuring
I'd say. I somewhat agree that having both 242 and 243 rc in already
-proposed at one point does seem like a plus, but on the other side
their removal means there were unsuspected regressions. That being said,
I am willing to take the risk so early after Feature Freeze.

Let's make sure to check if the regressions we saw with 243 and 242
aren't visible here (if those weren't visible via autopkgtests of
course). Anyway, +1 on the FFe. Please upload as soon as possible.

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

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

Title:
  [FFe] Please accept systemd 241 to Eoan

Status in systemd package in Ubuntu:
  Triaged

Bug description:
  Eoan currently has 240-6ubuntu13, but it is not used widely, Debian stable 
already has 241 and Debian testing moved to 242 last week.
  Version 241 is the safest choice for Eoan (from v240, v241 and v242) since it 
is widely tested, while going forward 20.04 will most likely ship a systemd 
release which is not released yet, probably v244+.

  Updating to v241 will allow us to carry fewer patches in Eoan and
  makes moving to the next release easier.

  The proposed package is tested in Bileto and all tests are passing:
  https://bileto.ubuntu.com/#/ticket/3789

  The final version will be 241-7ubuntu1 and I'm tidying up the
  changelog, too.

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

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


[Touch-packages] [Bug 1637800] Re: add a motd script for news

2019-08-29 Thread Brian Murray
I also noticed this when installing the package:

Setting up base-files (9.4ubuntu4.10) ...
motd-news.service is a disabled or a static unit, not starting it.
motd-news.timer is a disabled or a static unit, not starting it.

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

Title:
  add a motd script for news

Status in base-files package in Ubuntu:
  Fix Released
Status in base-files source package in Xenial:
  Fix Committed

Bug description:
  Add a new update-motd script for printing news and/or important
  notices.

  == SRU ==

  [IMPACT]
  We should add important security messages or other news to the MOTD.

  [TEST CASE]
  Login to the system and ensure that the "news" section of the motd is 
displayed.  Note that you might need to force trigger an update by running 
'sudo update-motd'.

  [REGRESSION POTENTIAL]
  No reasonable regression potential.  The script simply prints 2 lines of text 
to the MOTD.

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

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


[Touch-packages] [Bug 1740894] Re: KEY_RFKILL is not passed to userspace

2019-08-29 Thread Brian Murray
** Tags removed: rls-bb-incoming

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

Title:
  KEY_RFKILL is not passed to userspace

Status in OEM Priority Project:
  Fix Released
Status in OEM Priority Project bionic series:
  Fix Released
Status in libxkbcommon package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in xkeyboard-config package in Ubuntu:
  Fix Released
Status in xorgproto package in Ubuntu:
  Fix Released
Status in libxkbcommon source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Fix Committed
Status in xkeyboard-config source package in Bionic:
  Fix Committed
Status in xorgproto source package in Bionic:
  Fix Released
Status in libxkbcommon source package in Cosmic:
  Fix Released
Status in xkeyboard-config source package in Cosmic:
  Fix Released
Status in xorgproto source package in Cosmic:
  Fix Released

Bug description:
  * Impact
  the airplane mode key doesn't work in GNOME

  * Test case
  Use a laptop with a key to activate airplane mode, it should toggle the 
corresponding mode on/off when used

  * Regression potential
  The change adds a new key definition but doesn't touch any existing one, 
nothing specific to test out of the new key working

  -

  There are a couple things going on, that could be fixed by a Debian or
  Ubuntu maintainer:

  - libxkbdcommon needs to be updated from 0.7.1 to 0.7.2. This
  introduces the RFKill key: https://lists.freedesktop.org/archives
  /wayland-devel/2017-August/034721.html

  - x11-proto needs a new release. This commit added RFKill, but it is
  not in a release:
  
https://cgit.freedesktop.org/xorg/proto/xproto/commit/?id=98a32d328e7195e12c38baa877917335bceffbaf

  - Likely other X11 packages need to be rebuilt.

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

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


[Touch-packages] [Bug 1841953] Re: Bionic ⋅ SuperTuxKart ⋅ Flickering shadows ⋅ Haswell i915

2019-08-29 Thread Coeur Noir
** Also affects: xserver-xorg-video-intel
   Importance: Undecided
   Status: New

** Package changed: mesa (Ubuntu) => mesa

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

Title:
  Bionic ⋅ SuperTuxKart ⋅ Flickering shadows ⋅ Haswell i915

Status in Mesa:
  New
Status in xf86-video-intel:
  New

Bug description:
  Hi,

  for few weeks now, I've noticed a big change in graphic performance
  while playing famous SuperTuxKart on ubuntu bionic :

  shadows are flickering, all over the screen, it's a big pain for eyes
  ( and wonder what would happen for epileptic people ).

  My computer is :
  Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz with 16Go ram and Haswell integrated 
graphics.
  coeur-noir@asgard:~$ lspci -k | grep -A 2 -i "VGA"
  00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen 
Core Processor Integrated Graphics Controller (rev 06)
Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller
Kernel driver in use: i915
  coeur-noir@asgard:~$ sudo lshw -c video
*-display 
 description: VGA compatible controller
 produit: Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller
 fabriquant: Intel Corporation
 identifiant matériel: 2
 information bus: pci@:00:02.0
 version: 06
 bits: 64 bits
 horloge: 33MHz
 fonctionnalités: msi pm vga_controller bus_master cap_list rom
 configuration: driver=i915 latency=0
 ressources: irq:26 mémoire:f780-f7bf mémoire:e000-efff 
portE/S:f000(taille=64) mémoire:c-d
  coeur-noir@asgard:~$

  My Ubuntu Budgie 18.04 is :
  coeur-noir@asgard:~$ lsb_release -rd
  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04
  coeur-noir@asgard:~$ uname -a
  Linux asgard 5.0.0-23-generic #24~18.04.1-Ubuntu SMP Mon Jul 29 16:12:28 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux
  coeur-noir@asgard:~$ 

  mesa packages are :
  coeur-noir@asgard:~$ dpkg -l | grep mesa
  ii  libegl-mesa0:amd64  19.0.8-0ubuntu0~18.04.1   
amd64free implementation of the EGL API -- Mesa vendor 
library
  ii  libegl1-mesa:amd64  19.0.8-0ubuntu0~18.04.1   
amd64transitional dummy package
  ii  libgl1-mesa-dri:amd64   19.0.8-0ubuntu0~18.04.1   
amd64free implementation of the OpenGL API -- DRI modules
  ii  libgl1-mesa-dri:i38619.0.8-0ubuntu0~18.04.1   
i386 free implementation of the OpenGL API -- DRI modules
  ii  libgl1-mesa-glx:amd64   19.0.8-0ubuntu0~18.04.1   
amd64transitional dummy package
  ii  libgl1-mesa-glx:i38619.0.8-0ubuntu0~18.04.1   
i386 transitional dummy package
  ii  libglapi-mesa:amd64 19.0.8-0ubuntu0~18.04.1   
amd64free implementation of the GL API -- shared library
  ii  libglapi-mesa:i386  19.0.8-0ubuntu0~18.04.1   
i386 free implementation of the GL API -- shared library
  ii  libgles2-mesa:amd64 19.0.8-0ubuntu0~18.04.1   
amd64transitional dummy package
  ii  libglu1-mesa:amd64  9.0.0-2.1build1   
amd64Mesa OpenGL utility library (GLU)
  ii  libglu1-mesa:i386   9.0.0-2.1build1   
i386 Mesa OpenGL utility library (GLU)
  ii  libglx-mesa0:amd64  19.0.8-0ubuntu0~18.04.1   
amd64free implementation of the OpenGL API -- GLX vendor 
library
  ii  libglx-mesa0:i386   19.0.8-0ubuntu0~18.04.1   
i386 free implementation of the OpenGL API -- GLX vendor 
library
  ii  libosmesa6:amd6419.0.8-0ubuntu0~18.04.1   
amd64Mesa Off-screen rendering extension
  ii  libosmesa6:i386 19.0.8-0ubuntu0~18.04.1   
i386 Mesa Off-screen rendering extension
  ii  libwayland-egl1-mesa:amd64  19.0.8-0ubuntu0~18.04.1   
amd64transitional dummy package
  ii  mesa-utils  8.4.0-1   
amd64Miscellaneous Mesa GL utilities
  ii  mesa-utils-extra8.4.0-1   
amd64Miscellaneous Mesa utilies (opengles, egl)
  ii  mesa-va-drivers:amd64   19.0.8-0ubuntu0~18.04.1   
amd64Mesa VA-API video acceleration drivers
  ii  

[Touch-packages] [Bug 1841953] [NEW] Bionic ⋅ SuperTuxKart ⋅ Flickering shadows ⋅ Haswell i915

2019-08-29 Thread Coeur Noir
Public bug reported:

Hi,

for few weeks now, I've noticed a big change in graphic performance
while playing famous SuperTuxKart on ubuntu bionic :

shadows are flickering, all over the screen, it's a big pain for eyes (
and wonder what would happen for epileptic people ).

My computer is :
Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz with 16Go ram and Haswell integrated 
graphics.
coeur-noir@asgard:~$ lspci -k | grep -A 2 -i "VGA"
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen 
Core Processor Integrated Graphics Controller (rev 06)
Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller
Kernel driver in use: i915
coeur-noir@asgard:~$ sudo lshw -c video
  *-display 
   description: VGA compatible controller
   produit: Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller
   fabriquant: Intel Corporation
   identifiant matériel: 2
   information bus: pci@:00:02.0
   version: 06
   bits: 64 bits
   horloge: 33MHz
   fonctionnalités: msi pm vga_controller bus_master cap_list rom
   configuration: driver=i915 latency=0
   ressources: irq:26 mémoire:f780-f7bf mémoire:e000-efff 
portE/S:f000(taille=64) mémoire:c-d
coeur-noir@asgard:~$

My Ubuntu Budgie 18.04 is :
coeur-noir@asgard:~$ lsb_release -rd
Description:Ubuntu 18.04.3 LTS
Release:18.04
coeur-noir@asgard:~$ uname -a
Linux asgard 5.0.0-23-generic #24~18.04.1-Ubuntu SMP Mon Jul 29 16:12:28 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux
coeur-noir@asgard:~$ 

mesa packages are :
coeur-noir@asgard:~$ dpkg -l | grep mesa
ii  libegl-mesa0:amd64  19.0.8-0ubuntu0~18.04.1 
  amd64free implementation of the EGL API -- Mesa vendor library
ii  libegl1-mesa:amd64  19.0.8-0ubuntu0~18.04.1 
  amd64transitional dummy package
ii  libgl1-mesa-dri:amd64   19.0.8-0ubuntu0~18.04.1 
  amd64free implementation of the OpenGL API -- DRI modules
ii  libgl1-mesa-dri:i38619.0.8-0ubuntu0~18.04.1 
  i386 free implementation of the OpenGL API -- DRI modules
ii  libgl1-mesa-glx:amd64   19.0.8-0ubuntu0~18.04.1 
  amd64transitional dummy package
ii  libgl1-mesa-glx:i38619.0.8-0ubuntu0~18.04.1 
  i386 transitional dummy package
ii  libglapi-mesa:amd64 19.0.8-0ubuntu0~18.04.1 
  amd64free implementation of the GL API -- shared library
ii  libglapi-mesa:i386  19.0.8-0ubuntu0~18.04.1 
  i386 free implementation of the GL API -- shared library
ii  libgles2-mesa:amd64 19.0.8-0ubuntu0~18.04.1 
  amd64transitional dummy package
ii  libglu1-mesa:amd64  9.0.0-2.1build1 
  amd64Mesa OpenGL utility library (GLU)
ii  libglu1-mesa:i386   9.0.0-2.1build1 
  i386 Mesa OpenGL utility library (GLU)
ii  libglx-mesa0:amd64  19.0.8-0ubuntu0~18.04.1 
  amd64free implementation of the OpenGL API -- GLX vendor 
library
ii  libglx-mesa0:i386   19.0.8-0ubuntu0~18.04.1 
  i386 free implementation of the OpenGL API -- GLX vendor 
library
ii  libosmesa6:amd6419.0.8-0ubuntu0~18.04.1 
  amd64Mesa Off-screen rendering extension
ii  libosmesa6:i386 19.0.8-0ubuntu0~18.04.1 
  i386 Mesa Off-screen rendering extension
ii  libwayland-egl1-mesa:amd64  19.0.8-0ubuntu0~18.04.1 
  amd64transitional dummy package
ii  mesa-utils  8.4.0-1 
  amd64Miscellaneous Mesa GL utilities
ii  mesa-utils-extra8.4.0-1 
  amd64Miscellaneous Mesa utilies (opengles, egl)
ii  mesa-va-drivers:amd64   19.0.8-0ubuntu0~18.04.1 
  amd64Mesa VA-API video acceleration drivers
ii  mesa-vdpau-drivers:amd6419.0.8-0ubuntu0~18.04.1 
  amd64Mesa VDPAU video acceleration drivers
coeur-noir@asgard:~$ 

SuperTuxKart version is :
coeur-noir@asgard:~$ dpkg -l | grep supertu
ii  supertuxkart1.0~ubuntu18.04.1   
  amd643D kart racing game
ii  supertuxkart-data   1.0~ubuntu18.04.1   
  all  3D kart racing game (data)
coeur-noir@asgard:~$ 

IMPORTANT NOTE #1 : I don't have 

[Touch-packages] [Bug 1841790] Re: [FFe] Please accept systemd 241 to Eoan

2019-08-29 Thread Balint Reczey
@xnox I asked @vorlon on #ubuntu-release yesterday and he said he could not 
give a proper review which I consider as an answer implying that I don't get an 
easy free pass.
I think the upload is as well tested by Bileto as reasonably can be and a safe 
upload but I don't want to break the freeze without approval.

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

Title:
  [FFe] Please accept systemd 241 to Eoan

Status in systemd package in Ubuntu:
  New

Bug description:
  Eoan currently has 240-6ubuntu13, but it is not used widely, Debian stable 
already has 241 and Debian testing moved to 242 last week.
  Version 241 is the safest choice for Eoan (from v240, v241 and v242) since it 
is widely tested, while going forward 20.04 will most likely ship a systemd 
release which is not released yet, probably v244+.

  Updating to v241 will allow us to carry fewer patches in Eoan and
  makes moving to the next release easier.

  The proposed package is tested in Bileto and all tests are passing:
  https://bileto.ubuntu.com/#/ticket/3789

  The final version will be 241-7ubuntu1 and I'm tidying up the
  changelog, too.

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

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


[Touch-packages] [Bug 1589289] Autopkgtest regression report (util-linux/2.27.1-6ubuntu3.8)

2019-08-29 Thread Ubuntu SRU Bot
All autopkgtests for the newly accepted util-linux (2.27.1-6ubuntu3.8) for 
xenial have finished running.
The following regressions have been reported in tests triggered by the package:

chromium-browser/76.0.3809.100-0ubuntu0.16.04.1 (i386, amd64, arm64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/xenial/update_excuses.html#util-linux

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  fstrim: cannot open /dev/.lxd-mounts: Permission denied

Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Xenial:
  Fix Committed
Status in util-linux source package in Bionic:
  Fix Committed
Status in util-linux source package in Disco:
  Fix Committed
Status in util-linux package in Debian:
  Unknown

Bug description:
  [Impact]
  fstrim weekly cronjob output in an unprivileged LXD container:

  /etc/cron.weekly/fstrim:
  fstrim: cannot open /dev/.lxd-mounts: Permission denied
  fstrim: /dev/fuse: not a directory
  fstrim: /dev/lxd: FITRIM ioctl failed: Operation not permitted

  There is a github issue:

  https://github.com/lxc/lxd/issues/2030

  The outcome is that it's purely an fstrim misbehaviour, it could be
  smarter.

  Stephane Graber comment:

  As all of this is handled by the kernel, there isn't anything we can
  do about it in LXD.

  I think fstrim should be made slightly more clever:

  * Don't run on bind-mounts (you can detect bind-mounts by parsing 
/proc/self/mountinfo instead of /proc/mounts)
  * Maybe not be as noisy on expected errors like EACCES, EPERM and ENOENT, 
only log actual failures which would likely be EINVAL or memory related errors.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: util-linux 2.27.1-6ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sun Jun  5 19:49:04 2016
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: util-linux
  UpgradeStatus: No upgrade log present (probably fresh install)

  [Test Case]
  * Ubuntu lxd container
  * Wait for the scheduled fstrim run (X: cronjob, B and late: systemd timer)
  * fstrim will run and report errors "Operation not permitted" "Permission 
denied", ...

  Container shouldn't run fstrim, it should only be run at host level.

  [Potential Regression]

  None, the change will only block fstrim to be automatically run at
  scheduled time. One can still run fstrim on a container manually, even
  if there is no purpose of doing that.

  Xenial uses the cronjob approach /etc/cron.weekly/fstrim
  Bionic and late switched to a systemd timer.

  2 differents fixes (one for X, and one for B and late) will be needed,
  but they'll do same thing, which prevent fstrim to automatically run
  if inside a container both fixes using systemd-virt-detect.

  [Other Informations]

  * The systemd timer change upstream PR:
  https://github.com/karelzak/util-linux/pull/841
  
https://github.com/karelzak/util-linux/commit/0280d31a2bd6292acd9a4b86d0f6b5feb275a618

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

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


[Touch-packages] [Bug 1589289] Autopkgtest regression report (util-linux/2.33.1-0.1ubuntu3)

2019-08-29 Thread Ubuntu SRU Bot
All autopkgtests for the newly accepted util-linux (2.33.1-0.1ubuntu3) for 
disco have finished running.
The following regressions have been reported in tests triggered by the package:

systemd/240-6ubuntu5.3 (amd64, ppc64el)
openjdk-8/8u222-b10-1ubuntu1~19.04.1 (armhf, arm64, amd64, s390x, i386, ppc64el)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/disco/update_excuses.html#util-linux

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  fstrim: cannot open /dev/.lxd-mounts: Permission denied

Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Xenial:
  Fix Committed
Status in util-linux source package in Bionic:
  Fix Committed
Status in util-linux source package in Disco:
  Fix Committed
Status in util-linux package in Debian:
  Unknown

Bug description:
  [Impact]
  fstrim weekly cronjob output in an unprivileged LXD container:

  /etc/cron.weekly/fstrim:
  fstrim: cannot open /dev/.lxd-mounts: Permission denied
  fstrim: /dev/fuse: not a directory
  fstrim: /dev/lxd: FITRIM ioctl failed: Operation not permitted

  There is a github issue:

  https://github.com/lxc/lxd/issues/2030

  The outcome is that it's purely an fstrim misbehaviour, it could be
  smarter.

  Stephane Graber comment:

  As all of this is handled by the kernel, there isn't anything we can
  do about it in LXD.

  I think fstrim should be made slightly more clever:

  * Don't run on bind-mounts (you can detect bind-mounts by parsing 
/proc/self/mountinfo instead of /proc/mounts)
  * Maybe not be as noisy on expected errors like EACCES, EPERM and ENOENT, 
only log actual failures which would likely be EINVAL or memory related errors.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: util-linux 2.27.1-6ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sun Jun  5 19:49:04 2016
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: util-linux
  UpgradeStatus: No upgrade log present (probably fresh install)

  [Test Case]
  * Ubuntu lxd container
  * Wait for the scheduled fstrim run (X: cronjob, B and late: systemd timer)
  * fstrim will run and report errors "Operation not permitted" "Permission 
denied", ...

  Container shouldn't run fstrim, it should only be run at host level.

  [Potential Regression]

  None, the change will only block fstrim to be automatically run at
  scheduled time. One can still run fstrim on a container manually, even
  if there is no purpose of doing that.

  Xenial uses the cronjob approach /etc/cron.weekly/fstrim
  Bionic and late switched to a systemd timer.

  2 differents fixes (one for X, and one for B and late) will be needed,
  but they'll do same thing, which prevent fstrim to automatically run
  if inside a container both fixes using systemd-virt-detect.

  [Other Informations]

  * The systemd timer change upstream PR:
  https://github.com/karelzak/util-linux/pull/841
  
https://github.com/karelzak/util-linux/commit/0280d31a2bd6292acd9a4b86d0f6b5feb275a618

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

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


[Touch-packages] [Bug 1837700] Autopkgtest regression report (systemd/240-6ubuntu5.4)

2019-08-29 Thread Ubuntu SRU Bot
All autopkgtests for the newly accepted systemd (240-6ubuntu5.4) for disco have 
finished running.
The following regressions have been reported in tests triggered by the package:

ndctl/unknown (armhf)
tinyssh/unknown (armhf)
munin/2.0.47-1ubuntu3 (armhf)
polkit-qt-1/0.112.0-6 (armhf)
gvfs/1.40.1-1ubuntu0.1 (amd64, i386)
systemd/240-6ubuntu5.4 (amd64, s390x, i386, ppc64el)
php7.2/7.2.19-0ubuntu0.19.04.2 (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/disco/update_excuses.html#systemd

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Dell system takes a long time to connect network with external dock

Status in HWE Next:
  New
Status in OEM Priority Project:
  In Progress
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Disco:
  Fix Committed
Status in systemd source package in Eoan:
  Fix Released

Bug description:
  update for SRU process:

  [Impact]
  1. On system featured mac passthrough, e.g., Dell/Lenovo laptop, or system 
occasionally install two USB ethernet with same MAC address, the system will 
suffer 90 seconds for network interface renaming mechanism before the last USB 
ethernet interface to activate.

  [Test Case]
  1. Install ubuntu on Dell laptop.
  2. Connect the Dell laptop with two Realtek 8153 USB ethernet dongle. Users 
can observe the last one will take 90 seconds for renaming to rename0.
  3. Users can also find that the two USB ethernet have the same MAC address.

  [Regression Potential] 
  To resolve the issue, drop a debian patch from systemd package. The debian 
patch is to revert an upstream commit to support 
75-persistent-net-generator.rules udev rule. Since the udev rule is deprecated, 
the regression potential should be relatively low.

  ---

  
  Dell has a feature called MAC addrss passthrough[1] that would force usb 
ethernet adapters to be assigned with a predefined MAC address stored in BIOS 
or so. This feature has been landed to mainline kernel in driver r8152[2]. So 
whenever a r8152 managed device is plugged into Dell devices with MAC addrss 
passthrough enabled, this driver will set NIC MAC to a predefined one.

  And some Dell devices have already one built-in r8152 NIC port. On
  these devices, when a second r8152 NIC is plugged in, a Debian
  originated udev rules file 73-usb-net-by-mac.rules[3] will invoke udev
  built-in command `net_id` to give a persistent name, and that will be
  based on MAC address. However, since the system has already
  initialized the built-in r8152 NIC with that name, renaming the second
  interface with this name will always fail.

  While Debian still carries a patch called "Revert-udev-network-device-
  renaming-immediately-give.patch"[4] that tries to keep support of
  already deprecated "75-persistent-net-generator.rules" based interface
  renaming mechanism, this patch also propagated into Ubuntu[5]. This
  patch will retry renaming with a 90 seconds timeout when the error
  code is -EEXIST, so the uevent processing will always be blocked in
  the last ifrename step in the victim system.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: udev 237-3ubuntu10.24 [modified: lib/udev/rules.d/50-firmware.rules 
lib/udev/rules.d/50-udev-default.rules 
lib/udev/rules.d/73-special-net-names.rules 
lib/udev/rules.d/73-usb-net-by-mac.rules]
  ProcVersionSignature: Ubuntu 4.15.0-1043.48-oem 4.15.18
  Uname: Linux 4.15.0-1043-oem x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  CustomUdevRuleFiles: 70-snap.core.rules 95-oem-hotkey-osd.rules
  Date: Wed Jul 24 15:30:59 2019
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+beaver-jorah+X90
  InstallationDate: Installed on 2019-07-03 (20 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Dell Inc. Latitude 7424 Rugged Extreme
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1043-oem.efi.signed 
root=UUID=5da90c85-3500-49a2-b989-71a604f9eec4 ro mem_sleep_default=deep quiet 
splash systemd.log_level=debug udev.log-priority=debug log_buf_len=8M 
vt.handoff=1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/27/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  

[Touch-packages] [Bug 1841790] Re: [FFe] Please accept systemd 241 to Eoan

2019-08-29 Thread Dimitri John Ledkov
For a long time we had v243 rc in proposed, however we have identified
that it has too many regressions. And whilst regressions are getting
fixed upstream, we decided to pull it and start doing slightly more
incremental updates to systemd and jump to v243 final in stages.

Imho this shouldn't require FFe cause we did have v243 in -proposed, and
are still trying to get there in stages.

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

Title:
  [FFe] Please accept systemd 241 to Eoan

Status in systemd package in Ubuntu:
  New

Bug description:
  Eoan currently has 240-6ubuntu13, but it is not used widely, Debian stable 
already has 241 and Debian testing moved to 242 last week.
  Version 241 is the safest choice for Eoan (from v240, v241 and v242) since it 
is widely tested, while going forward 20.04 will most likely ship a systemd 
release which is not released yet, probably v244+.

  Updating to v241 will allow us to carry fewer patches in Eoan and
  makes moving to the next release easier.

  The proposed package is tested in Bileto and all tests are passing:
  https://bileto.ubuntu.com/#/ticket/3789

  The final version will be 241-7ubuntu1 and I'm tidying up the
  changelog, too.

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

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


[Touch-packages] [Bug 1589289] Autopkgtest regression report (util-linux/2.31.1-0.4ubuntu3.4)

2019-08-29 Thread Ubuntu SRU Bot
All autopkgtests for the newly accepted util-linux (2.31.1-0.4ubuntu3.4) for 
bionic have finished running.
The following regressions have been reported in tests triggered by the package:

network-manager/1.10.6-2ubuntu1.1 (arm64)
openjdk-8/8u222-b10-1ubuntu1~18.04.1 (arm64, ppc64el, armhf, i386, amd64, s390x)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#util-linux

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  fstrim: cannot open /dev/.lxd-mounts: Permission denied

Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Xenial:
  Fix Committed
Status in util-linux source package in Bionic:
  Fix Committed
Status in util-linux source package in Disco:
  Fix Committed
Status in util-linux package in Debian:
  Unknown

Bug description:
  [Impact]
  fstrim weekly cronjob output in an unprivileged LXD container:

  /etc/cron.weekly/fstrim:
  fstrim: cannot open /dev/.lxd-mounts: Permission denied
  fstrim: /dev/fuse: not a directory
  fstrim: /dev/lxd: FITRIM ioctl failed: Operation not permitted

  There is a github issue:

  https://github.com/lxc/lxd/issues/2030

  The outcome is that it's purely an fstrim misbehaviour, it could be
  smarter.

  Stephane Graber comment:

  As all of this is handled by the kernel, there isn't anything we can
  do about it in LXD.

  I think fstrim should be made slightly more clever:

  * Don't run on bind-mounts (you can detect bind-mounts by parsing 
/proc/self/mountinfo instead of /proc/mounts)
  * Maybe not be as noisy on expected errors like EACCES, EPERM and ENOENT, 
only log actual failures which would likely be EINVAL or memory related errors.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: util-linux 2.27.1-6ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sun Jun  5 19:49:04 2016
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: util-linux
  UpgradeStatus: No upgrade log present (probably fresh install)

  [Test Case]
  * Ubuntu lxd container
  * Wait for the scheduled fstrim run (X: cronjob, B and late: systemd timer)
  * fstrim will run and report errors "Operation not permitted" "Permission 
denied", ...

  Container shouldn't run fstrim, it should only be run at host level.

  [Potential Regression]

  None, the change will only block fstrim to be automatically run at
  scheduled time. One can still run fstrim on a container manually, even
  if there is no purpose of doing that.

  Xenial uses the cronjob approach /etc/cron.weekly/fstrim
  Bionic and late switched to a systemd timer.

  2 differents fixes (one for X, and one for B and late) will be needed,
  but they'll do same thing, which prevent fstrim to automatically run
  if inside a container both fixes using systemd-virt-detect.

  [Other Informations]

  * The systemd timer change upstream PR:
  https://github.com/karelzak/util-linux/pull/841
  
https://github.com/karelzak/util-linux/commit/0280d31a2bd6292acd9a4b86d0f6b5feb275a618

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

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


[Touch-packages] [Bug 1740894] Autopkgtest regression report (systemd/237-3ubuntu10.26)

2019-08-29 Thread Ubuntu SRU Bot
All autopkgtests for the newly accepted systemd (237-3ubuntu10.26) for bionic 
have finished running.
The following regressions have been reported in tests triggered by the package:

network-manager/1.10.6-2ubuntu1.1 (arm64)
dovecot/1:2.2.33.2-1ubuntu4.3 (armhf)
systemd/237-3ubuntu10.26 (ppc64el)
gvfs/1.36.1-0ubuntu1.3.3 (ppc64el, i386)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#systemd

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  KEY_RFKILL is not passed to userspace

Status in OEM Priority Project:
  Fix Released
Status in OEM Priority Project bionic series:
  Fix Released
Status in libxkbcommon package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in xkeyboard-config package in Ubuntu:
  Fix Released
Status in xorgproto package in Ubuntu:
  Fix Released
Status in libxkbcommon source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Fix Committed
Status in xkeyboard-config source package in Bionic:
  Fix Committed
Status in xorgproto source package in Bionic:
  Fix Released
Status in libxkbcommon source package in Cosmic:
  Fix Released
Status in xkeyboard-config source package in Cosmic:
  Fix Released
Status in xorgproto source package in Cosmic:
  Fix Released

Bug description:
  * Impact
  the airplane mode key doesn't work in GNOME

  * Test case
  Use a laptop with a key to activate airplane mode, it should toggle the 
corresponding mode on/off when used

  * Regression potential
  The change adds a new key definition but doesn't touch any existing one, 
nothing specific to test out of the new key working

  -

  There are a couple things going on, that could be fixed by a Debian or
  Ubuntu maintainer:

  - libxkbdcommon needs to be updated from 0.7.1 to 0.7.2. This
  introduces the RFKill key: https://lists.freedesktop.org/archives
  /wayland-devel/2017-August/034721.html

  - x11-proto needs a new release. This commit added RFKill, but it is
  not in a release:
  
https://cgit.freedesktop.org/xorg/proto/xproto/commit/?id=98a32d328e7195e12c38baa877917335bceffbaf

  - Likely other X11 packages need to be rebuilt.

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

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


[Touch-packages] [Bug 1830629] Autopkgtest regression report (libarchive/3.2.2-3.1ubuntu0.4)

2019-08-29 Thread Ubuntu SRU Bot
All autopkgtests for the newly accepted libarchive (3.2.2-3.1ubuntu0.4) for 
bionic have finished running.
The following regressions have been reported in tests triggered by the package:

gvfs/1.36.1-0ubuntu1.3.3 (ppc64el)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#libarchive

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Errors when extracting ZIP files. It can not differentiate between
  files and directories

Status in libarchive package in Ubuntu:
  Fix Released
Status in libarchive source package in Bionic:
  Fix Committed

Bug description:
  * Impact
  The bionic version has a known problem when reading file entries in ZIP 
files, where it incorrectly identifies directories and files entries.

  * Test case
  $ wget 
https://bugs.launchpad.net/ubuntu/+source/libarchive/+bug/1830629/+attachment/5268728/+files/example.zip
  $ bsdtar -vxf example.zip
  $ ls -l

  The 'ABCD_1234' and 'empty' entries should be directories

  * Regression potential
  Check that extracting zips from bsdtar or nautilus work without issue

  

  It has been confirmed that the previous and following versions
  (3.3.1+) do not have this problem and the library handles the ZIP
  files correctly.

  Is it possible to include a newer version of libarchive (3.3.1+) in
  Bionic?

  This problem is seriously affecting some of our systems.

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

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


[Touch-packages] [Bug 1813581] Autopkgtest regression report (gpgme1.0/1.10.0-1ubuntu2.1)

2019-08-29 Thread Ubuntu SRU Bot
All autopkgtests for the newly accepted gpgme1.0 (1.10.0-1ubuntu2.1) for bionic 
have finished running.
The following regressions have been reported in tests triggered by the package:

libreoffice/1:6.0.7-0ubuntu0.18.04.8 (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#gpgme1.0

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  gpgme1.0 ftbfs in 18.04 LTS

Status in gpgme1.0 package in Ubuntu:
  Won't Fix
Status in gpgme1.0 source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  according to
  
http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html

  gpgme1.0 ftbfs.

  * Start testing of TofuInfoTest *
  Config: Using QtTest library 5.9.5, Qt 5.9.5 (x86_64-little_endian-lp64 
shared (dynamic) release build; by GCC 7.3.0)
  PASS   : TofuInfoTest::initTestCase()
  PASS   : TofuInfoTest::testTofuNull()
  PASS   : TofuInfoTest::testTofuInfo()
  PASS   : TofuInfoTest::testTofuSignCount()
  PASS   : TofuInfoTest::testTofuKeyList()
  PASS   : TofuInfoTest::testTofuPolicy()
  FAIL!  : TofuInfoTest::testTofuConflict() 'sig.validity() == 
Signature::Marginal' returned FALSE. ()
     Loc: [t-tofuinfo.cpp(458)]
  PASS   : TofuInfoTest::cleanupTestCase()
  Totals: 7 passed, 1 failed, 0 skipped, 0 blacklisted, 2386ms
  * Finished testing of TofuInfoTest *
  FAIL: t-tofuinfo

  [Test case]
  build it

  [Regression potential]
  This only changes the test suite run during build, and that one currently 
fails, so it can't cause any regression.

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

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


[Touch-packages] [Bug 1837700] Autopkgtest regression report (systemd/237-3ubuntu10.26)

2019-08-29 Thread Ubuntu SRU Bot
All autopkgtests for the newly accepted systemd (237-3ubuntu10.26) for bionic 
have finished running.
The following regressions have been reported in tests triggered by the package:

network-manager/1.10.6-2ubuntu1.1 (arm64)
dovecot/1:2.2.33.2-1ubuntu4.3 (armhf)
systemd/237-3ubuntu10.26 (ppc64el)
gvfs/1.36.1-0ubuntu1.3.3 (ppc64el, i386)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#systemd

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Dell system takes a long time to connect network with external dock

Status in HWE Next:
  New
Status in OEM Priority Project:
  In Progress
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Disco:
  Fix Committed
Status in systemd source package in Eoan:
  Fix Released

Bug description:
  update for SRU process:

  [Impact]
  1. On system featured mac passthrough, e.g., Dell/Lenovo laptop, or system 
occasionally install two USB ethernet with same MAC address, the system will 
suffer 90 seconds for network interface renaming mechanism before the last USB 
ethernet interface to activate.

  [Test Case]
  1. Install ubuntu on Dell laptop.
  2. Connect the Dell laptop with two Realtek 8153 USB ethernet dongle. Users 
can observe the last one will take 90 seconds for renaming to rename0.
  3. Users can also find that the two USB ethernet have the same MAC address.

  [Regression Potential] 
  To resolve the issue, drop a debian patch from systemd package. The debian 
patch is to revert an upstream commit to support 
75-persistent-net-generator.rules udev rule. Since the udev rule is deprecated, 
the regression potential should be relatively low.

  ---

  
  Dell has a feature called MAC addrss passthrough[1] that would force usb 
ethernet adapters to be assigned with a predefined MAC address stored in BIOS 
or so. This feature has been landed to mainline kernel in driver r8152[2]. So 
whenever a r8152 managed device is plugged into Dell devices with MAC addrss 
passthrough enabled, this driver will set NIC MAC to a predefined one.

  And some Dell devices have already one built-in r8152 NIC port. On
  these devices, when a second r8152 NIC is plugged in, a Debian
  originated udev rules file 73-usb-net-by-mac.rules[3] will invoke udev
  built-in command `net_id` to give a persistent name, and that will be
  based on MAC address. However, since the system has already
  initialized the built-in r8152 NIC with that name, renaming the second
  interface with this name will always fail.

  While Debian still carries a patch called "Revert-udev-network-device-
  renaming-immediately-give.patch"[4] that tries to keep support of
  already deprecated "75-persistent-net-generator.rules" based interface
  renaming mechanism, this patch also propagated into Ubuntu[5]. This
  patch will retry renaming with a 90 seconds timeout when the error
  code is -EEXIST, so the uevent processing will always be blocked in
  the last ifrename step in the victim system.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: udev 237-3ubuntu10.24 [modified: lib/udev/rules.d/50-firmware.rules 
lib/udev/rules.d/50-udev-default.rules 
lib/udev/rules.d/73-special-net-names.rules 
lib/udev/rules.d/73-usb-net-by-mac.rules]
  ProcVersionSignature: Ubuntu 4.15.0-1043.48-oem 4.15.18
  Uname: Linux 4.15.0-1043-oem x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  CustomUdevRuleFiles: 70-snap.core.rules 95-oem-hotkey-osd.rules
  Date: Wed Jul 24 15:30:59 2019
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+beaver-jorah+X90
  InstallationDate: Installed on 2019-07-03 (20 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Dell Inc. Latitude 7424 Rugged Extreme
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1043-oem.efi.signed 
root=UUID=5da90c85-3500-49a2-b989-71a604f9eec4 ro mem_sleep_default=deep quiet 
splash systemd.log_level=debug udev.log-priority=debug log_buf_len=8M 
vt.handoff=1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/27/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0Y7FK3
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X03
  

[Touch-packages] [Bug 1817537] Autopkgtest regression report (libsoup2.4/2.62.1-1ubuntu0.3)

2019-08-29 Thread Ubuntu SRU Bot
All autopkgtests for the newly accepted libsoup2.4 (2.62.1-1ubuntu0.3) for 
bionic have finished running.
The following regressions have been reported in tests triggered by the package:

gvfs/1.36.1-0ubuntu1.3.3 (ppc64el)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#libsoup2.4

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  libsoup should support ntlmv2

Status in libsoup2.4 package in Ubuntu:
  Fix Released
Status in libsoup2.4 source package in Bionic:
  Fix Committed

Bug description:
  * Impact
  Without NTLMv2 support evolution-ews can't connect to some exchange servers

  * Test case
  Try connecting from evolution-ews to an exchange server which enforces NTLMV2

  * Regression potential
  The change adds extra cases in the ntlm handling support, it should impact 
existing feature but check out for any potential regression in libsoup user 
(check at least evolution and epiphany-browser).
  Note that the patch include additional code tests

  ---

  Our Exchange admins recently made NTLMv2 obligatory. Since then
  interaction with Exchange through Evolution isn't possible anymore.

  In newer versions of libsoup that has been implemented, see
  https://gitlab.gnome.org/GNOME/evolution-ews/issues/38

  Could that be backported to Ubuntu 18.04?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libsoup2.4-1 2.62.1-1ubuntu0.1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon Feb 25 12:10:26 2019
  SourcePackage: libsoup2.4
  UpgradeStatus: Upgraded to bionic on 2018-09-27 (150 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libsoup2.4/+bug/1817537/+subscriptions

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


[Touch-packages] [Bug 1837734] Autopkgtest regression report (nss/2:3.35-2ubuntu2.4)

2019-08-29 Thread Ubuntu SRU Bot
All autopkgtests for the newly accepted nss (2:3.35-2ubuntu2.4) for bionic have 
finished running.
The following regressions have been reported in tests triggered by the package:

openjdk-8/8u222-b10-1ubuntu1~18.04.1 (i386)
chrony/3.2-4ubuntu4.2 (arm64, ppc64el, armhf, i386, amd64, s390x)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#nss

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Firefox crash on a FIPS enabled machine due to libnss3

Status in nss package in Ubuntu:
  Fix Released
Status in nss source package in Xenial:
  Fix Committed
Status in nss source package in Bionic:
  Fix Committed
Status in nss source package in Disco:
  Fix Committed
Status in nss source package in Eoan:
  Fix Released

Bug description:
  [IMPACT]
  nss is not a FIPS certified library. On a machine running FIPS enabled 
kernel, the library by default goes into FIPS mode if 
/proc/sys/crypto/fips_enabled=1. This is an untested configuration and since 
libnss3 is not a certified library we propose disabling reading the 
'fips_enabled' flag and therefore switching the library automatically into FIPS 
mode. A FIPS customer reported firefox crash on a FIPS enabled system and 
strace showed it was repeatedly trying to read the fips_enabled flag from 
libnss3 before crashing.

  The proposed patch disables reading the /proc/sys/crypto/fips_enabled
  flag. The users of the library however can force nss into FIPS mode
  via an environment variable. We plan to leave it as is so as not to
  regress existing users who may be using it.

  The issue impacts libnss3 versions in eoan, disco, bionic and xenial.

  lsb_release -rd
  Description:  Ubuntu Eoan Ermine (development branch)
  Release: 19.10

  Version: 2:3.45-1ubuntu1

  lsb_release -rd
  Description: Ubuntu Disco Dingo
  Release: 19.04

  Version: 2:3.42-1ubuntu2

  lsb_release -rd
  Description:  Ubuntu Bionic Beaver
  Release:  18.04

  Version: 2:3.35-2ubuntu2.3

  lsb_release -rd
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  Version: 2:3.28.4-0ubuntu0.16.04

  [FIX]
  This fix proposes to disable libnss3 reading proc/sys/crypto/fips_enabled. We 
only want fips certified modules reading this file and running in fips mode. 
libnss3 is not one of our fips certified modules, so should not be reading this 
along with our fips certified modules to determine whether to run in fips mode.

  Users who do want to run the library in FIPS mode can do so by using
  the environment variable "NSS_FIPS". We propose to leave it as is so
  as not to regress anyone using this. The user who is using this option
  should be doing so with the awareness.

  [TEST]
  Tested on a xenial and bionic desktop ISO running FIPS enabled kernel and in 
FIPS mode. With the patch fix no crashes were observed when launching firefox 
browser.
  Without the patch fix, firefox crashes.

  Tested on a xenial and bionic desktop ISO running non-FIPS generic
  kernel. With the patch fix, firefox worked as expected and no changes
  were observed.

  [REGRESSION POTENTIAL]
  The regression potential for this is small. A FIPS kernel is required to
  create /proc/sys/crypto/fips_enabled and it is not available in standard 
ubuntu archive. For users forcing FIPS through environment variable, nothing 
has changed.

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

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


[Touch-packages] [Bug 1830796] Autopkgtest regression report (gdb/8.1-0ubuntu3.1)

2019-08-29 Thread Ubuntu SRU Bot
All autopkgtests for the newly accepted gdb (8.1-0ubuntu3.1) for bionic have 
finished running.
The following regressions have been reported in tests triggered by the package:

apport/2.20.9-0ubuntu7.7 (amd64)
python3.6/3.6.8-1~18.04.1 (amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#gdb

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  [Bionic][ARM64]Failure debugging linux kernel

Status in gdb package in Ubuntu:
  Fix Released
Status in gdb source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  GDB fails to debug ARM64 vmlinux debug image with proc/kcore information. For 
example it is unable to print values of variables like 'jiffies_64'.

  [Test]
  # gdb /usr/lib/debug/boot/vmlinux-4.18.0-20-generic  /proc/kcore
  [New process 1]
  Core was generated by `BOOT_IMAGE=/boot/vmlinuz-4.18.0-20-generic 
root=UUID=edb5e5a7-8272-4e13-aa25-37'.
  #0  0x in ?? ()
  (gdb) p jiffies_64
  Cannot access memory at address 0x09616980
  (gdb)

  [Fix]
  This issue was fixed upstream (git://sourceware.org/git/binutils-gdb.git) by 
the following patch:
  8727de56b0  Fix tagged pointer support

  [Regression Potential]
  The risk of regression after applying this patch could be to architectures 
other than ARM64 due to changes to gdb/util.c. Please see comment #2 where I 
have tested the PPA package on a ppc64el system and found it does not introduce 
any regressions.

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

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


[Touch-packages] [Bug 1841790] Re: [FFe] Please accept systemd 241 to Eoan

2019-08-29 Thread Francis Ginther
** Tags added: id-5d2e4c813a5b1a58c17d63f6

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

Title:
  [FFe] Please accept systemd 241 to Eoan

Status in systemd package in Ubuntu:
  New

Bug description:
  Eoan currently has 240-6ubuntu13, but it is not used widely, Debian stable 
already has 241 and Debian testing moved to 242 last week.
  Version 241 is the safest choice for Eoan (from v240, v241 and v242) since it 
is widely tested, while going forward 20.04 will most likely ship a systemd 
release which is not released yet, probably v244+.

  Updating to v241 will allow us to carry fewer patches in Eoan and
  makes moving to the next release easier.

  The proposed package is tested in Bileto and all tests are passing:
  https://bileto.ubuntu.com/#/ticket/3789

  The final version will be 241-7ubuntu1 and I'm tidying up the
  changelog, too.

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

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


[Touch-packages] [Bug 1668771] Re: [SRU] systemd-resolved negative caching for extended period of time

2019-08-29 Thread Eric Desrochers
There is discussion to push systemd 241 to Eoan:
https://launchpad.net/bugs/1841790

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

Title:
  [SRU] systemd-resolved negative caching for extended period of time

Status in systemd:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released
Status in systemd source package in Disco:
  Fix Released
Status in systemd source package in Eoan:
  Fix Released

Bug description:
  [Impact]

   * If a DNS lookup returns SERVFAIL, systemd-resolved seems to cache
  the result for very long (infinity?). I have to restart systemd-
  resolved to have the negative caching purged.

  * After SERVFAIL DNS server issue has been resolved, chromium/firefox
  still returns DNS error despite host can correctly resolve the name.

  [Test Case]

  * If a lookup returns SERVFAIL systemd-resolved will cache the result for 30s 
(See 201d995),
  however, there are several use cases on which this condition is not 
acceptable (See #5552 comments)
  and the only workaround would be to disable cache entirely or flush it , 
which isn't optimal.

  * Configure /etc/systemd/resolved.conf as follows:

  Cache=yes (default)

  * Restart systemd-resolved (systemctl restart systemd-
  resolved.service)

  * Run a host/getent command against a entry that will return SERVFAIL
  and check the journalctl output to see that the reply gets served from
  cache.

  root@systemd-disco:/home/ubuntu# host www.no-record.cl
  Host www.montemar.cl not found: 2(SERVFAIL)
  root@systemd-disco:/home/ubuntu# journalctl -u systemd-resolved -n
  -- Logs begin at Fri 2019-07-12 18:09:42 UTC, end at Tue 2019-07-23 15:10:17 
UTC. --
  Jul 23 15:10:10 systemd-disco systemd-resolved[1282]: Transaction 6222 for 
 on scope dns on ens3/* now complete with 
  Jul 23 15:10:10 systemd-disco systemd-resolved[1282]: Sending response packet 
with id 61042 on interface 1/AF_INET.
  Jul 23 15:10:10 systemd-disco systemd-resolved[1282]: Freeing transaction 
6222.
  Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: Got DNS stub UDP query 
packet for id 53580
  Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: Looking up RR for  
www.no-record.cl IN A.
  Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: RCODE SERVFAIL cache 
hit for  www.no-record.cl IN A
  Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: Transaction 58570 for < 
www.no-record.cl IN A> on scope dns on ens3/* now complete with  scope dns on ens3/.
  Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Using feature level UDP 
for transaction 22382.
  Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Sending query packet 
with id 22382.
  Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Processing incoming 
packet on transaction 22382 (rcode=SERVFAIL).
  Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Server returned error: 
SERVFAIL
  Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Not caching negative 
entry for: www.metaklass.org IN A, cache mode set to no-negative
  Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Transaction 22382 for 
 on scope dns on ens3/ now complete with from network 
(unsigned).
  Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Sending response packet 
with id 31060 on interface 1/AF_INET.

  The following patch https://github.com/systemd/systemd/pull/13047
  implements the required changes.

  [Other Info]

  Note that systemd in Eoan is being upgraded to upstream 242, so I am
  not adding this to Eoan now, as I don't want to disturb the merge. If
  needed after the merge, I'll add to Eoan.

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

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


[Touch-packages] [Bug 1841928] [NEW] systemd service file not triggering the bash script

2019-08-29 Thread Alan Kis
Public bug reported:

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04.6 LTS"

systemd:
  Installed: 229-4ubuntu21.21
  Candidate: 229-4ubuntu21.22
  Version table:
 229-4ubuntu21.22 500
500 http://eu-central-1.ec2.archive.ubuntu.com/ubuntu 
xenial-updates/main amd64 Packages
 *** 229-4ubuntu21.21 500
500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
100 /var/lib/dpkg/status
 229-4ubuntu4 500
500 http://eu-central-1.ec2.archive.ubuntu.com/ubuntu xenial/main amd64 
Packages

Computer type: AWS EC2 instance

I am creating a systemd service file like this:

##
bootscript=/usr/bin/local/luksautomount.sh
servicename=luksautomount

cat > $bootscript <> /tmp/it-works
EOF

chmod +x $bootscript

cat > /etc/systemd/system/$servicename.service  $bootscript <> /tmp/it-works
  EOF

  chmod +x $bootscript

  cat > /etc/systemd/system/$servicename.service 

[Touch-packages] [Bug 1841928] Re: systemd service file not triggering the bash script

2019-08-29 Thread Chris Guiver
Thank you for taking the time to report this issue and helping to make
Ubuntu better.

Examining the information you have given us, this does not appear to be
a bug report, but instead seems to be a request for support.  Is it?

We understand the difficulties you are facing, but it is better to raise
problems you are having in the support tracker at
https://answers.launchpad.net/ubuntu if you are uncertain if they are
bugs.

You can also find help with your problem in the support forum of your
local Ubuntu community http://loco.ubuntu.com/ or asking at
https://askubuntu.com or https://ubuntuforums.org. For help on reporting
bugs, see https://help.ubuntu.com/community/ReportingBugs.

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

Title:
  systemd  service file not triggering the bash script

Status in systemd package in Ubuntu:
  New

Bug description:
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=16.04
  DISTRIB_CODENAME=xenial
  DISTRIB_DESCRIPTION="Ubuntu 16.04.6 LTS"

  systemd:
Installed: 229-4ubuntu21.21
Candidate: 229-4ubuntu21.22
Version table:
   229-4ubuntu21.22 500
  500 http://eu-central-1.ec2.archive.ubuntu.com/ubuntu 
xenial-updates/main amd64 Packages
   *** 229-4ubuntu21.21 500
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   229-4ubuntu4 500
  500 http://eu-central-1.ec2.archive.ubuntu.com/ubuntu xenial/main 
amd64 Packages

  Computer type: AWS EC2 instance

  I am creating a systemd service file like this:

  ##
  bootscript=/usr/bin/local/luksautomount.sh
  servicename=luksautomount

  cat > $bootscript <> /tmp/it-works
  EOF

  chmod +x $bootscript

  cat > /etc/systemd/system/$servicename.service 

[Touch-packages] [Bug 1815172] Re: [bionic] drm/i915: softpin broken, needs to be fixed for 32bit mesa

2019-08-29 Thread Chris Halse Rogers
Hello Alkis, or anyone else affected,

Accepted mesa into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/19.0.8-0ubuntu0~18.04.2 in a
few hours, and then in the -proposed repository.

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

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

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

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

** Changed in: mesa (Ubuntu Bionic)
   Status: In Progress => Fix Committed

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

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

Title:
  [bionic] drm/i915: softpin broken, needs to be fixed for 32bit mesa

Status in Mesa:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Committed
Status in mesa source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Won't Fix
Status in mesa source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  Several schools reported black screens after normally updating their Ubuntu 
boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1.

  Downgrading mesa fixes the problem.

  lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD
  Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer
  Inc. HD Graphics 530 [1043:8694]Kernel modules: i915

  Unfortunately I can't find a lot of useful information, here are some bits:
   * systemctl --failed says "gpu-manager" and "lightdm" have failed
   * Xorg.log is clean: https://termbin.com/6l2b
   * dmesg too: https://termbin.com/ip4e
   * It happens on lightdm/MATE, I don't know about Ubuntu GNOME.
   * If one runs `xinit` from ssh, it fails with:
  i965: Failed to submit batchbuffer: Invalid argument

  This is caused by mesa assuming that soft-pinning on GEN8+ is working
  since kernel 4.5, but in fact this issue wasn't fixed until 4.19.3. So
  a proper fix would be to backport commits from 4.19.3/4.20 to fix GTT
  sizes/pin flags, but that's left for future.

  [Test case]
  install fixed mesa or kernel, check that the regression is fixed

  [Regression potential]
  mesa: shouldn't be any, it just reverts the change to always soft-pin
  (TODO kernel: adds commits from upstream stable, which have been well tested 
upstream by now)

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

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


[Touch-packages] [Bug 1841412] Re: Build with NDEBUG again

2019-08-29 Thread Chris Halse Rogers
Hello Timo, or anyone else affected,

Accepted mesa into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/19.0.8-0ubuntu0~18.04.2 in a
few hours, and then in the -proposed repository.

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

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

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

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

** Changed in: mesa (Ubuntu Bionic)
   Status: Confirmed => Fix Committed

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

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

Title:
  Build with NDEBUG again

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

Bug description:
  [Impact]
  Mesa is now built with meson, and it turns out that meson < 0.47.0 (commit 
7c4736d27f4c5d7 to be exact) doesn't handle command line options properly which 
means that -Db_ndebug=true didn't have any effect when mesa is built on bionic. 
This means that some asserts are enabled, and at least nouveau is affected.

  [Test case]
  chech the build log that -DNDEBUG is passed

  [Regression potential]
  none really, it just adds a build flag which should've been there

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

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


[Touch-packages] [Bug 1838370] Re: slapd segfault on filter parse error

2019-08-29 Thread Launchpad Bug Tracker
This bug was fixed in the package openldap - 2.4.42+dfsg-2ubuntu3.7

---
openldap (2.4.42+dfsg-2ubuntu3.7) xenial; urgency=medium

  * d/p/rwm-do-not-free-original-filter.patch: Fix slapd segfault (LP:
#1838370)

 -- Lucas Kanashiro   Thu, 08 Aug 2019
16:33:06 -0300

** Changed in: openldap (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  slapd segfault on filter parse error

Status in openldap:
  Fix Released
Status in openldap package in Ubuntu:
  Fix Released
Status in openldap source package in Xenial:
  Fix Released
Status in openldap source package in Bionic:
  Fix Released
Status in openldap source package in Disco:
  Fix Released
Status in openldap package in Debian:
  Unknown

Bug description:
  [Impact]

  Users willing to use the slapd rwm overlay will face a slapd
  segmentation fault when trying to rewrite some rules. Backporting this
  fix will allow users using stable releases to take advantage of this
  feature without crashing slapd. This issue was fixed by upstream not
  freeing the rwm overlay filter memory without prior checking.

  [Test Case]

  In this test case, the rwm overlay will be used and a rule will be
  created to deny any search request for uid=root, then the 'ldapsearch'
  will be invoked to trigger the failure. It is important to mention
  that the 'ldapsearch' command should fail regardless the presence of
  the bug in the package, the target here is the slapd crash. To
  reproduce this bug one can follow the procedure below in Ubuntu
  xenial, bionic or disco:

  $ sudo apt-get update

  Use debconf to pre-seed slapd questions before install it:

  $ debconf-set-selections << EOF
  slapd slapd/no_configuration boolean false
  slapd slapd/domain string example.com
  slapd shared/organization string example.com
  slapd slapd/password1 password test
  slapd slapd/password2 password test
  slapd slapd/backend select MDB
  slapd slapd/move_old_database boolean false
  EOF
  $ sudo apt-get install slapd ldap-utils -y

  Create a file called 'add-rwm.ldif' with the following content:

  $ cat add-rwm.ldif
  dn: cn=module{0},cn=config
  changetype: modify
  add: olcModuleLoad
  olcModuleLoad: rwm

  dn: olcOverlay=rwm,olcDatabase={1}mdb,cn=config
  changetype: add
  objectClass: olcOverlayConfig
  objectClass: olcRwmConfig
  olcOverlay: rwm
  olcRwmRewrite: {0} rwm-rewriteEngine "on"
  olcRwmRewrite: {1} rwm-rewriteContext "searchFilter"
  olcRwmRewrite: {2} rwm-rewriteRule "(.*)(uid=root)(.*)" "$1$2$3" "#"

  With this file in place, run:

  $ sudo ldapadd -Q -Y EXTERNAL -H ldapi:/// -f add-rwm.ldif

  Now, to trigger the crash:

  $ ldapsearch -x -h localhost -b dc=example,dc=com -LLL uid=root
  Server is unwilling to perform (53)
  Additional information: searchFilter/searchFilterAttrDN massage error

  slapd process will die, and /var/crash will have a crash file for
  slapd. You can run the following command to confirm the error:

  $ cat /var/log/syslog | grep filter_free
  Aug  9 19:51:05 popular-gorilla slapd[1479]: filter_free: unknown filter 
type=28530

  -> Expected behavior

  In this test case, as mentioned before, the 'ldapsearch' command
  should fail but the 'slapd' process should not die. As result, we
  don't expect a slapd crash report in /var/crash directory.

  [Regression Potential]

  Since the fix is a patch provided by upstream (reviewed by maintainers
  and us) simple mistakes like typos are not expected. The patch impacts
  only the rwm module which is not loaded by default. So any regression
  would affect only the users that make use of this overlay. If an user
  is not using rwm overlay and is facing any issue, it should be related
  to other problems related to LDAP directory services.

  [Original message]

  Hello!
  We have faced slapd crash, seems an attacker was trying to brute force one
  of our services and uid parsing failures caused slapd crash:

  Jul 26 18:59:47 slapd[1252]: conn=1466 op=13 SRCH
  base="ou=test,dc=test,dc=com" scope=2 deref=0
  
filter="(&(uid=aistar123<>!n)(objectClass=posixAccount)(uid=*)(&(uidNumber=*)(!(uidNumber=0"
  Jul 26 18:59:47 slapd[1252]: conn=1466 op=13 SRCH attr=objectClass uid
  userPassword uidNumber gidNumber gecos homeDirectory loginShell
  krbPrincipalName cn memberOf modifyTimestamp modifyTimestamp
  shadowLastChange shadowMin shadow
  Max shadowWarning shadowInactive shadowExpire shadowFlag krbLastPwdChange
  krbPasswordExpiration pwdAttribute authorizedService accountExpires
  userAccountControl nsAccountLock host loginDisabled loginExpirationTime
  loginAllowedTimeMap sshPublic
  Key
  Jul 26 18:59:47 slapd[1252]: conn=1466 op=13 SEARCH RESULT tag=101 err=0
  nentries=0 text=massaged filter parse error
  Jul 26 18:59:47 kernel: [ 9441.554161] slapd[2367]: segfault at 18 ip
  

[Touch-packages] [Bug 1818918] Re: gdb doesn't search in debug-file-directory for .gnu_debugaltlink

2019-08-29 Thread Matthias Klose
looking up the .gnu_debugaltlink in a normal debug session works
perfectly fine.  Please can you show this behavior without any sandbox,
or try to diagnose why it doesn't work in this sandbox?  I am not
familiar with this sandbox environment.


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

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

Title:
  gdb doesn't search in debug-file-directory for .gnu_debugaltlink

Status in gdb package in Ubuntu:
  Incomplete

Bug description:
  As far as I can tell gdb version 8.2.90 isn't searching the debug-
  file-directory, which I set, for the '.gnu_debugaltlink' which is in
  the debug symbols. Here's the error I'm seeing:

  Type "apropos word" to search for commands related to "word".
  Reading symbols from /srv/vms/apport-sandbox-dir/Ubuntu 
19.04/amd64/report-sandbox//usr/bin/gnome-calculator...
  Reading symbols from /srv/vms/apport-sandbox-dir/Ubuntu 
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug...
  could not find '.gnu_debugaltlink' file for 
/srv/vms/apport-sandbox-dir/Ubuntu 
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug
  (No debugging symbols found in /srv/vms/apport-sandbox-dir/Ubuntu 
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug)

  Here's part of an strace of what's going on behind the scenes:

  lstat("/srv/vms/apport-sandbox-dir/Ubuntu 
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug",
 {st_mode=S_IFREG|0644, st_size=839744, ...}) = 0 
  openat(AT_FDCWD, 
"/usr/lib/debug/.dwz/x86_64-linux-gnu/gnome-calculator.debug", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)

  This is the only time "/usr/lib/debug" is searched, generally
  "/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-
  sandbox/usr/lib/debug/" is used. I'll attach the full strace though.

  For completeness here's the gdb command I'm using:

  Calling gdb command: '/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64
  /report-sandbox/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2' '/srv/vms
  /apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/usr/bin/gdb'
  --ex 'set debug-file-directory /srv/vms/apport-sandbox-dir/Ubuntu
  19.04/amd64/report-sandbox/usr/lib/debug' --ex 'set solib-absolute-
  prefix /srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox'
  --ex 'add-auto-load-safe-path /srv/vms/apport-sandbox-dir/Ubuntu
  19.04/amd64/report-sandbox' --ex 'set solib-search-path /srv/vms
  /apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/lib/x86_64
  -linux-gnu' --ex 'set data-directory /srv/vms/apport-sandbox-
  dir/Ubuntu 19.04/amd64/report-sandbox/usr/share/gdb' --ex 'file
  "/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-
  sandbox//usr/bin/gnome-calculator"' --ex 'core-file
  /tmp/apport_core_1b6dn6np'

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

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