[Touch-packages] [Bug 1720890] Re: vulkan-smoketest segfaults steam vulkan games segfault

[Lawrence A Fossi]

Didn't see your last post no worries I'm not really too concerned about i386 
was just trying to be as complete as possible. I just ran The Talos Princible 
in moddable version non x64 and it completed just fine despite the elf class 
warning no loss of fps or any visible graphical errors so really not a big 
issue. Thank you can't wait for 17.2.4 to hit the official update repo's.
As far as I'm comcerned issues fixed.

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

Title:
  vulkan-smoketest segfaults steam vulkan games segfault

Status in mesa package in Ubuntu:
  In Progress
Status in mesa source package in Xenial:
  New
Status in mesa source package in Artful:
  New

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  $ apt-cache policy mesa-vulkan-drivers
  mesa-vulkan-drivers:
Installed: 17.2.1-0ubuntu1
Candidate: 17.2.1-0ubuntu1
Version table:
   *** 17.2.1-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu artful/universe amd64 Packages
  100 /var/lib/dpkg/status

  
  Easily reproducible : apt-get install mesa-vulkan-drivers apt-get install 
vulkan-utils

  Open a terminal type vulkan-smoketest instead of a glxgears type window it 
will segfault.
  message from kernel.log:
  Sep 29 16:23:53 Tardis-1 kernel: [17709.532915] vulkan-smoketes[11798]: 
segfault at 0 ip 7fed61a17914 sp 7ffedcb8f850 error 6 in 
libvulkan_radeon.so[7fed619ab000+18b000]
  syslog:
  Sep 28 10:38:13 Tardis-1 kernel: [18292.174313] vulkan-smoketes[13385]: 
segfault at 0 ip 7f62705a7914 sp 7ffd0edc6260 error 6 in 
libvulkan_radeon.so[7f627053b000+18b000]

  What should happen is a glxgears like window will open and render properly 
instead of segfaulting.
  It appears that the culprit is an old or broken libvulkan_radeon.so provided 
by mesa-vulkan-drivers.

  As a test I renamed the old lib and dropped in a newer version from
  oibaf's ppa. smoketest now passes steam's The Talos Princible and Mad
  Max now work properly in Vulkan mode as well instead of segfaulting.

  This issue is also present on Zesty and fixed in both Oibaf's and
  Padoka's ppa's since April back when they were rolling 17.2 mesa.

  I have no idea if libvulkan_intel.so also needs updating no hardware
  to check.

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

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

[Touch-packages] [Bug 1720890] Re: vulkan-smoketest segfaults steam vulkan games segfault

[Lawrence A Fossi]

to be specific the libvulkan_intel.so and libvulkan_radeon.so i386
provided by mesa-vulkan-drivers:i386

also works great with $ uname -a
Linux 4.14.0-041400rc8-generic #201711052313 SMP Sun Nov 5 23:14:08 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  vulkan-smoketest segfaults steam vulkan games segfault

Status in mesa package in Ubuntu:
  In Progress
Status in mesa source package in Xenial:
  New
Status in mesa source package in Artful:
  New

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  $ apt-cache policy mesa-vulkan-drivers
  mesa-vulkan-drivers:
Installed: 17.2.1-0ubuntu1
Candidate: 17.2.1-0ubuntu1
Version table:
   *** 17.2.1-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu artful/universe amd64 Packages
  100 /var/lib/dpkg/status

  
  Easily reproducible : apt-get install mesa-vulkan-drivers apt-get install 
vulkan-utils

  Open a terminal type vulkan-smoketest instead of a glxgears type window it 
will segfault.
  message from kernel.log:
  Sep 29 16:23:53 Tardis-1 kernel: [17709.532915] vulkan-smoketes[11798]: 
segfault at 0 ip 7fed61a17914 sp 7ffedcb8f850 error 6 in 
libvulkan_radeon.so[7fed619ab000+18b000]
  syslog:
  Sep 28 10:38:13 Tardis-1 kernel: [18292.174313] vulkan-smoketes[13385]: 
segfault at 0 ip 7f62705a7914 sp 7ffd0edc6260 error 6 in 
libvulkan_radeon.so[7f627053b000+18b000]

  What should happen is a glxgears like window will open and render properly 
instead of segfaulting.
  It appears that the culprit is an old or broken libvulkan_radeon.so provided 
by mesa-vulkan-drivers.

  As a test I renamed the old lib and dropped in a newer version from
  oibaf's ppa. smoketest now passes steam's The Talos Princible and Mad
  Max now work properly in Vulkan mode as well instead of segfaulting.

  This issue is also present on Zesty and fixed in both Oibaf's and
  Padoka's ppa's since April back when they were rolling 17.2 mesa.

  I have no idea if libvulkan_intel.so also needs updating no hardware
  to check.

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

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

[Touch-packages] [Bug 1720890] Re: vulkan-smoketest segfaults steam vulkan games segfault

[Timo Aaltonen]

thanks for testing!

32bit drivers need 32bit vulkaninfo, and I don't know how to provide
that for 64bit.. so it's a non-issue right now

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

Title:
  vulkan-smoketest segfaults steam vulkan games segfault

Status in mesa package in Ubuntu:
  In Progress
Status in mesa source package in Xenial:
  New
Status in mesa source package in Artful:
  New

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  $ apt-cache policy mesa-vulkan-drivers
  mesa-vulkan-drivers:
Installed: 17.2.1-0ubuntu1
Candidate: 17.2.1-0ubuntu1
Version table:
   *** 17.2.1-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu artful/universe amd64 Packages
  100 /var/lib/dpkg/status

  
  Easily reproducible : apt-get install mesa-vulkan-drivers apt-get install 
vulkan-utils

  Open a terminal type vulkan-smoketest instead of a glxgears type window it 
will segfault.
  message from kernel.log:
  Sep 29 16:23:53 Tardis-1 kernel: [17709.532915] vulkan-smoketes[11798]: 
segfault at 0 ip 7fed61a17914 sp 7ffedcb8f850 error 6 in 
libvulkan_radeon.so[7fed619ab000+18b000]
  syslog:
  Sep 28 10:38:13 Tardis-1 kernel: [18292.174313] vulkan-smoketes[13385]: 
segfault at 0 ip 7f62705a7914 sp 7ffd0edc6260 error 6 in 
libvulkan_radeon.so[7f627053b000+18b000]

  What should happen is a glxgears like window will open and render properly 
instead of segfaulting.
  It appears that the culprit is an old or broken libvulkan_radeon.so provided 
by mesa-vulkan-drivers.

  As a test I renamed the old lib and dropped in a newer version from
  oibaf's ppa. smoketest now passes steam's The Talos Princible and Mad
  Max now work properly in Vulkan mode as well instead of segfaulting.

  This issue is also present on Zesty and fixed in both Oibaf's and
  Padoka's ppa's since April back when they were rolling 17.2 mesa.

  I have no idea if libvulkan_intel.so also needs updating no hardware
  to check.

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

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

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

[Nicholas Stommel]

@bagl0312 I agree, there really should be some kind of GUI default way
to set negative DNS priority when setting up certain VPN connections.
The average user shouldn't experience a nasty surprise when DNS leaks
happen by default.

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

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

Status in NetworkManager:
  Unknown
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Zesty:
  Confirmed
Status in network-manager source package in Artful:
  Fix Released

Bug description:
  [Impact]

   * NetworkManager incorrectly handles dns-priority of the VPN-like
  connections, which leads to leaking DNS queries outside of the VPN
  into the general internet.

   * Upstream has resolved this issue in master and 1.8 to correctly
  configure any dns backends with negative dns-priority settings.

  [Test Case]

  #FIXME#

   * detailed instructions how to reproduce the bug

   * these should allow someone who is not familiar with the affected
 package to reproduce the bug and verify that the updated package fixes
 the problem.

  #FIXME#

  [Regression Potential]

   * If this issue is changed DNS resolution will change, for certain
  queries, to go via VPN rather than general internet. And therefore,
  one may get new/different results or even loose access to
  resolve/access certain parts of the interent depending on what the DNS
  server on VPN chooses to respond to.

  [Other Info]
   
   * Original bug report

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

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

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

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

[Touch-packages] [Bug 1686189] Re: External monitor connecting problem on Intel graphics card

[Kai-Heng Feng]

Linux kernel v4.4.0-100 in xenial-proposed contains the fix. Please give
it a try.

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

Title:
  External monitor connecting problem on Intel graphics card

Status in linux package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I am facing a problem with Intel Graphics driver. I have external
  monitor and in display settings the second monitor is detecting but
  it's not working, so could you email me a solution.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.4.25-040425-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Apr 25 21:45:16 2017
  DistUpgraded: 2017-04-25 21:07:40,819 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-75-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05e9]
  InstallationDate: Installed on 2017-04-25 (0 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  MachineType: Dell Inc. Inspiron 3537
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.25-040425-generic 
root=UUID=3914e6d5-5c87-4816-8043-776ef4184d29 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-04-25 (0 days ago)
  dmi.bios.date: 04/30/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 03JPPR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A08
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd04/30/2014:svnDellInc.:pnInspiron3537:pvrA08:rvnDellInc.:rn03JPPR:rvrA00:cvnDellInc.:ct8:cvrA08:
  dmi.product.name: Inspiron 3537
  dmi.product.version: A08
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Apr 25 21:37:24 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   17900 
   vendor AUO
  xserver.version: 2:1.18.4-0ubuntu0.2

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

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

[Touch-packages] [Bug 1731130] [NEW] /run/resolvconf/resolv.conf contains invalid 'search' entries

[Paul Natsuo Kishimoto]

Public bug reported:

STEPS TO REPRODUCE:

I connect to certain MIT networks via both wired and wireless
connections.

Afterwards, I connect to a home network.

EXPECTED:

Domains like http://web.mit.edu resolve.

OBSERVED:

They don't.

The file /run/resolvconf/resolv.conf contains only these lines:

nameserver 127.0.0.53
search mit.edu hsd1.ma.comcast.net

It would seem hsd1.ma.comcast.net is correct, since that describes my
ISP. But the mit.edu is erroneous and prevents applications from
correctly resolving mit.edu domains.

If I manually edit this file and remove "mit.edu" from the search line,
the domains then resolve correctly. Shouldn't this be removed
automatically?


~$ lsb_release -rd && apt-cache policy resolvconf
Description:Ubuntu 17.10
Release:17.10
resolvconf:
  Installed: 1.79ubuntu8
  Candidate: 1.79ubuntu8
  Version table:
 *** 1.79ubuntu8 500
500 http://us.archive.ubuntu.com/ubuntu artful/universe amd64 Packages
500 http://us.archive.ubuntu.com/ubuntu artful/universe i386 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: resolvconf 1.79ubuntu8
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Nov  9 00:34:20 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-10-11 (28 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
PackageArchitecture: all
SourcePackage: resolvconf
UpgradeStatus: Upgraded to artful on 2017-10-19 (20 days ago)

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


** Tags: amd64 apport-bug artful wayland-session

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

Title:
  /run/resolvconf/resolv.conf contains invalid 'search' entries

Status in resolvconf package in Ubuntu:
  New

Bug description:
  STEPS TO REPRODUCE:

  I connect to certain MIT networks via both wired and wireless
  connections.

  Afterwards, I connect to a home network.

  EXPECTED:

  Domains like http://web.mit.edu resolve.

  OBSERVED:

  They don't.

  The file /run/resolvconf/resolv.conf contains only these lines:

  nameserver 127.0.0.53
  search mit.edu hsd1.ma.comcast.net

  It would seem hsd1.ma.comcast.net is correct, since that describes my
  ISP. But the mit.edu is erroneous and prevents applications from
  correctly resolving mit.edu domains.

  If I manually edit this file and remove "mit.edu" from the search
  line, the domains then resolve correctly. Shouldn't this be removed
  automatically?

  
  ~$ lsb_release -rd && apt-cache policy resolvconf
  Description:Ubuntu 17.10
  Release:17.10
  resolvconf:
Installed: 1.79ubuntu8
Candidate: 1.79ubuntu8
Version table:
   *** 1.79ubuntu8 500
  500 http://us.archive.ubuntu.com/ubuntu artful/universe amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu artful/universe i386 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: resolvconf 1.79ubuntu8
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov  9 00:34:20 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-10-11 (28 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: resolvconf
  UpgradeStatus: Upgraded to artful on 2017-10-19 (20 days ago)

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

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

[Touch-packages] [Bug 1728773] Re: [235.2ubuntu1] systemd upgrade set a read only filesystem

[dino99]

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

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

Title:
  [235.2ubuntu1] systemd upgrade set a read only filesystem

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  systemd update on Bionic  ends with a read only filesystem, and startx
  also fails.

  Looks like it is related to the tmpfiles right change in systemd:

  [ Michael Biebl ]
  * New upstream version 235
  - cryptsetup-generator: use remote-cryptsetup.target when _netdev is
  present (Closes: #852534)
  - tmpfiles: change btmp mode 0600 → 0660 (Closes: #870638)
  ---
  
  note: ran apport-collect from a 17.10 install, so the info is not about the 
Bionic install indeed.
  

  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: systemd 234-2ubuntu12.1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=8a00317c-669e-447c-bc40-1e06010b49ca ro
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P7.00
  dmi.board.name: B150M-HDV
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP7.00:bd10/07/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-HDV:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Touch-packages] [Bug 1731102] [NEW] Poor performance with Wayland

[David Beswick]

Public bug reported:

When running Gnome 3 in Wayland mode (confirmed with XDG_SESSION_TYPE
env var) I see the following issues on this hardware:

* Jerky animations (glxgears stutters noticably)
* Mouse cursor sometimes updated at a reduced framerate, usualy when CPU is 
under load, appearing to worsen over time (> 8 hours uptime)
* High CPU usage when mousing over icons in left-hand side Unity dock (20-30%), 
also causing mouse cursor to stutter
* 15fps in Kodi and poor video playback framerate
* 30-40% CPU usage in Kodi when program idle
* Gnome shell frequently using 25% of CPU or more

All issues disappear when using x11 mode (again confirmed with
XDG_SESSION_TYPE env var). Performance in that case seems as good as
17.04

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
BootLog:
 * Setting up X socket directories...    
[ OK ]
  * Restoring resolver state...    
[ OK ]
 Starting jabber server: ejabberd
CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Nov  9 13:03:08 2017
DistUpgraded: 2017-11-07 09:38:15,448 DEBUG icon theme changed, re-reading
DistroCodename: artful
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.1.30, 4.10.0-37-generic, x86_64: installed
 virtualbox, 5.1.30, 4.13.0-16-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6310] [1002:9802] 
(prog-if 00 [VGA controller])
   Subsystem: ZOTAC International (MCO) Ltd. Wrestler [Radeon HD 6310] 
[19da:a191]
InstallationDate: Installed on 2011-12-05 (2165 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=e1bf9820-e70e-4e84-9037-621437cc90f1 ro radeon.audio=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to artful on 2017-11-06 (2 days ago)
dmi.bios.date: 10/28/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.4
dmi.board.name: AMD HUDSON-M1
dmi.board.vendor: ZOTAC
dmi.chassis.type: 3
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd10/28/2011:svn:pn:pvr:rvnZOTAC:rnAMDHUDSON-M1:rvr:cvn:ct3:cvr:
version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Wed Oct 18 20:39:16 2017
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputRiitek Micro Keyboard KEYBOARD, id 8
 inputRiitek Micro Keyboard MOUSE, id 9
 inputRiitek Micro Keyboard KEYBOARD, id 10
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.3-1ubuntu1.3
xserver.video_driver: radeon

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


** Tags: amd64 apport-bug artful performance ubuntu wayland-session

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

Title:
  Poor performance with Wayland

Status in xorg package in Ubuntu:
  New

Bug description:
  When running Gnome 3 in Wayland mode (confirmed with XDG_SESSION_TYPE
  env var) I see the following issues on this hardware:

  * Jerky animations (glxgears stutters noticably)
  * Mouse cursor sometimes updated at a reduced framerate, usualy when CPU is 
under load, appearing to worsen over time (> 8 hours uptime)
  * High CPU usage when mousing over icons in left-hand side Unity dock 
(20-30%), also causing mouse cursor to stutter
  * 15fps in Kodi and poor video playback framerate
  * 30-40% CPU usage in Kodi when program idle
  * Gnome shell frequently using 25% of CPU or more

  All issues disappear when using x11 mode (again confirmed with
  XDG_SESSION_TYPE env var). Performance in that case seems as good as
  17.04

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic 

[Touch-packages] [Bug 1670959] Re: systemd-resolved using 100% CPU

[James Cuzella]

Also seeing this issue in Ubuntu 17.10 (artful) with:

dnsmasq-base  2.78-1
systemd   234-2ubuntu12.1

I can confirm that following https://askubuntu.com/a/968309/  resolves
the issue!

Steps to fix the issue:

Added this line to /etc/default/dnsmasq:

DNSMASQ_EXCEPT=lo

Then restarting dnsmasq:

sudo systemctl daemon-reload
sudo systemctl restart dnsmasq

No more systemd-resolved taking 99-100% of a CPU core!

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

Title:
  systemd-resolved using 100% CPU

Status in dnsmasq package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Sometimes systemd-resolved process is using 100% CPU.
  After a while it changes back to normal.

  It happens usually after connecting to the (wifi) network, like
  starting the OS.

  strace output:

  sendmsg(12, {msg_name(16)={sa_family=AF_INET, sin_port=htons(33589), 
sin_addr=inet_addr("127.0.0.1")}, 
msg_iov(1)=[{"6\215\201\200\0\1\0\1\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\300\f\0\34\0\1\0\0\10\235\0\20&\6(\0\0024\0Y%L\4\6#f&\214\0\0)\377\326\0\0\0\0\0\0",
 81}], msg_controllen=28, [{cmsg_len=28, cmsg_level=SOL_IP, 
cmsg_type=IP_PKTINFO, {ipi_ifindex=if_nametoindex("lo"), 
ipi_spec_dst=inet_addr("127.0.0.53"), ipi_addr=inet_addr("127.0.0.53")}}], 
msg_flags=0}, 0) = 81
  sendmsg(3, {msg_name(0)=NULL, 
msg_iov(4)=[{"PRIORITY=6\nSYSLOG_FACILITY=3\nCODE_FILE=../src/resolve/resolved-dns-stub.c\nCODE_LINE=363\nCODE_FUNCTION=dns_stub_process_query\nSYSLOG_IDENTIFIER=systemd-resolved\n",
 160}, {"MESSAGE=", 8}, {"Processing query...", 19}, {"\n", 1}], 
msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 188
  epoll_wait(4, [{EPOLLIN, {u32=3176459184, u64=94565471415216}}], 16, -1) = 1
  clock_gettime(CLOCK_BOOTTIME, {44665, 938069872}) = 0
  recvfrom(12, NULL, 0, MSG_PEEK|MSG_TRUNC, NULL, NULL) = 53
  recvmsg(12, {msg_name(16)={sa_family=AF_INET, sin_port=htons(33589), 
sin_addr=inet_addr("127.0.0.1")}, 
msg_iov(1)=[{"Z\262\1\20\0\1\0\0\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\0\0)\2\0\0\0\0\0\0\0",
 3936}], msg_controllen=56, [{cmsg_len=28, cmsg_level=SOL_IP, 
cmsg_type=IP_PKTINFO, {ipi_ifindex=if_nametoindex("lo"), 
ipi_spec_dst=inet_addr("127.0.0.53"), ipi_addr=inet_addr("127.0.0.53")}}, 
{cmsg_len=20, cmsg_level=SOL_IP, cmsg_type=IP_TTL, {ttl=64}}], msg_flags=0}, 0) 
= 53
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  getrandom("\365I", 2, GRND_NONBLOCK)= 2
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  getrandom("\203;", 2, GRND_NONBLOCK)= 2
  clock_gettime(CLOCK_BOOTTIME, {44665, 938446937}) = 0
  open("/run/systemd/netif/links/3", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such 
file or directory)
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  socket(AF_INET, SOCK_DGRAM|SOCK_CLOEXEC|SOCK_NONBLOCK, IPPROTO_IP) = 18
  connect(18, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("127.0.0.1")}, 16) = 0
  epoll_ctl(4, EPOLL_CTL_ADD, 18, {EPOLLIN, {u32=3176610576, 
u64=94565471566608}}) = 0
  write(18, 
"\203;\1\20\0\1\0\0\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\0\0)\2\0\0\0\0\0\0\0",
 53) = 53
  clock_gettime(CLOCK_BOOTTIME, {44665, 938833717}) = 0
  clock_gettime(CLOCK_BOOTTIME, {44665, 938875138}) = 0
  epoll_ctl(4, EPOLL_CTL_DEL, 18, NULL)   = 0
  close(18)   = 0

  journalctl output:

  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:41 parsec dnsmasq[1545]: Maximum number of concurrent DNS 
queries reached (max: 150)

  As you can see, I would use it together with dnsmasq.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-18ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-9.11-generic 4.10.0
  Uname: Linux 4.10.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  Date: Wed Mar  8 08:20:18 2017
  MachineType: Hewlett-Packard HP EliteBook Folio 1020 G1
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.10.0-9-generic 
root=UUID=a54fe703-35d4-47ac-9c6e-4034421531fb ro rootflags=subvol=@
  SourcePackage: systemd
  

[Touch-packages] [Bug 1731094] [NEW] Trouble Switching between GPUs on a Carrizo laptop with an integrated and discrete graphics card.

[Craig Stein]

Public bug reported:


Yesterday I decided to learn how to switch between my low power usage
GPU and my discrete GPU in my laptop using Prime. I started by running
this command: xrandr --listproviders.

I got the following result:

Providers: number : 2 Provider 0: id: 0x75 cap: 0x9, Source Output,
Sink Offload crtcs: 3 outputs: 3 associated providers: 1 name:AMD Radeon
R6 Graphics @ pci::00:01.0 Provider 1: id: 0x3f cap: 0x4, Source
Offload crtcs: 0 outputs: 0 associated providers: 1 name:AMD Radeon (TM)
R7 M360 @ pci::03:00.0

I then ran this command to switch to my discrete GPU: xrandr
--setprovideroffloadsink 1 0.

This resulted in the following result to my GPU with this command:
DRI_PRIME=1 glxinfo | grep "OpenGL renderer"

OpenGL renderer string: AMD Radeon (TM) R7 M360 (AMD ICELAND / DRM
3.18.0 / 4.13.8-041308-generic, LLVM 5.0.0)

Now however when i attempt to switch back to using my low powered Radeon
R6 with this command I get: xrandr --setprovideroffloadsink 0 1

X Error of failed request: BadValue (integer parameter out of range
for operation) Major opcode of failed request: 140 (RANDR) Minor opcode
of failed request: 34 (RRSetProviderOffloadSink) Value in failed
request: 0x75 Serial number of failed request: 16 Current serial number
in output stream: 17

I should mention I am logging into the Gnome session using Xorg on
Ubuntu 17.10. I would love to be able to switch back to my R6 so any
help is much appreciated.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
Uname: Linux 4.13.8-041308-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CompositorRunning: None
CurrentDesktop: GNOME
Date: Wed Nov  8 19:53:41 2017
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
DkmsStatus: virtualbox, 5.1.30, 4.13.8-041308-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Carrizo [1002:9874] (rev c5) (prog-if 
00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] Carrizo [1025:095e]
InstallationDate: Installed on 2017-10-20 (19 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.8-041308-generic 
root=UUID=17c9ce89-7e9f-4910-965e-cbd862c45839 ro modprobe.blacklist=radeon 
radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 
amdgpu.cik_support=1 quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/15/2015
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.10
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Nami_CZ
dmi.board.vendor: Acer
dmi.board.version: V1.10
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.10:bd09/15/2015:svnAcer:pn:pvrV1.10:rvnAcer:rnNami_CZ:rvrV1.10:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.family: CZ
dmi.product.version: V1.10
dmi.sys.vendor: Acer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug artful ubuntu xrandr

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

Title:
  Trouble Switching between GPUs on a Carrizo laptop with an integrated
  and discrete graphics card.

Status in xorg package in Ubuntu:
  New

Bug description:

  Yesterday I decided to learn how to switch between my low power usage
  GPU and my discrete GPU in my laptop using Prime. I started by running
  this command: xrandr --listproviders.

  I got the following result:

  Providers: number : 2 Provider 0: id: 0x75 cap: 0x9, Source
  Output, Sink Offload crtcs: 3 outputs: 3 associated providers: 1
  name:AMD Radeon R6 Graphics @ pci::00:01.0 Provider 1: id: 0x3f
  cap: 0x4, Source Offload crtcs: 0 outputs: 0 associated providers: 1
  name:AMD Radeon (TM) R7 M360 @ pci::03:00.0

  I then ran this command to switch to my discrete GPU: xrandr
  --setprovideroffloadsink 1 0.

  This resulted in the following result to my GPU with this command:
  DRI_PRIME=1 glxinfo | grep "OpenGL renderer"

  OpenGL renderer string: AMD Radeon (TM) R7 M360 (AMD ICELAND / DRM
  3.18.0 / 4.13.8-041308-generic, LLVM 5.0.0)

  Now however when i attempt 

[Touch-packages] [Bug 1612711] Re: TLS negation fails

[Graham Leggett]

Using openssl s_client on a MacOS Sierra machine connecting to the same
postgresql server, the failure is identical.

Looks like whatever is triggering this is caused by the server, but is
being failed by the client.

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

Title:
  TLS negation fails

Status in openssl package in Ubuntu:
  Confirmed

Bug description:
  This seems like a duplicate of #965371, however that is marked fixed,
  so I don't know.

  I'm running 16.04.1.  I'm setting up OpenLDAP with TLS.  I've followed
  the instructions at https://help.ubuntu.com/lts/serverguide/openldap-
  server.html#openldap-tls, and test with the command openssl s_client
  -connect my.server.com:389 -showcerts and I get the error:

  140668035487384:error:140790E5:SSL routines:ssl23_write:ssl handshake
  failure:s23_lib.c:177

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

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

[Touch-packages] [Bug 1729377] Re: AMD r7 250 wrong detection

[brad]

** Attachment added: "Xorg.1.log"
   
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1729377/+attachment/5006144/+files/Xorg.1.log

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

Title:
  AMD r7 250 wrong detection

Status in mesa package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  My AMD R7 250 GPU is being wrongly detected in Ubuntu as a Radeon HD
  8830M. This results in the wrong detection of drivers. The result is a
  wrongly installed driver and very poor performance. This bug has been
  affecting me since Ubuntu 16.10, and still affects me in Ubuntu 17.10.

  brad@brad-ubuntu:~$ lspci | grep 'VGA compatible controller'
  02:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Venus LE [Radeon HD 8830M] (rev 87)
  brad@brad-ubuntu:~$ lsmod | grep -i 'radeon'
  radeon   1470464  9
  i2c_algo_bit   16384  2 amdgpu,radeon
  ttm94208  2 amdgpu,radeon
  drm_kms_helper167936  2 amdgpu,radeon
  drm   356352  9 amdgpu,radeon,ttm,drm_kms_helper
  brad@brad-ubuntu:~$ lsmod | grep -i 'amdgpu'
  amdgpu   2007040  0
  i2c_algo_bit   16384  2 amdgpu,radeon
  ttm94208  2 amdgpu,radeon
  drm_kms_helper167936  2 amdgpu,radeon
  drm   356352  9 amdgpu,radeon,ttm,drm_kms_helper

  Ubuntu installs by autodetection: xserver-xorg-video-ati. The proper
  driver is, xserver-xorg-video-radeon.

  However even after proper installation of the new driver. Ubuntu still
  reports that I am using a mobile graphics card, instead of a desktop
  graphics card.

  Ubuntu reports: llvmpipe (LLVM 5.0, 128 bits) with the radeon driver. And 
CAPE VERDE with the ati driver. Its a "OLAND" or "southern island" card.
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: 2017-10-21 23:44:08,256 DEBUG icon theme changed, re-reading
  DistroCodename: artful
  DistroRelease: Ubuntu 17.10
  DistroVariant: ubuntu
  InstallationDate: Installed on 2017-08-23 (71 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: MSI MS-7721
  Package: xorg 1:7.7+19ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=d9298166-bfea-422f-990f-71ef38407fa5 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful ubuntu
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-22 (11 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/10/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V8.4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A68HM-E33 V2 (MS-7721)
  dmi.board.vendor: MSI
  dmi.board.version: 9.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 9.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV8.4:bd08/10/2016:svnMSI:pnMS-7721:pvr9.0:rvnMSI:rnA68HM-E33V2(MS-7721):rvr9.0:cvnMSI:ct3:cvr9.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7721
  dmi.product.version: 9.0
  dmi.sys.vendor: MSI
  version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Touch-packages] [Bug 1729377] Re: AMD r7 250 wrong detection

[brad]

** Attachment added: "outpout of glxinfo.txt"
   
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1729377/+attachment/5006143/+files/outpout%20of%20glxinfo.txt

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

Title:
  AMD r7 250 wrong detection

Status in mesa package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  My AMD R7 250 GPU is being wrongly detected in Ubuntu as a Radeon HD
  8830M. This results in the wrong detection of drivers. The result is a
  wrongly installed driver and very poor performance. This bug has been
  affecting me since Ubuntu 16.10, and still affects me in Ubuntu 17.10.

  brad@brad-ubuntu:~$ lspci | grep 'VGA compatible controller'
  02:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Venus LE [Radeon HD 8830M] (rev 87)
  brad@brad-ubuntu:~$ lsmod | grep -i 'radeon'
  radeon   1470464  9
  i2c_algo_bit   16384  2 amdgpu,radeon
  ttm94208  2 amdgpu,radeon
  drm_kms_helper167936  2 amdgpu,radeon
  drm   356352  9 amdgpu,radeon,ttm,drm_kms_helper
  brad@brad-ubuntu:~$ lsmod | grep -i 'amdgpu'
  amdgpu   2007040  0
  i2c_algo_bit   16384  2 amdgpu,radeon
  ttm94208  2 amdgpu,radeon
  drm_kms_helper167936  2 amdgpu,radeon
  drm   356352  9 amdgpu,radeon,ttm,drm_kms_helper

  Ubuntu installs by autodetection: xserver-xorg-video-ati. The proper
  driver is, xserver-xorg-video-radeon.

  However even after proper installation of the new driver. Ubuntu still
  reports that I am using a mobile graphics card, instead of a desktop
  graphics card.

  Ubuntu reports: llvmpipe (LLVM 5.0, 128 bits) with the radeon driver. And 
CAPE VERDE with the ati driver. Its a "OLAND" or "southern island" card.
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: 2017-10-21 23:44:08,256 DEBUG icon theme changed, re-reading
  DistroCodename: artful
  DistroRelease: Ubuntu 17.10
  DistroVariant: ubuntu
  InstallationDate: Installed on 2017-08-23 (71 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: MSI MS-7721
  Package: xorg 1:7.7+19ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=d9298166-bfea-422f-990f-71ef38407fa5 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful ubuntu
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-22 (11 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/10/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V8.4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A68HM-E33 V2 (MS-7721)
  dmi.board.vendor: MSI
  dmi.board.version: 9.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 9.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV8.4:bd08/10/2016:svnMSI:pnMS-7721:pvr9.0:rvnMSI:rnA68HM-E33V2(MS-7721):rvr9.0:cvnMSI:ct3:cvr9.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7721
  dmi.product.version: 9.0
  dmi.sys.vendor: MSI
  version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Touch-packages] [Bug 1612711] Re: TLS negation fails

[Graham Leggett]

ssldump looks like the below.

>From ssldump, we can see that the server sent three separate
certificates. Openssl s_client however claims that no certificates were
detected.

New TCP connection #42: 172.29.231.43(33116) <-> 172.29.228.240(5432)
42 1  0.0038 (0.0038)  C>SV3.1(300)  Handshake
 ClientHello
   Version 3.3 
   random[32]=
 80 cf 99 66 b3 07 55 c2 3f cf b2 61 13 39 89 c1 
 33 37 f4 77 21 a3 fd 2e f9 fa 9b 65 4e b5 bd 24 
   cipher suites
   Unknown value 0xc030
   Unknown value 0xc02c
   Unknown value 0xc028
   Unknown value 0xc024
   Unknown value 0xc014
   Unknown value 0xc00a
   Unknown value 0xa5
   Unknown value 0xa3
   Unknown value 0xa1
   Unknown value 0x9f
   Unknown value 0x6b
   Unknown value 0x6a
   Unknown value 0x69
   Unknown value 0x68
   TLS_DHE_RSA_WITH_AES_256_CBC_SHA
   TLS_DHE_DSS_WITH_AES_256_CBC_SHA
   TLS_DH_RSA_WITH_AES_256_CBC_SHA
   TLS_DH_DSS_WITH_AES_256_CBC_SHA
   Unknown value 0x88
   Unknown value 0x87
   Unknown value 0x86
   Unknown value 0x85
   Unknown value 0xc032
   Unknown value 0xc02e
   Unknown value 0xc02a
   Unknown value 0xc026
   Unknown value 0xc00f
   Unknown value 0xc005
   Unknown value 0x9d
   Unknown value 0x3d
   TLS_RSA_WITH_AES_256_CBC_SHA
   Unknown value 0x84
   Unknown value 0xc02f
   Unknown value 0xc02b
   Unknown value 0xc027
   Unknown value 0xc023
   Unknown value 0xc013
   Unknown value 0xc009
   Unknown value 0xa4
   Unknown value 0xa2
   Unknown value 0xa0
   Unknown value 0x9e
   TLS_DHE_DSS_WITH_NULL_SHA
   Unknown value 0x40
   Unknown value 0x3f
   Unknown value 0x3e
   TLS_DHE_RSA_WITH_AES_128_CBC_SHA
   TLS_DHE_DSS_WITH_AES_128_CBC_SHA
   TLS_DH_RSA_WITH_AES_128_CBC_SHA
   TLS_DH_DSS_WITH_AES_128_CBC_SHA
   Unknown value 0x9a
   Unknown value 0x99
   Unknown value 0x98
   Unknown value 0x97
   Unknown value 0x45
   Unknown value 0x44
   Unknown value 0x43
   Unknown value 0x42
   Unknown value 0xc031
   Unknown value 0xc02d
   Unknown value 0xc029
   Unknown value 0xc025
   Unknown value 0xc00e
   Unknown value 0xc004
   Unknown value 0x9c
   Unknown value 0x3c
   TLS_RSA_WITH_AES_128_CBC_SHA
   Unknown value 0x96
   Unknown value 0x41
   Unknown value 0xc011
   Unknown value 0xc007
   Unknown value 0xc00c
   Unknown value 0xc002
   TLS_RSA_WITH_RC4_128_SHA
   TLS_RSA_WITH_RC4_128_MD5
   Unknown value 0xc012
   Unknown value 0xc008
   TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA
   TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA
   TLS_DH_RSA_WITH_3DES_EDE_CBC_SHA
   TLS_DH_DSS_WITH_3DES_EDE_CBC_SHA
   Unknown value 0xc00d
   Unknown value 0xc003
   TLS_RSA_WITH_3DES_EDE_CBC_SHA
   Unknown value 0xff
   compression methods
 NULL
42 2  0.0056 (0.0017)  S>CV3.3(62)  Handshake
 ServerHello
   Version 3.3 
   random[32]=
 f9 4d fa 63 ee d5 65 6d ba dd 58 de 51 00 8e ac 
 9f 45 24 43 e2 17 88 07 41 9a 8d aa 7f 95 2a 13 
   session_id[0]=

   cipherSuite Unknown value 0xc030
   compressionMethod   NULL
42 3  0.0056 (0.)  S>CV3.3(3345)  Handshake
 Certificate
   certificate[1329]=[snip]
   certificate[1010]=[snip]
   certificate[990]=[snip]
42 4  0.0056 (0.)  S>CV3.3(333)  Handshake
 ServerKeyExchange
42 5  0.0056 (0.)  S>CV3.3(179)  Handshake
 CertificateRequest
   certificate_types   rsa_sign
   certificate_types   dss_sign
   certificate_types unknown value
Not enough data. Found 163 bytes (expecting 32767)
 ServerHelloDone
42 6  0.0061 (0.0004)  C>SV3.3(2)  Alert
   level   fatal
   value   unknown_ca
420.0062 (0.0001)  C>S  TCP RST

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

Title:
  TLS negation fails

Status in openssl package in Ubuntu:
  Confirmed

Bug description:
  This seems like a duplicate of #965371, however that is marked fixed,
  so I don't know.

  I'm running 16.04.1.  I'm setting up OpenLDAP with TLS.  I've followed
  the instructions at https://help.ubuntu.com/lts/serverguide/openldap-
  server.html#openldap-tls, and test with the command openssl s_client
  -connect my.server.com:389 -showcerts and I get the error:

  140668035487384:error:140790E5:SSL routines:ssl23_write:ssl handshake
  failure:s23_lib.c:177

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

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

[Touch-packages] [Bug 1612711] Re: TLS negation fails

[Graham Leggett]

Despite printing "no peer certificate available" below, the postgresql
server serves three certificates (two intermediates and a leaf) as
picked up by ssldump.

In this case it is the client side that is triggering the handshake
failure, not the server. The client side refuses to add the cause of the
handshake failure to the error message, which is definitely a bug.

postgres@sql02:~$ openssl s_client -verify 10 -CAfile .postgresql/root.crt -key 
.postgresql/postgresql.key -cert .postgresql/postgresql.crt -connect sql01:5432 
-servername sql01
verify depth is 10
CONNECTED(0003)
139930468939416:error:140790E5:SSL routines:ssl23_write:ssl handshake 
failure:s23_lib.c:177:
---
no peer certificate available
---
No client certificate CA names sent
---
SSL handshake has read 0 bytes and written 379 bytes
---
New, (NONE), Cipher is (NONE)
Secure Renegotiation IS NOT supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
SSL-Session:
Protocol  : TLSv1.2
Cipher: 
Session-ID: 
Session-ID-ctx: 
Master-Key: 
Key-Arg   : None
PSK identity: None
PSK identity hint: None
SRP username: None
Start Time: 1510188432
Timeout   : 300 (sec)
Verify return code: 0 (ok)
---

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

Title:
  TLS negation fails

Status in openssl package in Ubuntu:
  Confirmed

Bug description:
  This seems like a duplicate of #965371, however that is marked fixed,
  so I don't know.

  I'm running 16.04.1.  I'm setting up OpenLDAP with TLS.  I've followed
  the instructions at https://help.ubuntu.com/lts/serverguide/openldap-
  server.html#openldap-tls, and test with the command openssl s_client
  -connect my.server.com:389 -showcerts and I get the error:

  140668035487384:error:140790E5:SSL routines:ssl23_write:ssl handshake
  failure:s23_lib.c:177

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

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

[Touch-packages] [Bug 1612711] Re: TLS negation fails

[Graham Leggett]

I am seeing the exact same bug, only with the server being postgresql
instead of openldap.

The same setup and certificates works fine on Trusty, but have regressed
on Xenial.

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

Title:
  TLS negation fails

Status in openssl package in Ubuntu:
  Confirmed

Bug description:
  This seems like a duplicate of #965371, however that is marked fixed,
  so I don't know.

  I'm running 16.04.1.  I'm setting up OpenLDAP with TLS.  I've followed
  the instructions at https://help.ubuntu.com/lts/serverguide/openldap-
  server.html#openldap-tls, and test with the command openssl s_client
  -connect my.server.com:389 -showcerts and I get the error:

  140668035487384:error:140790E5:SSL routines:ssl23_write:ssl handshake
  failure:s23_lib.c:177

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

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

[Touch-packages] [Bug 1612711] Re: TLS negation fails

[Launchpad Bug Tracker]

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

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

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

Title:
  TLS negation fails

Status in openssl package in Ubuntu:
  Confirmed

Bug description:
  This seems like a duplicate of #965371, however that is marked fixed,
  so I don't know.

  I'm running 16.04.1.  I'm setting up OpenLDAP with TLS.  I've followed
  the instructions at https://help.ubuntu.com/lts/serverguide/openldap-
  server.html#openldap-tls, and test with the command openssl s_client
  -connect my.server.com:389 -showcerts and I get the error:

  140668035487384:error:140790E5:SSL routines:ssl23_write:ssl handshake
  failure:s23_lib.c:177

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

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

[Touch-packages] [Bug 1719720] Re: [LTCTest][libvpd] Process '/bin/touch /run/run.vpdupdate' failed with exit code 127

[Michael Hudson-Doyle]

I tried and failed to reproduce this in an artful vm:

ubuntu@mwhudson-artful:~$ cat /etc/udev/rules.d/my.rules
KERNELS=="*", ACTION=="*", DEVPATH=="/devices/*", RUN+="/bin/touch /run/my-file"
ubuntu@mwhudson-artful:~$ sudo rm -f /run/my-file
ubuntu@mwhudson-artful:~$ sudo udevadm trigger 
/sys/devices/pci:00/:00:03.0/virtio2/block/vdb/vdb1
ubuntu@mwhudson-artful:~$ ls -l /run/my-file
-rw-r--r-- 1 root root 0 Nov  8 23:53 /run/my-file

(and there are no interesting messages in syslog when I do this).

Is the bug still affecting you? It's possible it got fixed in systemd or
somewhere else in the meantime.

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

Title:
  [LTCTest][libvpd] Process '/bin/touch /run/run.vpdupdate' failed with
  exit code 127

Status in The Ubuntu-power-systems project:
  Triaged
Status in coreutils package in Ubuntu:
  Triaged

Bug description:
  ---Problem Description---
  Currently syslog is getting flooded with below log messages ..
  Sep 25 03:16:41 ubuntu1710 systemd-udevd[2654]: Process '/bin/touch 
/run/run.vpdd
  update' failed with exit code 127.

  This is on UBuntu 17.10 latest build.. 
   
  ---uname output---
  Linux ubuntu1710 4.12.0-11-generic #12-Ubuntu SMP Fri Aug 11 12:23:06 UTC 
2017 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = ZZ-L 

  ---Steps to Reproduce---
   I have seen these messages logged more often when we do any hotplug 
operations.. ex. cpu hotplug..

  Ok. .this is the continuation of LTC #144627 / Launchpad #1682774.

  As suggested in that bug, we did change udev script to create
  temporary file under /run and that patch is available in ubuntu 17.10.

  Looks like this is udev script issue. If I modify systemd-udevd like
  below it works fine.

  I've limited udev knowledge. I don't know if you have any other better
  solution to this issue.

  root@ltc-boston123:/lib/systemd/system# diff -Naurp  
systemd-udevd.service.org systemd-udevd.service
  --- systemd-udevd.service.org 2017-09-26 04:37:47.090057318 -0500
  +++ systemd-udevd.service 2017-09-26 04:37:55.381739372 -0500
  @@ -25,7 +25,7 @@ KillMode=mixed
   WatchdogSec=3min
   TasksMax=infinity
   MountFlags=slave
  -MemoryDenyWriteExecute=yes
  +#MemoryDenyWriteExecute=yes
   RestrictRealtime=yes
   RestrictAddressFamilies=AF_UNIX AF_NETLINK AF_INET AF_INET6
   SystemCallArchitectures=native

  
  -Vasant

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

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

[Touch-packages] [Bug 1731073] Re: package lsb-invalid-mta 9.20160110ubuntu0.2 failed to install/upgrade: package lsb-invalid-mta is not ready for configuration cannot configure (current status 'half-

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package lsb-invalid-mta 9.20160110ubuntu0.2 failed to install/upgrade:
  package lsb-invalid-mta is not ready for configuration  cannot
  configure (current status 'half-installed')

Status in lsb package in Ubuntu:
  New

Bug description:
  Received error while attempting to install update after downloading
  from Ubuntu Software.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: lsb-invalid-mta 9.20160110ubuntu0.2
  ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  AptOrdering:
   resolvconf: Install
   lsb-invalid-mta: Configure
   resolvconf: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Wed Nov  8 18:41:06 2017
  Dependencies:
   
  DuplicateSignature:
   package:lsb-invalid-mta:9.20160110ubuntu0.2
   Processing triggers for systemd (229-4ubuntu21) ...
   dpkg: error processing package lsb-invalid-mta (--configure):
package lsb-invalid-mta is not ready for configuration
  ErrorMessage: package lsb-invalid-mta is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2017-10-03 (36 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: lsb
  Title: package lsb-invalid-mta 9.20160110ubuntu0.2 failed to install/upgrade: 
package lsb-invalid-mta is not ready for configuration  cannot configure 
(current status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1731073] [NEW] package lsb-invalid-mta 9.20160110ubuntu0.2 failed to install/upgrade: package lsb-invalid-mta is not ready for configuration cannot configure (current status 'hal

[Rick]

Public bug reported:

Received error while attempting to install update after downloading from
Ubuntu Software.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: lsb-invalid-mta 9.20160110ubuntu0.2
ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-38-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.10
AptOrdering:
 resolvconf: Install
 lsb-invalid-mta: Configure
 resolvconf: Configure
 NULL: ConfigurePending
Architecture: amd64
Date: Wed Nov  8 18:41:06 2017
Dependencies:
 
DuplicateSignature:
 package:lsb-invalid-mta:9.20160110ubuntu0.2
 Processing triggers for systemd (229-4ubuntu21) ...
 dpkg: error processing package lsb-invalid-mta (--configure):
  package lsb-invalid-mta is not ready for configuration
ErrorMessage: package lsb-invalid-mta is not ready for configuration  cannot 
configure (current status 'half-installed')
InstallationDate: Installed on 2017-10-03 (36 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: lsb
Title: package lsb-invalid-mta 9.20160110ubuntu0.2 failed to install/upgrade: 
package lsb-invalid-mta is not ready for configuration  cannot configure 
(current status 'half-installed')
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  package lsb-invalid-mta 9.20160110ubuntu0.2 failed to install/upgrade:
  package lsb-invalid-mta is not ready for configuration  cannot
  configure (current status 'half-installed')

Status in lsb package in Ubuntu:
  New

Bug description:
  Received error while attempting to install update after downloading
  from Ubuntu Software.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: lsb-invalid-mta 9.20160110ubuntu0.2
  ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  AptOrdering:
   resolvconf: Install
   lsb-invalid-mta: Configure
   resolvconf: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Wed Nov  8 18:41:06 2017
  Dependencies:
   
  DuplicateSignature:
   package:lsb-invalid-mta:9.20160110ubuntu0.2
   Processing triggers for systemd (229-4ubuntu21) ...
   dpkg: error processing package lsb-invalid-mta (--configure):
package lsb-invalid-mta is not ready for configuration
  ErrorMessage: package lsb-invalid-mta is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2017-10-03 (36 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: lsb
  Title: package lsb-invalid-mta 9.20160110ubuntu0.2 failed to install/upgrade: 
package lsb-invalid-mta is not ready for configuration  cannot configure 
(current status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1592721] Re: Don't write search domains to resolv.conf in the case of split DNS

[Caleb]

Yes, please bring to 16.04

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

Title:
  Don't write search domains to resolv.conf in the case of split DNS

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  All VPN users meaning to use split-tunnelling in a situation where leaking 
DNS data to the internet about what might be behind their VPN is undesirable.

  [Test case]
  1) connect to VPN
  2) Use dig to request a name that should be on the VPN
  3) Verify (kill -USR1 the dnsmasq binary from NM) that the request has only 
gone through the VPN nameservers (only its request number should have increased 
by one)
  4) Use dig to request a name off-VPN, such as google.com.
  5) Verify (kill -USR1 again) that the request has caused the non-VPN 
nameserver request number to increase, and that the VPN number has not 
increased.

  It is easier to verify this when there is as little traffic as
  possible on the system, to avoid spurious DNS requests which would
  make it harder to validate the counters.

  [Regression potential]
  This change modifies the way in which DNS nameservers and search domains are 
passed to dnsmasq, as such, if a VPN is configured in a non-standard way and 
intended to be used to resolve all network requests (which is typically not the 
case for split-tunnelling) or if the public network is intended to always 
resolve all requests while the VPN still provides search domains, one might 
observe incorrect behavior.

  Possible failure cases would include failure to resolve names
  correctly (resulting in NXDOMAIN or REFUSED from dnsmasq) or resolving
  to the incorrect values (if the wrong nameserver is used).

  ---

  Currently, NM will write all search domains to both any DNS-handling
  plugins running, and also to resolv.conf / resolvconf; in all cases.

  The issue is that doing so means that in the split-DNS case on VPNs,
  you might get a negative response from all nameservers, then a new
  request by glibc with the search tacked on, to nameservers again,
  which might cause DNS requests for "private" resources (say, on the
  VPN) to be sent to external, untrusted resolvers, or for DNS queries
  not meant for VPN nameservers to be sent through the VPN anyway.

  This is fixable in the case where we have a caching plugin running
  (such as dnsmasq). dnsmasq will already know about the search domains
  and use that to limit queries to the right nameservers when a VPN is
  running. Writing search domains to resolv.conf is unnecessary in this
  case.

  We should still write search domains if no caching gets done, as we
  then need to expect glibc to send requests as it otherwise would.

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

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

[Touch-packages] [Bug 1731068] [NEW] With NVIDIA proprietary drivers, initial login screan appears only on mouse movement

[Michal Bultrowicz]

Public bug reported:

After installing the proprietary NVIDIA driver (384) I've been faced
with a black screen after reboot. It turned out, that when I moved the
mouse, the login screen appeared. The screen goes black immediately when
I stop moving the mouse. I can normally put the password in on the black
screen and go on with my life, but, you know, it doesn't look stable :)

After I get the system up from sleeping (which didn't work earlier but
suddenly started working) the log in screen in displayed normally.

My system (Alienware 15 R3) has Intel's i7-7820HK and NVIDIA's GeForce
GTX 1070 Mobile 8GB

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.90  Tue Sep 19 19:17:35 
PDT 2017
 GCC version:  gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3)
.proc.driver.nvidia.warnings.fbdev:
 Your system is not currently configured to drive a VGA console
 on the primary VGA device. The NVIDIA Linux graphics driver
 requires the use of a text-mode VGA console. Use of other console
 drivers including, but not limited to, vesafb, may result in
 corruption and stability problems, and is not supported.
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
BootLog: /dev/sda2: clean, 200420/61046784 files, 6117516/244157440 blocks
CompositorRunning: None
CurrentDesktop: KDE
Date: Wed Nov  8 23:43:20 2017
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: kubuntu
DkmsStatus:
 bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed
 nvidia-384, 384.90, 4.13.0-16-generic, x86_64: installed
ExtraDebuggingInterest: No
GraphicsCard:
 Subsystem: Dell Device [1028:0774]
 NVIDIA Corporation GP104M [GeForce GTX 1070 Mobile] [10de:1be1] (rev a1) 
(prog-if 00 [VGA controller])
   Subsystem: Dell GP104M [GeForce GTX 1070 Mobile] [1028:07c0]
InstallationDate: Installed on 2017-11-04 (4 days ago)
InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 0bda:58c2 Realtek Semiconductor Corp. 
 Bus 001 Device 003: ID 0cf3:e300 Atheros Communications, Inc. 
 Bus 001 Device 002: ID 187c:0530 Alienware Corporation 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Alienware Alienware 15 R3
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=32edfbb9-d0bb-495a-9313-48b5ee124d2b ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/09/2017
dmi.bios.vendor: Alienware
dmi.bios.version: 1.1.8
dmi.board.name: Alienware 15 R3
dmi.board.vendor: Alienware
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Alienware
dmi.chassis.version: Not Specified
dmi.modalias: 
dmi:bvnAlienware:bvr1.1.8:bd06/09/2017:svnAlienware:pnAlienware15R3:pvr1.1.8:rvnAlienware:rnAlienware15R3:rvrA00:cvnAlienware:ct10:cvrNotSpecified:
dmi.product.family: Alienware
dmi.product.name: Alienware 15 R3
dmi.product.version: 1.1.8
dmi.sys.vendor: Alienware
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug artful kubuntu

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

Title:
  With NVIDIA proprietary drivers, initial login screan appears only on
  mouse movement

Status in xorg package in Ubuntu:
  New

Bug description:
  After installing the proprietary NVIDIA driver (384) I've been faced
  with a black screen after reboot. It turned out, that when I moved the
  mouse, the login screen appeared. The screen goes black immediately
  when I stop moving the mouse. I can normally put the password in on
  the black screen and go on with my life, but, you know, it doesn't
  look stable :)

  After I get the system up from sleeping (which didn't work earlier but
  suddenly started working) the log in screen in displayed normally.

  My system 

[Touch-packages] [Bug 1620636] Re: Fails to pair with Bose QC35 headphones

[Letatcest]

@p7ter thanks, I wasn't aware. No need to look further then ;) In that
case I have no bug to report (and will retract my bug report as it
connects smoothly to my 16.04 desktop and 17.10 laptop without any
changes to bt files).

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

Title:
  Fails to pair with Bose QC35 headphones

Status in Canonical System Image:
  In Progress
Status in bluez package in Ubuntu:
  In Progress

Bug description:
  I am unable to pair the Bose QC35 BT headphones with Ubuntu, either
  Ubuntu desktop running 16.04 LTS with bluez 5.37 (also tried bluez
  5.41 from installed from yakkety archive), nor using Ubuntu Touch rc-
  proposed build for Turbo #174. I'm trying to pair through the normal
  bluetooth control panel brought up through the bluetooth indicator.

  I've attached some logs that show it failing to pair. If I can provide
  anymore useful information about the headphones, please let me know.

  Syslog with bluetoothd debugging enabled:
  http://pastebin.ubuntu.com/23141394/

  btmon output:
  http://pastebin.ubuntu.com/23141446/

  bluetoothctl output:
  http://pastebin.ubuntu.com/23141510/

  With Linux kernel 4.8.0 and bluez 4.52:
  ---

  bluetoothctl: http://pastebin.ubuntu.com/23256457/
  btmon: http://pastebin.ubuntu.com/23256471/

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1620636/+subscriptions

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

[Touch-packages] [Bug 1720890] Re: vulkan-smoketest segfaults steam vulkan games segfault

[Lawrence A Fossi]

I added the ppa vulkan-smoketest now runs correctly as well as The Talos
Principle. Just one issue left vulkaninfo shows an elf class error on
both of the mesa-vulkan-drivers:i386 packages

** Attachment added: "apt-cache policy and full vulkaninfo"
   
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1720890/+attachment/5006110/+files/Updated%20Vulkan%20Info%2017.2.4%20testing

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

Title:
  vulkan-smoketest segfaults steam vulkan games segfault

Status in mesa package in Ubuntu:
  In Progress
Status in mesa source package in Xenial:
  New
Status in mesa source package in Artful:
  New

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  $ apt-cache policy mesa-vulkan-drivers
  mesa-vulkan-drivers:
Installed: 17.2.1-0ubuntu1
Candidate: 17.2.1-0ubuntu1
Version table:
   *** 17.2.1-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu artful/universe amd64 Packages
  100 /var/lib/dpkg/status

  
  Easily reproducible : apt-get install mesa-vulkan-drivers apt-get install 
vulkan-utils

  Open a terminal type vulkan-smoketest instead of a glxgears type window it 
will segfault.
  message from kernel.log:
  Sep 29 16:23:53 Tardis-1 kernel: [17709.532915] vulkan-smoketes[11798]: 
segfault at 0 ip 7fed61a17914 sp 7ffedcb8f850 error 6 in 
libvulkan_radeon.so[7fed619ab000+18b000]
  syslog:
  Sep 28 10:38:13 Tardis-1 kernel: [18292.174313] vulkan-smoketes[13385]: 
segfault at 0 ip 7f62705a7914 sp 7ffd0edc6260 error 6 in 
libvulkan_radeon.so[7f627053b000+18b000]

  What should happen is a glxgears like window will open and render properly 
instead of segfaulting.
  It appears that the culprit is an old or broken libvulkan_radeon.so provided 
by mesa-vulkan-drivers.

  As a test I renamed the old lib and dropped in a newer version from
  oibaf's ppa. smoketest now passes steam's The Talos Princible and Mad
  Max now work properly in Vulkan mode as well instead of segfaulting.

  This issue is also present on Zesty and fixed in both Oibaf's and
  Padoka's ppa's since April back when they were rolling 17.2 mesa.

  I have no idea if libvulkan_intel.so also needs updating no hardware
  to check.

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

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

[Touch-packages] [Bug 1712921] Re: enabling networkd appears to eat up entropy

[Mathieu Trudel-Lapierre]

** Description changed:

+ [Impact]
+ Booting systems have a limited amount of entropy, especially in some of the 
cloud cases. We should avoid using it up unnecessarily.
+ 
+ [Test cases]
+ 
+ == netplan ==
+ 1) Boot system with netplan config; using networkd renderer
+ 2) Validate that it starts and does not cause undue delay.
+ 2b) strace nplan at boottime (the netplan generator at 
/lib/systemd/system-generators/netplan) and validate it does not call 
get_random() / uuid_generate().
+ 3) Validate that config with NetworkManager renderer generates UUIDs.
+ 
+ [Regression potential]
+ Netplan depends on UUID generation to create correct networkManager 
configuration for VLANs. This is a specific use-case that is typically not hit, 
but any failure to generate valid NetworkManager configuration would be a 
regression from this SRU.
+ 
+ ---
+ 
  enabling networkd appears to eat up entropy
  
  as seen in openssh autopkgtest failing, when networkd is enabled by
  default.
  
  See http://autopkgtest.ubuntu.com/packages/openssh/artful/amd64 with
  triggers systemd/234-2ubuntu9

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

Title:
  enabling networkd appears to eat up entropy

Status in nplan package in Ubuntu:
  In Progress
Status in openssh package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Triaged
Status in nplan source package in Xenial:
  New
Status in openssh source package in Xenial:
  New
Status in systemd source package in Xenial:
  New
Status in nplan source package in Zesty:
  New
Status in openssh source package in Zesty:
  New
Status in systemd source package in Zesty:
  New
Status in nplan source package in Artful:
  In Progress
Status in openssh source package in Artful:
  Fix Released
Status in systemd source package in Artful:
  Triaged
Status in nplan source package in Bionic:
  In Progress
Status in openssh source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Triaged

Bug description:
  [Impact]
  Booting systems have a limited amount of entropy, especially in some of the 
cloud cases. We should avoid using it up unnecessarily.

  [Test cases]

  == netplan ==
  1) Boot system with netplan config; using networkd renderer
  2) Validate that it starts and does not cause undue delay.
  2b) strace nplan at boottime (the netplan generator at 
/lib/systemd/system-generators/netplan) and validate it does not call 
get_random() / uuid_generate().
  3) Validate that config with NetworkManager renderer generates UUIDs.

  [Regression potential]
  Netplan depends on UUID generation to create correct networkManager 
configuration for VLANs. This is a specific use-case that is typically not hit, 
but any failure to generate valid NetworkManager configuration would be a 
regression from this SRU.

  ---

  enabling networkd appears to eat up entropy

  as seen in openssh autopkgtest failing, when networkd is enabled by
  default.

  See http://autopkgtest.ubuntu.com/packages/openssh/artful/amd64 with
  triggers systemd/234-2ubuntu9

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

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

[Touch-packages] [Bug 1696415] Re: NetworkManager does not update IPv4 address lifetime even though DHCP lease was successfully renewed

[Ray Link]

Correction/Addendum to the SRU justification above:

Fixed in current Ubuntu.  Bionic uses NM 1.8.x.  This bug was fixed in
1.4.

[Impact]

* This LP bug's original submitter backported the upstream 1.4 fix to
1.2, not Upstream.

[Regression Potential]

* The patch changes both nm-dhcp-helper and NetworkManager itself.  As
soon as the new packages are unpacked, the new nm-dhcp-helper will be
used on DHCP lease renewals, with the new Notify mechanism.  Since the
running, old NetworkManager is still expecting Event notifications, the
patched nm-dhcp-helper has fallback capability to Event.

* Once NetworkManager is restarted and is running the patched version,
it will have the new Notify support.

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

Title:
  NetworkManager does not update IPv4 address lifetime even though DHCP
  lease was successfully renewed

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I've found an issue on some of our Xenial office machines, causing
  NetworkManager to drop its IP address lease in some cases when it
  shouldn't. I'm not sure if the actual bug is in NetworkManager or
  perhaps dbus or dhclient, but I'll do my best to help to figure out
  where it is.

  What appears to happen:
  * NetworkManager is informed of a new IPv4 lease.
  * During the lease, dhclient keeps it fresh by renewing it using DHCPREQUESTs 
regularly.
  * In spite of this, NetworkManager drops the IP address from the interface 
when the last reported lease time expires.

  This happens on various machines, once every few days. We are using a
  failover DHCP configuration using two machines (192.168.0.3 'bonaire'
  and 192.168.0.4 'curacao').



  The machine where I've done the debugging is called 'pampus'
  (192.168.0.166). As you can see in the logs, at 01:21:06
  NetworkManager reports a new lease with lease time 7200.

  jun 07 01:21:06 pampus dhclient[1532]: DHCPREQUEST of 192.168.0.166 on eth0 
to 192.168.0.4 port 67 (xid=0x3295b440)
  jun 07 01:21:06 pampus dhclient[1532]: DHCPACK of 192.168.0.166 from 
192.168.0.4
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
address 192.168.0.166
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   plen 
24 (255.255.255.0)
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
gateway 192.168.0.5
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
server identifier 192.168.0.4
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
lease time 7200
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
nameserver '192.168.0.3'
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
nameserver '192.168.0.4'
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
domain name 'office.screenpointmed.com'
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9531] dhcp4 
(eth0): state changed bound -> bound

  After this, dhclient is supposed to keep the lease fresh, which it
  does. E.g. at 03:13:19 you can see a DHCPREQUEST and DHCPACK; I've
  seen this DHCPACK in a tcpdump and it contains a new lease time of
  7200 seconds.

  jun 07 03:13:19 pampus dhclient[1532]: DHCPREQUEST of 192.168.0.166 on eth0 
to 192.168.0.4 port 67 (xid=0x3295b440)
  jun 07 03:13:19 pampus dhclient[1532]: DHCPACK of 192.168.0.166 from 
192.168.0.4
  jun 07 03:13:19 pampus dhclient[1532]: bound to 192.168.0.166 -- renewal in 
2708 seconds.

  However, at 03:21:07 (exactly 2 hours and 1 second after the last
  lease reported by NetworkManager) Avahi and NTP report that the IP
  address is gone:

  jun 07 03:21:07 pampus avahi-daemon[1167]: Withdrawing address record for 
192.168.0.166 on eth0.
  jun 07 03:21:07 pampus avahi-daemon[1167]: Leaving mDNS multicast group on 
interface eth0.IPv4 with address 192.168.0.166.
  jun 07 03:21:07 pampus avahi-daemon[1167]: Interface eth0.IPv4 no longer 
relevant for mDNS.
  jun 07 03:21:08 pampus ntpd[18832]: Deleting interface #3 eth0, 
192.168.0.166#123, interface stats: received=2512, sent=2549, dropped=0, 
active_time=111819 secs

  So I suspect NetworkManager dropped the IP address from the interface,
  because it wasn't informed by dhclient that the lease was renewed. The
  logs don't explicitly say this, so I may have to turn on more verbose
  debugging logs in NetworkManager or dhclient to verify this.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.6-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Wed Jun  7 14:48:59 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) 

[Touch-packages] [Bug 1720541] Re: flock does not lock dpkg lock file properly

[Phillip Susi]

lockfile from the procmail package will do it.


** Changed in: util-linux (Ubuntu)
   Status: New => Invalid

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

Title:
  flock does not lock dpkg lock file properly

Status in util-linux package in Ubuntu:
  Invalid

Bug description:
  Test:
  sudo flock /var/lib/dpkg/lock -c \
  'echo 1; apt-get -o Debug::NoLocking=true check; echo 2; apt-get check'

  Expected behavior:
  apt-get fails in stage 2.

  
  Workaround (needs moreutils package, which is not installed by default):

  sudo lckdo /var/lib/dpkg/lock /bin/sh -c \
  'echo 1; apt-get -o Debug::NoLocking=true check; echo 2; apt-get check'

  
  Similarly, flock does not recognize lock set by e.g. apt-get.

  man lckdo:
  "Now that util-linux contains a similar command named flock, lckdo is 
deprecated, and will be removed from some  future version of moreutils."

  So developer can not rely on lckdo.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: util-linux 2.20.1-5.1ubuntu20.9
  ProcVersionSignature: Ubuntu 4.4.0-96.119~14.04.1-generic 4.4.83
  Uname: Linux 4.4.0-96-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.25
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Sep 30 16:30:50 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-09-21 (1105 days ago)
  InstallationMedia: Ubuntu-Studio 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.1)
  SourcePackage: util-linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.cron.weekly.fstrim: 2014-09-21T13:07:51.420447

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

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

[Touch-packages] [Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

[Scott Moser]

** Attachment added: "one more try at reproduce script."
   
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1711760/+attachment/5006069/+files/lp-1711760-test.sh

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

Title:
  [2.3] resolv.conf is not set (during commissioning or testing)

Status in MAAS:
  Fix Released
Status in resolvconf package in Ubuntu:
  Won't Fix
Status in resolvconf source package in Trusty:
  Fix Committed
Status in resolvconf source package in Xenial:
  Fix Released

Bug description:
  === Begin SRU Template ===
  [Impact]
  Without this fix applied, dns settings provided to the dhcp response
  in the initramfs are not reflected in the "real root".

  Thus dns resolution does not work. Of most interest was the MAAS use
  case of the 'root=http://<>/squashfs' use case.

  MAAS 2.3 uses this for the installation environment and also the rescue
  environment.  In most cases the 14.04 specific fix will only apply
  to installation as 16.04 is most likely to be used in rescue mode.

  [Test Case]
  There are two tests for this.

  a.) local/non-MAAS test
  Download the test case attached.
  Run it and follow the instructions.
  Login to the guest (ubuntu:password), and inspect /etc/resolv.conf
  without the fix there would be no data in /etc/resolv.conf.  With the
  fix you should see 'nameserver 10.0.2.2' and 'search mydomain.com bar.com'

  b.) MAAS test.
  For the full maas test, you need to build a image stream for maas
  with the fix included in the squashfs image and then import that
  stream to maas and use the rescue environment and verify dns.
  This process is beyond the scope of the SRU template, but is
  described partially in
    
http://bazaar.launchpad.net/~maas-images-maintainers/maas-images/maas-ephemerals/view/head:/README

  [Regression Potential]
  Regression potential should be very low.  There are gates in the code
  to make sure that this code is inactive other than when it is explicitly
  enabled.

  net-interface-handler will exit without doing anything unless:
  a.) there exist files /run/net-$INTERFACE.conf or /run/net6-$INTERFACE.conf
  and these files have non-empty values for a variable mentioned above.
  (These files are written by the initramfs code when 'ip=' is seen).

  b.) this is not a container.
trusty uses 'running-in-container' to determine this.
xenial uses 'systemd-detect-virt'

  c.) there is no OPENISCSI_MARKER file (/run/initramfs/open-iscsi.interface)
  if open-iscsi has written this file due to open-iscsi root, then it
  will handle this functionality. resolvconf will get out of the way.

  d.) /proc/cmdline contains cloud-config-url=* or 'rc-initrd-dns'
  This lowers the scope of changes in runtime to cases with where either the
  new flag is seen or cloud-config-url is passed. The MAAS use case will
  contain this flag.

  [Other Info]

  === End SRU Template ===

  Using MAAS 2.3, during commissioning (and likely in the rest of the
  ephemeral environment) we have noticed that resolv.conf is not set
  with the DNS server.

  That said, during the commissioning process, MAAS does not send any
  metadata to cloud-init to configure the network, rather, we expect the
  image to boot from the network via DHCP. So, cloud-init writes:

  ubuntu@manual:~$ cat /etc/network/interfaces.d/50-cloud-init.cfg
  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  auto lo
  iface lo inet loopback

  # control-manual ens3
  iface ens3 inet dhcp
  broadcast 192.168.122.255
  dns-nameservers 192.168.122.2
  gateway 192.168.122.1
  netmask 255.255.255.0

  Which correctly includes the DNS server. However:

  ubuntu@manual:~$ ping google.com
  ping: unknown host google.com

  If restart the interfacE:

  ubuntu@manual:~$ sudo ifdown ens3 && sudo ifup ens3
  ifdown: interface ens3 not configured
  Internet Systems Consortium DHCP Client 4.3.3
  Copyright 2004-2015 Internet Systems Consortium.
  All rights reserved.
  For info, please visit https://www.isc.org/software/dhcp/

  Listening on LPF/ens3/52:54:00:ea:57:31
  Sending on   LPF/ens3/52:54:00:ea:57:31
  Sending on   Socket/fallback
  DHCPDISCOVER on ens3 to 255.255.255.255 port 67 interval 3 (xid=0x14eb0354)
  DHCPDISCOVER on ens3 to 255.255.255.255 port 67 interval 4 (xid=0x14eb0354)
  DHCPREQUEST of 192.168.122.195 on ens3 to 255.255.255.255 port 67 
(xid=0x5403eb14)
  DHCPOFFER of 192.168.122.195 from 192.168.122.2
  DHCPACK of 192.168.122.195 from 192.168.122.2
  Restarting ntp (via systemctl): ntp.service.
  bound to 192.168.122.195 -- renewal in 290 seconds.

  

[Touch-packages] [Bug 1696415] Re: NetworkManager does not update IPv4 address lifetime even though DHCP lease was successfully renewed

[Ray Link]

[Impact]

 * nm-dhcp-helper sometimes fails to notify NetworkManager of a DHCP
   lease renewal due to a DBus race condition.

 * Upstream NetworkManager 1.4 fixes the race condition by changing
   nm-dhcp-helper's DBus notification from signal "Event" to method
   "Notify".

 * Upstream backported NM 1.4's nm-dhcp-helper notification fix to
   NM 1.2.  This SRU request applies that backported patch to Xenial's
   NM 1.2.x.

[Test Case]

 * Not reliably reproducible.  Out of hudreds of machines, only a
   dozen or so fail to notify NetworkManager of a DHCP lease
   renewal about 30-50% of the time.  (i.e. It's always the same
   handful of machines that fail.)

 * All such machines with the patched packages have been fine for weeks,
   over many dozens of lease renewals.

[Regression Potential]

 * Minimal.  Upstream's patch falls back to the former behavior if the
   new behavior is not supported or times out.

[Other Info]

 * Upstream bug w/ patch:
https://bugzilla.gnome.org/show_bug.cgi?id=784636

 * RHEL bug with links to the 1.4 commits from which the patch was
   derived: https://bugzilla.redhat.com/show_bug.cgi?id=1373276

** Bug watch added: Red Hat Bugzilla #1373276
   https://bugzilla.redhat.com/show_bug.cgi?id=1373276

** Patch added: "nm-dhcp-helper.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1696415/+attachment/5006066/+files/nm-dhcp-helper.debdiff

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

Title:
  NetworkManager does not update IPv4 address lifetime even though DHCP
  lease was successfully renewed

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I've found an issue on some of our Xenial office machines, causing
  NetworkManager to drop its IP address lease in some cases when it
  shouldn't. I'm not sure if the actual bug is in NetworkManager or
  perhaps dbus or dhclient, but I'll do my best to help to figure out
  where it is.

  What appears to happen:
  * NetworkManager is informed of a new IPv4 lease.
  * During the lease, dhclient keeps it fresh by renewing it using DHCPREQUESTs 
regularly.
  * In spite of this, NetworkManager drops the IP address from the interface 
when the last reported lease time expires.

  This happens on various machines, once every few days. We are using a
  failover DHCP configuration using two machines (192.168.0.3 'bonaire'
  and 192.168.0.4 'curacao').



  The machine where I've done the debugging is called 'pampus'
  (192.168.0.166). As you can see in the logs, at 01:21:06
  NetworkManager reports a new lease with lease time 7200.

  jun 07 01:21:06 pampus dhclient[1532]: DHCPREQUEST of 192.168.0.166 on eth0 
to 192.168.0.4 port 67 (xid=0x3295b440)
  jun 07 01:21:06 pampus dhclient[1532]: DHCPACK of 192.168.0.166 from 
192.168.0.4
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
address 192.168.0.166
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   plen 
24 (255.255.255.0)
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
gateway 192.168.0.5
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
server identifier 192.168.0.4
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
lease time 7200
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
nameserver '192.168.0.3'
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
nameserver '192.168.0.4'
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
domain name 'office.screenpointmed.com'
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9531] dhcp4 
(eth0): state changed bound -> bound

  After this, dhclient is supposed to keep the lease fresh, which it
  does. E.g. at 03:13:19 you can see a DHCPREQUEST and DHCPACK; I've
  seen this DHCPACK in a tcpdump and it contains a new lease time of
  7200 seconds.

  jun 07 03:13:19 pampus dhclient[1532]: DHCPREQUEST of 192.168.0.166 on eth0 
to 192.168.0.4 port 67 (xid=0x3295b440)
  jun 07 03:13:19 pampus dhclient[1532]: DHCPACK of 192.168.0.166 from 
192.168.0.4
  jun 07 03:13:19 pampus dhclient[1532]: bound to 192.168.0.166 -- renewal in 
2708 seconds.

  However, at 03:21:07 (exactly 2 hours and 1 second after the last
  lease reported by NetworkManager) Avahi and NTP report that the IP
  address is gone:

  jun 07 03:21:07 pampus avahi-daemon[1167]: Withdrawing address record for 
192.168.0.166 on eth0.
  jun 07 03:21:07 pampus avahi-daemon[1167]: Leaving mDNS multicast group on 
interface eth0.IPv4 with address 192.168.0.166.
  jun 07 03:21:07 pampus avahi-daemon[1167]: Interface eth0.IPv4 no longer 
relevant for mDNS.
  jun 07 03:21:08 pampus ntpd[18832]: Deleting interface #3 eth0, 
192.168.0.166#123, interface stats: received=2512, sent=2549, dropped=0, 

[Touch-packages] [Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

[Scott Moser]

testing showed that I uploaded a bad version.
Fixed in a new upload
https://launchpadlibrarian.net/345007871/resolvconf_1.69ubuntu1.3_source.changes

** Tags removed: verification-needed verification-needed-trusty
** Tags added: verification-failed verification-failed-trusty

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

Title:
  [2.3] resolv.conf is not set (during commissioning or testing)

Status in MAAS:
  Fix Released
Status in resolvconf package in Ubuntu:
  Won't Fix
Status in resolvconf source package in Trusty:
  Fix Committed
Status in resolvconf source package in Xenial:
  Fix Released

Bug description:
  === Begin SRU Template ===
  [Impact]
  Without this fix applied, dns settings provided to the dhcp response
  in the initramfs are not reflected in the "real root".

  Thus dns resolution does not work. Of most interest was the MAAS use
  case of the 'root=http://<>/squashfs' use case.

  MAAS 2.3 uses this for the installation environment and also the rescue
  environment.  In most cases the 14.04 specific fix will only apply
  to installation as 16.04 is most likely to be used in rescue mode.

  [Test Case]
  There are two tests for this.

  a.) local/non-MAAS test
  Download the test case attached.
  Run it and follow the instructions.
  Login to the guest (ubuntu:password), and inspect /etc/resolv.conf
  without the fix there would be no data in /etc/resolv.conf.  With the
  fix you should see 'nameserver 10.0.2.2' and 'search mydomain.com bar.com'

  b.) MAAS test.
  For the full maas test, you need to build a image stream for maas
  with the fix included in the squashfs image and then import that
  stream to maas and use the rescue environment and verify dns.
  This process is beyond the scope of the SRU template, but is
  described partially in
    
http://bazaar.launchpad.net/~maas-images-maintainers/maas-images/maas-ephemerals/view/head:/README

  [Regression Potential]
  Regression potential should be very low.  There are gates in the code
  to make sure that this code is inactive other than when it is explicitly
  enabled.

  net-interface-handler will exit without doing anything unless:
  a.) there exist files /run/net-$INTERFACE.conf or /run/net6-$INTERFACE.conf
  and these files have non-empty values for a variable mentioned above.
  (These files are written by the initramfs code when 'ip=' is seen).

  b.) this is not a container.
trusty uses 'running-in-container' to determine this.
xenial uses 'systemd-detect-virt'

  c.) there is no OPENISCSI_MARKER file (/run/initramfs/open-iscsi.interface)
  if open-iscsi has written this file due to open-iscsi root, then it
  will handle this functionality. resolvconf will get out of the way.

  d.) /proc/cmdline contains cloud-config-url=* or 'rc-initrd-dns'
  This lowers the scope of changes in runtime to cases with where either the
  new flag is seen or cloud-config-url is passed. The MAAS use case will
  contain this flag.

  [Other Info]

  === End SRU Template ===

  Using MAAS 2.3, during commissioning (and likely in the rest of the
  ephemeral environment) we have noticed that resolv.conf is not set
  with the DNS server.

  That said, during the commissioning process, MAAS does not send any
  metadata to cloud-init to configure the network, rather, we expect the
  image to boot from the network via DHCP. So, cloud-init writes:

  ubuntu@manual:~$ cat /etc/network/interfaces.d/50-cloud-init.cfg
  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  auto lo
  iface lo inet loopback

  # control-manual ens3
  iface ens3 inet dhcp
  broadcast 192.168.122.255
  dns-nameservers 192.168.122.2
  gateway 192.168.122.1
  netmask 255.255.255.0

  Which correctly includes the DNS server. However:

  ubuntu@manual:~$ ping google.com
  ping: unknown host google.com

  If restart the interfacE:

  ubuntu@manual:~$ sudo ifdown ens3 && sudo ifup ens3
  ifdown: interface ens3 not configured
  Internet Systems Consortium DHCP Client 4.3.3
  Copyright 2004-2015 Internet Systems Consortium.
  All rights reserved.
  For info, please visit https://www.isc.org/software/dhcp/

  Listening on LPF/ens3/52:54:00:ea:57:31
  Sending on   LPF/ens3/52:54:00:ea:57:31
  Sending on   Socket/fallback
  DHCPDISCOVER on ens3 to 255.255.255.255 port 67 interval 3 (xid=0x14eb0354)
  DHCPDISCOVER on ens3 to 255.255.255.255 port 67 interval 4 (xid=0x14eb0354)
  DHCPREQUEST of 192.168.122.195 on ens3 to 255.255.255.255 port 67 
(xid=0x5403eb14)
  DHCPOFFER of 192.168.122.195 from 192.168.122.2
  DHCPACK of 192.168.122.195 from 192.168.122.2
  

[Touch-packages] [Bug 1722564] Re: apport question will not accept multi-character responses

[Launchpad Bug Tracker]

** Branch linked: lp:~ubuntu-core-dev/ubuntu/bionic/apport/ubuntu

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

Title:
  apport question will not accept multi-character responses

Status in Apport:
  Confirmed
Status in apport package in Ubuntu:
  In Progress
Status in apport source package in Xenial:
  New
Status in apport source package in Artful:
  In Progress

Bug description:
  the newly added cloud-init apport support shows a list of cloud
  providers and asks the user to select one.  There are currently 18
  options.  For any option > 10, apport will just take the '1' that is
  typed as the answer.

  It should obviously wait for more than one character or a carriage
  return.

  
  *** Please select the cloud vendor or environment in which this instance is 
running

  
  Choices:
1: Amazon - Ec2
2: AliYun
3: AltCloud
4: Azure
5: Bigstep
6: CloudSigma
7: CloudStack
8: DigitalOcean
9: GCE - Google Compute Engine
10: MAAS
11: NoCloud
12: OpenNebula
13: OpenStack
14: OVF
15: Scaleway
16: SmartOS
17: VMware
18: Other
C: Cancel
  Please choose (1/2/3/4/5/6/7/8/9/10/11/12/13/14/15/16/17/18/C): 1

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: apport 2.20.7-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  Date: Tue Oct 10 15:21:48 2017
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1730647] Re: on s390x one should alway be able to manipulate z devices

[Dimitri John Ledkov]

Bionic image build is at
https://launchpad.net/~cloudware/+livefs/ubuntu/bionic/cpc/+build/114329

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

Title:
  on s390x one should alway be able to manipulate z devices

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-meta source package in Xenial:
  Fix Committed
Status in ubuntu-meta source package in Zesty:
  Fix Committed
Status in ubuntu-meta source package in Artful:
  Fix Committed
Status in ubuntu-meta source package in Bionic:
  Fix Released

Bug description:
  [Impact]

   * Currently s390-tools is not installed as part of the server seed,
  which leads to inconsistencies between manually installed systems with
  d-i and systems originating from cloud images - containers, cloud
  images, maas. d-i installs s390-tools, whilst the rest do not.
  However, s390-tools ship tooling to inspect, list, operate on z
  specific devices and should always be available across all of ubuntu,
  including containers, maas, etc. Hence seeding it to server seed.

  [Test Case]

   * s390x containers have s390-tools package installed
   * s390x cloud images have s390-tools package installed
   * s390x maas images have s390-tools package installed

  [Regression Potential]

   * This is calling ubuntu-meta update script only
   * The only other changes are those that have been introduced in other srus.
   * s390-tools is in main

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

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

Re: [Touch-packages] [Bug 1720126] Re: [ip link] Message truncated error for large number of passthrough VFs

[Nish Aravamudan]

I'm guessing this might be a quirk of the armhf runners:

test_tree_garbage (__main__.ChrootRunner)
copied source tree contains only expected files ... : Operation not permitted
cp: cannot create special file ‘/tmp/tmp36ee0r77/chroot//dev/null’:
Operation not permitted
cp: cannot create special file ‘/tmp/tmplo89rot6/chroot//dev/null’:
Operation not permitted
cp: cannot create special file ‘/tmp/tmpsd8_r783/chroot//dev/null’:
Operation not permitted
ERROR
test_tree_norestrictions_nobuild_fail_on_exit (__main__.ChrootRunner)
source tree, no build, no restrictions, test fails with non-zero ... ERROR
test_tree_norestrictions_nobuild_fail_on_stderr (__main__.ChrootRunner)
source tree, no build, no restrictions, test fails with stderr ... ERROR
test_tree_norestrictions_nobuild_fail_on_stderr_and_exit (__main__.ChrootRunner)
source tree, no build, no restrictions, test fails with stderr+exit ... ERROR

I'll see if it might need some restrictions (or if the runner env
changed)?

-Nish

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

Title:
  [ip link] Message truncated error for large number of passthrough VFs

Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Trusty:
  Fix Committed
Status in iproute2 source package in Xenial:
  Fix Released
Status in iproute2 source package in Zesty:
  Fix Released
Status in iproute2 package in CentOS:
  In Progress

Bug description:
  [Impact]

  When querying a Physical Function netdev with a large amount of VF's
  (more than 30), the resulting return message can overflow the 16K
  netlink message buffer.

  This can be fixed by enabling message peeking on the socket and
  resizing the buffer on receive, or by simply enlarging the receive
  buffer.

  Since there's an upper limit to the number of VF's per PF, it's
  relatively sane to just enlarge the receive buffer. Please see the
  attached patch.

  [Test Case]

  # Set up 60 VF's on an SR-IOV device
  ip link show > /dev/null

  Observe the following:
  Message truncated
  Message truncated
  Message truncated

  [Regression Potential]

  1) Applications relying on the broken behaviour will need to be updated, but 
it would be a really dubious use case.
  2) Increasing the rx buffer size increases the memory footprint (but 
realistically, this is tiny).
  3) Extra processing time is now needed to parse the larger buffer, in the 
case that a call to "ip link" is on the critical time path of an application, 
(called multiple times in a tight loop, for example), it would affect load.

  [Other Info]

  Observed on Ubuntu kernel 4.4.0-93-generic on both 14.04 and 16.04

  
=
  Ubuntu16 system

  stack@cluster04:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial

  stack@cluster04:~$ uname -r
  4.4.0-93-generic

  stack@cluster04:~$ apt-cache policy iproute2
  iproute2:
    Installed: 4.3.0-1ubuntu3.16.04.1
  Version table:
  *** 4.3.0-1ubuntu3.16.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  
=

  Ubuntu14 system:
  root@boomslang:~# lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 14.04.3 LTS
  Release:  14.04
  Codename: trusty

  root@boomslang:~# uname -r
  4.4.0-96-generic

  root@boomslang:~# apt-cache policy iproute2
  iproute2:
    Installed: 3.12.0-2ubuntu1
    Version table:
   *** 3.12.0-2ubuntu1 0
  500 http://za.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages

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

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

[Touch-packages] [Bug 1696415] Re: NetworkManager does not update IPv4 address lifetime even though DHCP lease was successfully renewed

[Ray Link]

Upstream GNOME bug fixed.  I've applied the fix to Xenial's NM and
tested.  SRU incoming.

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

Title:
  NetworkManager does not update IPv4 address lifetime even though DHCP
  lease was successfully renewed

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I've found an issue on some of our Xenial office machines, causing
  NetworkManager to drop its IP address lease in some cases when it
  shouldn't. I'm not sure if the actual bug is in NetworkManager or
  perhaps dbus or dhclient, but I'll do my best to help to figure out
  where it is.

  What appears to happen:
  * NetworkManager is informed of a new IPv4 lease.
  * During the lease, dhclient keeps it fresh by renewing it using DHCPREQUESTs 
regularly.
  * In spite of this, NetworkManager drops the IP address from the interface 
when the last reported lease time expires.

  This happens on various machines, once every few days. We are using a
  failover DHCP configuration using two machines (192.168.0.3 'bonaire'
  and 192.168.0.4 'curacao').



  The machine where I've done the debugging is called 'pampus'
  (192.168.0.166). As you can see in the logs, at 01:21:06
  NetworkManager reports a new lease with lease time 7200.

  jun 07 01:21:06 pampus dhclient[1532]: DHCPREQUEST of 192.168.0.166 on eth0 
to 192.168.0.4 port 67 (xid=0x3295b440)
  jun 07 01:21:06 pampus dhclient[1532]: DHCPACK of 192.168.0.166 from 
192.168.0.4
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
address 192.168.0.166
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   plen 
24 (255.255.255.0)
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
gateway 192.168.0.5
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
server identifier 192.168.0.4
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
lease time 7200
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
nameserver '192.168.0.3'
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
nameserver '192.168.0.4'
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
domain name 'office.screenpointmed.com'
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9531] dhcp4 
(eth0): state changed bound -> bound

  After this, dhclient is supposed to keep the lease fresh, which it
  does. E.g. at 03:13:19 you can see a DHCPREQUEST and DHCPACK; I've
  seen this DHCPACK in a tcpdump and it contains a new lease time of
  7200 seconds.

  jun 07 03:13:19 pampus dhclient[1532]: DHCPREQUEST of 192.168.0.166 on eth0 
to 192.168.0.4 port 67 (xid=0x3295b440)
  jun 07 03:13:19 pampus dhclient[1532]: DHCPACK of 192.168.0.166 from 
192.168.0.4
  jun 07 03:13:19 pampus dhclient[1532]: bound to 192.168.0.166 -- renewal in 
2708 seconds.

  However, at 03:21:07 (exactly 2 hours and 1 second after the last
  lease reported by NetworkManager) Avahi and NTP report that the IP
  address is gone:

  jun 07 03:21:07 pampus avahi-daemon[1167]: Withdrawing address record for 
192.168.0.166 on eth0.
  jun 07 03:21:07 pampus avahi-daemon[1167]: Leaving mDNS multicast group on 
interface eth0.IPv4 with address 192.168.0.166.
  jun 07 03:21:07 pampus avahi-daemon[1167]: Interface eth0.IPv4 no longer 
relevant for mDNS.
  jun 07 03:21:08 pampus ntpd[18832]: Deleting interface #3 eth0, 
192.168.0.166#123, interface stats: received=2512, sent=2549, dropped=0, 
active_time=111819 secs

  So I suspect NetworkManager dropped the IP address from the interface,
  because it wasn't informed by dhclient that the lease was renewed. The
  logs don't explicitly say this, so I may have to turn on more verbose
  debugging logs in NetworkManager or dhclient to verify this.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.6-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Wed Jun  7 14:48:59 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-11-04 (214 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  IpRoute:
   default via 192.168.0.5 dev eth0  proto static  metric 100 
   192.168.0.0/24 dev eth0  proto kernel  scope link  src 192.168.0.166 
   192.168.0.0/24 dev eth0  proto kernel  scope link  src 192.168.0.166  metric 
100
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
  

[Touch-packages] [Bug 1720126] Re: [ip link] Message truncated error for large number of passthrough VFs

[Łukasz Zemczak]

The trusty upload seems to have an armhf autopkgtest regression - looks
really strange and I see it failed once already. I think it might be
good to run the autopkgtest suite with no triggers to see if it's an
unrelated regression or not. Could anyone take a look at that?

http://autopkgtest.ubuntu.com/packages/a/autopkgtest/trusty/armhf

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

Title:
  [ip link] Message truncated error for large number of passthrough VFs

Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Trusty:
  Fix Committed
Status in iproute2 source package in Xenial:
  Fix Released
Status in iproute2 source package in Zesty:
  Fix Released
Status in iproute2 package in CentOS:
  In Progress

Bug description:
  [Impact]

  When querying a Physical Function netdev with a large amount of VF's
  (more than 30), the resulting return message can overflow the 16K
  netlink message buffer.

  This can be fixed by enabling message peeking on the socket and
  resizing the buffer on receive, or by simply enlarging the receive
  buffer.

  Since there's an upper limit to the number of VF's per PF, it's
  relatively sane to just enlarge the receive buffer. Please see the
  attached patch.

  [Test Case]

  # Set up 60 VF's on an SR-IOV device
  ip link show > /dev/null

  Observe the following:
  Message truncated
  Message truncated
  Message truncated

  [Regression Potential]

  1) Applications relying on the broken behaviour will need to be updated, but 
it would be a really dubious use case.
  2) Increasing the rx buffer size increases the memory footprint (but 
realistically, this is tiny).
  3) Extra processing time is now needed to parse the larger buffer, in the 
case that a call to "ip link" is on the critical time path of an application, 
(called multiple times in a tight loop, for example), it would affect load.

  [Other Info]

  Observed on Ubuntu kernel 4.4.0-93-generic on both 14.04 and 16.04

  
=
  Ubuntu16 system

  stack@cluster04:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial

  stack@cluster04:~$ uname -r
  4.4.0-93-generic

  stack@cluster04:~$ apt-cache policy iproute2
  iproute2:
    Installed: 4.3.0-1ubuntu3.16.04.1
  Version table:
  *** 4.3.0-1ubuntu3.16.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  
=

  Ubuntu14 system:
  root@boomslang:~# lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 14.04.3 LTS
  Release:  14.04
  Codename: trusty

  root@boomslang:~# uname -r
  4.4.0-96-generic

  root@boomslang:~# apt-cache policy iproute2
  iproute2:
    Installed: 3.12.0-2ubuntu1
    Version table:
   *** 3.12.0-2ubuntu1 0
  500 http://za.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages

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

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

[Touch-packages] [Bug 1731036] [NEW] package libglib2.0-0 2.52.0-1 failed to install/upgrade: intentando sobreescribir el compartido `/usr/share/doc/libglib2.0-0/NEWS.gz', que es distinto de otras ins

[Miqueas Josue Martinez Marcano]

Public bug reported:

the specified package is not updated and says that it looks like it is
broken

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: libglib2.0-0 2.52.0-1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
Date: Wed Nov  8 15:53:23 2017
ErrorMessage: intentando sobreescribir el compartido 
`/usr/share/doc/libglib2.0-0/NEWS.gz', que es distinto de otras instancias del 
paquetes libglib2.0-0:amd64
InstallationDate: Installed on 2017-11-08 (0 days ago)
InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1)
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5
SourcePackage: glib2.0
Title: package libglib2.0-0 2.52.0-1 failed to install/upgrade: intentando 
sobreescribir el compartido `/usr/share/doc/libglib2.0-0/NEWS.gz', que es 
distinto de otras instancias del paquetes libglib2.0-0:amd64
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: glib2.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package artful

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

Title:
  package libglib2.0-0 2.52.0-1 failed to install/upgrade: intentando
  sobreescribir el compartido `/usr/share/doc/libglib2.0-0/NEWS.gz', que
  es distinto de otras instancias del paquetes libglib2.0-0:amd64

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  the specified package is not updated and says that it looks like it is
  broken

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libglib2.0-0 2.52.0-1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  Date: Wed Nov  8 15:53:23 2017
  ErrorMessage: intentando sobreescribir el compartido 
`/usr/share/doc/libglib2.0-0/NEWS.gz', que es distinto de otras instancias del 
paquetes libglib2.0-0:amd64
  InstallationDate: Installed on 2017-11-08 (0 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5
  SourcePackage: glib2.0
  Title: package libglib2.0-0 2.52.0-1 failed to install/upgrade: intentando 
sobreescribir el compartido `/usr/share/doc/libglib2.0-0/NEWS.gz', que es 
distinto de otras instancias del paquetes libglib2.0-0:amd64
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1731031] Re: Kernel Oops with 17.10

[Henning Meyer]

xorg was auto selected when I used apport and said "freeze"

** Package changed: xorg (Ubuntu) => linux (Ubuntu)

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

Title:
  Kernel Oops with 17.10

Status in linux package in Ubuntu:
  New

Bug description:
  have captured dmesg just before oops

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Wed Nov  8 20:41:14 2017
  DistUpgraded: 2017-11-07 01:49:14,657 DEBUG icon theme changed, re-reading
  DistroCodename: artful
  DistroVariant: kubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.10.0-38-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.13.0-16-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a2e] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Apple Inc. Haswell-ULT Integrated Graphics Controller 
[106b:011a]
  LightdmGreeterLogOld: ** (lightdm-gtk-greeter:1762): WARNING **: Failed to 
load user image: Failed to open file '/home/hmeyer/.face': No such file or 
directory
  MachineType: Apple Inc. MacBookPro11,1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=fbc61d79-8b51-4801-8e2b-175ff6daa14f ro quiet splash apparmor=0 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to artful on 2017-11-07 (1 days ago)
  dmi.bios.date: 02/22/2016
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP111.88Z.0138.B17.1602221718
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-189A3D4F975D5FFC
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-189A3D4F975D5FFC
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP111.88Z.0138.B17.1602221718:bd02/22/2016:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC:
  dmi.product.family: Mac
  dmi.product.name: MacBookPro11,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Wed Nov  8 20:39:06 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2
  xserver.video_driver: modeset

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

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

[Touch-packages] [Bug 1731031] [NEW] Kernel Oops with 17.10

[Henning Meyer]

Public bug reported:

have captured dmesg just before oops

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: KDE
Date: Wed Nov  8 20:41:14 2017
DistUpgraded: 2017-11-07 01:49:14,657 DEBUG icon theme changed, re-reading
DistroCodename: artful
DistroVariant: kubuntu
DkmsStatus:
 bcmwl, 6.30.223.271+bdcom, 4.10.0-38-generic, x86_64: installed
 bcmwl, 6.30.223.271+bdcom, 4.13.0-16-generic, x86_64: installed
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a2e] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Apple Inc. Haswell-ULT Integrated Graphics Controller [106b:011a]
LightdmGreeterLogOld: ** (lightdm-gtk-greeter:1762): WARNING **: Failed to load 
user image: Failed to open file '/home/hmeyer/.face': No such file or directory
MachineType: Apple Inc. MacBookPro11,1
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=fbc61d79-8b51-4801-8e2b-175ff6daa14f ro quiet splash apparmor=0 
vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to artful on 2017-11-07 (1 days ago)
dmi.bios.date: 02/22/2016
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP111.88Z.0138.B17.1602221718
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-189A3D4F975D5FFC
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro11,1
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-189A3D4F975D5FFC
dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP111.88Z.0138.B17.1602221718:bd02/22/2016:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC:
dmi.product.family: Mac
dmi.product.name: MacBookPro11,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Wed Nov  8 20:39:06 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.5-0ubuntu2
xserver.video_driver: modeset

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


** Tags: amd64 apport-bug artful fonts kubuntu

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

Title:
  Kernel Oops with 17.10

Status in linux package in Ubuntu:
  New

Bug description:
  have captured dmesg just before oops

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Wed Nov  8 20:41:14 2017
  DistUpgraded: 2017-11-07 01:49:14,657 DEBUG icon theme changed, re-reading
  DistroCodename: artful
  DistroVariant: kubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.10.0-38-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.13.0-16-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a2e] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Apple Inc. Haswell-ULT Integrated Graphics Controller 
[106b:011a]
  LightdmGreeterLogOld: ** (lightdm-gtk-greeter:1762): WARNING **: Failed to 
load user image: Failed to open file '/home/hmeyer/.face': No such file or 
directory
  MachineType: Apple Inc. MacBookPro11,1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=fbc61d79-8b51-4801-8e2b-175ff6daa14f ro quiet splash apparmor=0 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to artful on 2017-11-07 (1 days ago)
  dmi.bios.date: 02/22/2016
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP111.88Z.0138.B17.1602221718
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-189A3D4F975D5FFC
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-189A3D4F975D5FFC
  dmi.modalias: 

[Touch-packages] [Bug 1712921] Re: enabling networkd appears to eat up entropy

[Mathieu Trudel-Lapierre]

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

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

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

** Also affects: openssh (Ubuntu Bionic)
   Importance: Critical
 Assignee: Dimitri John Ledkov (xnox)
   Status: Fix Released

** Also affects: systemd (Ubuntu Bionic)
   Importance: Critical
 Assignee: Dimitri John Ledkov (xnox)
   Status: Triaged

** Also affects: nplan (Ubuntu Bionic)
   Importance: Critical
 Assignee: Mathieu Trudel-Lapierre (cyphermox)
   Status: In Progress

** Also affects: openssh (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** Also affects: systemd (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** Also affects: nplan (Ubuntu Zesty)
   Importance: Undecided
   Status: New

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

Title:
  enabling networkd appears to eat up entropy

Status in nplan package in Ubuntu:
  In Progress
Status in openssh package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Triaged
Status in nplan source package in Xenial:
  New
Status in openssh source package in Xenial:
  New
Status in systemd source package in Xenial:
  New
Status in nplan source package in Zesty:
  New
Status in openssh source package in Zesty:
  New
Status in systemd source package in Zesty:
  New
Status in nplan source package in Artful:
  In Progress
Status in openssh source package in Artful:
  Fix Released
Status in systemd source package in Artful:
  Triaged
Status in nplan source package in Bionic:
  In Progress
Status in openssh source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Triaged

Bug description:
  enabling networkd appears to eat up entropy

  as seen in openssh autopkgtest failing, when networkd is enabled by
  default.

  See http://autopkgtest.ubuntu.com/packages/openssh/artful/amd64 with
  triggers systemd/234-2ubuntu9

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

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

[Touch-packages] [Bug 1720890] Re: vulkan-smoketest segfaults steam vulkan games segfault

[Lawrence A Fossi]

Awesome Thank you. I'll revert from Oibaf's ppa later today looking
forward to checking them out

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

Title:
  vulkan-smoketest segfaults steam vulkan games segfault

Status in mesa package in Ubuntu:
  In Progress
Status in mesa source package in Xenial:
  New
Status in mesa source package in Artful:
  New

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  $ apt-cache policy mesa-vulkan-drivers
  mesa-vulkan-drivers:
Installed: 17.2.1-0ubuntu1
Candidate: 17.2.1-0ubuntu1
Version table:
   *** 17.2.1-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu artful/universe amd64 Packages
  100 /var/lib/dpkg/status

  
  Easily reproducible : apt-get install mesa-vulkan-drivers apt-get install 
vulkan-utils

  Open a terminal type vulkan-smoketest instead of a glxgears type window it 
will segfault.
  message from kernel.log:
  Sep 29 16:23:53 Tardis-1 kernel: [17709.532915] vulkan-smoketes[11798]: 
segfault at 0 ip 7fed61a17914 sp 7ffedcb8f850 error 6 in 
libvulkan_radeon.so[7fed619ab000+18b000]
  syslog:
  Sep 28 10:38:13 Tardis-1 kernel: [18292.174313] vulkan-smoketes[13385]: 
segfault at 0 ip 7f62705a7914 sp 7ffd0edc6260 error 6 in 
libvulkan_radeon.so[7f627053b000+18b000]

  What should happen is a glxgears like window will open and render properly 
instead of segfaulting.
  It appears that the culprit is an old or broken libvulkan_radeon.so provided 
by mesa-vulkan-drivers.

  As a test I renamed the old lib and dropped in a newer version from
  oibaf's ppa. smoketest now passes steam's The Talos Princible and Mad
  Max now work properly in Vulkan mode as well instead of segfaulting.

  This issue is also present on Zesty and fixed in both Oibaf's and
  Padoka's ppa's since April back when they were rolling 17.2 mesa.

  I have no idea if libvulkan_intel.so also needs updating no hardware
  to check.

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

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

[Touch-packages] [Bug 1720890] Re: vulkan-smoketest segfaults steam vulkan games segfault

[Timo Aaltonen]

a new version has been uploaded to xenial/artful/bionic, and for X/A you
can find it also on the updates ppa:

https://launchpad.net/~ubuntu-x-swat/+archive/ubuntu/updates

(artful still building ATM)

** Changed in: mesa (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  vulkan-smoketest segfaults steam vulkan games segfault

Status in mesa package in Ubuntu:
  In Progress
Status in mesa source package in Xenial:
  New
Status in mesa source package in Artful:
  New

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  $ apt-cache policy mesa-vulkan-drivers
  mesa-vulkan-drivers:
Installed: 17.2.1-0ubuntu1
Candidate: 17.2.1-0ubuntu1
Version table:
   *** 17.2.1-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu artful/universe amd64 Packages
  100 /var/lib/dpkg/status

  
  Easily reproducible : apt-get install mesa-vulkan-drivers apt-get install 
vulkan-utils

  Open a terminal type vulkan-smoketest instead of a glxgears type window it 
will segfault.
  message from kernel.log:
  Sep 29 16:23:53 Tardis-1 kernel: [17709.532915] vulkan-smoketes[11798]: 
segfault at 0 ip 7fed61a17914 sp 7ffedcb8f850 error 6 in 
libvulkan_radeon.so[7fed619ab000+18b000]
  syslog:
  Sep 28 10:38:13 Tardis-1 kernel: [18292.174313] vulkan-smoketes[13385]: 
segfault at 0 ip 7f62705a7914 sp 7ffd0edc6260 error 6 in 
libvulkan_radeon.so[7f627053b000+18b000]

  What should happen is a glxgears like window will open and render properly 
instead of segfaulting.
  It appears that the culprit is an old or broken libvulkan_radeon.so provided 
by mesa-vulkan-drivers.

  As a test I renamed the old lib and dropped in a newer version from
  oibaf's ppa. smoketest now passes steam's The Talos Princible and Mad
  Max now work properly in Vulkan mode as well instead of segfaulting.

  This issue is also present on Zesty and fixed in both Oibaf's and
  Padoka's ppa's since April back when they were rolling 17.2 mesa.

  I have no idea if libvulkan_intel.so also needs updating no hardware
  to check.

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

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

[Touch-packages] [Bug 1717471] Re: networkd does not accept / set advertised mtu

[Mathieu Trudel-Lapierre]

Verification-done for zesty with nplan 0.29~17.04.1:

I verified that the generated networkd config in the .network file
contains "UseMTP=true" in the [DHCP] section; and the container gets the
right MTU from the DHCP server.

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

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

Title:
  networkd does not accept / set advertised mtu

Status in nplan package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in nplan source package in Xenial:
  Fix Committed
Status in systemd source package in Xenial:
  New
Status in nplan source package in Zesty:
  Fix Committed

Bug description:
  [Impact]
  Hosts may require a specific MTU to be set as passed by DHCP options. We 
should honor these settings to ensure proper communication of the host with the 
rest of the network.

  [Test case]
  1) Run netplan on a system that should receive MTU settings from DHCP.
  2) Validate that the MTU configuration provided by DHCP is applied to the 
right interface.

  [Regression Potential]
  If DHCP settings specify an invalid MTU setting which is currently being 
ignored and letting the systems communicate correctly with the network, then 
these systems would regress.

  ---

   Right, so as far as I can tell the neutron-api on lcy01 is
  configured to advertise an instance interface MTU of 1400, though
  that's lower than it has to be, and the new DHCP setup with networkd
  just doesn't respect that DHCP option.

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

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

[Touch-packages] [Bug 1730993] Re: Bluetooth stops working shortly after connecting to WiFi

[John W. Galvin]

** Summary changed:

- Bluetooth stops shortly working after connecting to WiFI
+ Bluetooth stops working shortly after connecting to WiFi

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

Title:
  Bluetooth stops working shortly after connecting to WiFi

Status in network-manager package in Ubuntu:
  New

Bug description:
  On a Lenovo T570 laptop with an Intel Dual Band Wireless-AC 8265, Wi-
  Fi, 2x2 802.11ac + BT4.2 chipset and a fresh install of Ubuntu 17.10,
  when using WiFi, bluetooth will stop working within a minute or two of
  connecting to WiFI.  Specifically a bluetooth mouse (Logitech
  MXAnywhere2) will stop working under these circumstances and will not
  work again until the laptop is restarted.  This does not happen when
  WiFi is not in use (no network or wired network).  This did not happen
  at all in Ubuntu 17.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.4-1ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  8 10:16:05 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-11-06 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  IpRoute:
   default via 192.168.18.1 dev enp0s31f6 proto static metric 100 
   169.254.0.0/16 dev enp0s31f6 scope link metric 1000 
   172.16.208.0/24 dev vmnet1 proto kernel scope link src 172.16.208.1 
   192.168.18.0/24 dev enp0s31f6 proto kernel scope link src 192.168.18.39 
metric 100 
   192.168.85.0/24 dev vmnet8 proto kernel scope link src 192.168.85.1
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1729910] Re: lp ignores ~/.cups/lpoptions in 17.10

[Eric Desrochers]

Sponsored for Artful.

* Manual run of autopkgtest has been successful :
--
adt-run [09:26:47]:  summary
cups-core-drivers PASS
cups PASS

- Eric

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

Title:
  lp ignores ~/.cups/lpoptions in 17.10

Status in cups package in Ubuntu:
  Fix Released
Status in cups source package in Artful:
  In Progress

Bug description:
  [Impact]

   * During some refactoring done to cupsGetNamedDest function used in
  many different parts of the code a regression has been introduced
  causing the per-user default printer setting (in ~/.cups/lpoptions) to
  be ignored.

  This bug has been introduced in Artful due to the refactoring. Earlier
  releases are fine, similarly this bug is fixed upstream for Bionic.

  [Test Case]

   1. Make sure at least 2 printers are set up in cups.
   2. Set one of them as global default.
   3. Create a user default setting (~/.cups/lpoptions) with the other printer 
set as default:
  Default other_printer
   4. Run lpstat -d.

  Expected result:
  User default printer is displayed.

  Actual result:
  Global default printer is displayed.

  [Regression Potential]

   * The regression potential is minial, as this is a very simple bugfix and is 
already included in the latest (2.2.5+) releases of cups (including Bionic).
   * The only setups affected may be those depending (possibly unintentionally) 
on the incorrect behavior. Their users may observe default printer change.

  [Other Info]

   * Original bug description

  LP ignores the settings defined in ~/cups/lpoptions in artful

  Steps to reproduce:

  1) Define a default print in lpoptions that differs from one in 
/etc/cups/printers.conf
  2) Execute lpstat -d
  3) Above will output default defined in prints.conf instead of 
~/cups/lpoptions

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

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

[Touch-packages] [Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

[Robie Basak]

Hello Andres, or anyone else affected,

Accepted resolvconf into trusty-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/resolvconf/1.69ubuntu1.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-trusty to verification-done-trusty. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-trusty. In either case, details of your
testing will help us make a better decision.

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

** Changed in: resolvconf (Ubuntu Trusty)
   Status: In Progress => Fix Committed

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

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

Title:
  [2.3] resolv.conf is not set (during commissioning or testing)

Status in MAAS:
  Fix Released
Status in resolvconf package in Ubuntu:
  Won't Fix
Status in resolvconf source package in Trusty:
  Fix Committed
Status in resolvconf source package in Xenial:
  Fix Released

Bug description:
  === Begin SRU Template ===
  [Impact]
  Without this fix applied, dns settings provided to the dhcp response
  in the initramfs are not reflected in the "real root".

  Thus dns resolution does not work. Of most interest was the MAAS use
  case of the 'root=http://<>/squashfs' use case.

  MAAS 2.3 uses this for the installation environment and also the rescue
  environment.  In most cases the 14.04 specific fix will only apply
  to installation as 16.04 is most likely to be used in rescue mode.

  [Test Case]
  There are two tests for this.

  a.) local/non-MAAS test
  Download the test case attached.
  Run it and follow the instructions.
  Login to the guest (ubuntu:password), and inspect /etc/resolv.conf
  without the fix there would be no data in /etc/resolv.conf.  With the
  fix you should see 'nameserver 10.0.2.2' and 'search mydomain.com bar.com'

  b.) MAAS test.
  For the full maas test, you need to build a image stream for maas
  with the fix included in the squashfs image and then import that
  stream to maas and use the rescue environment and verify dns.
  This process is beyond the scope of the SRU template, but is
  described partially in
    
http://bazaar.launchpad.net/~maas-images-maintainers/maas-images/maas-ephemerals/view/head:/README

  [Regression Potential]
  Regression potential should be very low.  There are gates in the code
  to make sure that this code is inactive other than when it is explicitly
  enabled.

  net-interface-handler will exit without doing anything unless:
  a.) there exist files /run/net-$INTERFACE.conf or /run/net6-$INTERFACE.conf
  and these files have non-empty values for a variable mentioned above.
  (These files are written by the initramfs code when 'ip=' is seen).

  b.) this is not a container.
trusty uses 'running-in-container' to determine this.
xenial uses 'systemd-detect-virt'

  c.) there is no OPENISCSI_MARKER file (/run/initramfs/open-iscsi.interface)
  if open-iscsi has written this file due to open-iscsi root, then it
  will handle this functionality. resolvconf will get out of the way.

  d.) /proc/cmdline contains cloud-config-url=* or 'rc-initrd-dns'
  This lowers the scope of changes in runtime to cases with where either the
  new flag is seen or cloud-config-url is passed. The MAAS use case will
  contain this flag.

  [Other Info]

  === End SRU Template ===

  Using MAAS 2.3, during commissioning (and likely in the rest of the
  ephemeral environment) we have noticed that resolv.conf is not set
  with the DNS server.

  That said, during the commissioning process, MAAS does not send any
  metadata to cloud-init to configure the network, rather, we expect the
  image to boot from the network via DHCP. So, cloud-init writes:

  ubuntu@manual:~$ cat /etc/network/interfaces.d/50-cloud-init.cfg
  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  auto lo
  iface lo inet loopback

  # control-manual ens3
  iface ens3 inet dhcp
  broadcast 192.168.122.255
  dns-nameservers 192.168.122.2
  gateway 

[Touch-packages] [Bug 1720890] Re: vulkan-smoketest segfaults steam vulkan games segfault

[Lawrence A Fossi]

Thanks for the update. I'm glad to see I wasn't imagining things or a 
user/hardware issue on my end.
When Ubuntu updated the mesa packages to 17.2.2 I made sure apport had the 
extra packages installed it needed. I also manually installed the 4 vulkan 
ddbug packages before running the vulkan-smoketest. Apport kicked in and 
auto-reported it. Hopefully that generated report helped since it does a far 
better job that my first attempt.

After I rebuilt the Ubuntu vulkan-utils package and used quilt to
restore the amd mesa source but was unable to rebuilt mesa for the mesa
vulkan drivers so was unable to test them. I had observed what the patch
was doing and came to the decision that radv was being disabled by
design. Thats why I didn't report upstream I didn't want to waste dev
time for what appeared to be a packaging choice. My apologies for that.

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

Title:
  vulkan-smoketest segfaults steam vulkan games segfault

Status in mesa package in Ubuntu:
  Triaged
Status in mesa source package in Xenial:
  New
Status in mesa source package in Artful:
  New

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  $ apt-cache policy mesa-vulkan-drivers
  mesa-vulkan-drivers:
Installed: 17.2.1-0ubuntu1
Candidate: 17.2.1-0ubuntu1
Version table:
   *** 17.2.1-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu artful/universe amd64 Packages
  100 /var/lib/dpkg/status

  
  Easily reproducible : apt-get install mesa-vulkan-drivers apt-get install 
vulkan-utils

  Open a terminal type vulkan-smoketest instead of a glxgears type window it 
will segfault.
  message from kernel.log:
  Sep 29 16:23:53 Tardis-1 kernel: [17709.532915] vulkan-smoketes[11798]: 
segfault at 0 ip 7fed61a17914 sp 7ffedcb8f850 error 6 in 
libvulkan_radeon.so[7fed619ab000+18b000]
  syslog:
  Sep 28 10:38:13 Tardis-1 kernel: [18292.174313] vulkan-smoketes[13385]: 
segfault at 0 ip 7f62705a7914 sp 7ffd0edc6260 error 6 in 
libvulkan_radeon.so[7f627053b000+18b000]

  What should happen is a glxgears like window will open and render properly 
instead of segfaulting.
  It appears that the culprit is an old or broken libvulkan_radeon.so provided 
by mesa-vulkan-drivers.

  As a test I renamed the old lib and dropped in a newer version from
  oibaf's ppa. smoketest now passes steam's The Talos Princible and Mad
  Max now work properly in Vulkan mode as well instead of segfaulting.

  This issue is also present on Zesty and fixed in both Oibaf's and
  Padoka's ppa's since April back when they were rolling 17.2 mesa.

  I have no idea if libvulkan_intel.so also needs updating no hardware
  to check.

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

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

[Touch-packages] [Bug 1731008] [NEW] Multi-monitor display arrangement doesn't work in Ubuntu 17.10

[John W. Galvin]

Public bug reported:

When using a fresh install of Ubuntu 17.10 desktop on a Lenovo T570
laptop in a Lenovo ThinkPad Ultra Dock (40A20090XX), with the buitin
monitor off (laptop closed) and 3 external 1920 x 1080 monitors (1 x
Acer V246HL VGA, 2 x Dell P2417H DisplayPort) display arrangement in
Settings | Devices | Displays does not work.  The Dell monitors show up
as 4 and 3, the Acer as 2.  1, the builtin monitor, is not displayed in
the arrangement area.  The monitor icons show up, left to right, in the
order 4, 3, 2.  It is almost impossible to change that order.  I have
managed, in 1 out of 20 attempts, to get the display icons into a 4, 2,
3 order, but in no case have I been able to apply any arrangement
changes.  The Apply button is never displayed.  I want to get them into
a 2, 4, 3 order.  This was not an issue in Ubuntu Gnome 17.04, in that
version everything worked fine.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Nov  8 10:51:08 2017
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo HD Graphics 620 [17aa:2247]
InstallationDate: Installed on 2017-11-06 (1 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
MachineType: LENOVO 20H9000NUS
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/02/2017
dmi.bios.vendor: LENOVO
dmi.bios.version: N1VET32W (1.22 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20H9000NUS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN1VET32W(1.22):bd06/02/2017:svnLENOVO:pn20H9000NUS:pvrThinkPadT570:rvnLENOVO:rn20H9000NUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T570
dmi.product.name: 20H9000NUS
dmi.product.version: ThinkPad T570
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug artful ubuntu wayland-session

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

Title:
  Multi-monitor display arrangement doesn't work in Ubuntu 17.10

Status in xorg package in Ubuntu:
  New

Bug description:
  When using a fresh install of Ubuntu 17.10 desktop on a Lenovo T570
  laptop in a Lenovo ThinkPad Ultra Dock (40A20090XX), with the buitin
  monitor off (laptop closed) and 3 external 1920 x 1080 monitors (1 x
  Acer V246HL VGA, 2 x Dell P2417H DisplayPort) display arrangement in
  Settings | Devices | Displays does not work.  The Dell monitors show
  up as 4 and 3, the Acer as 2.  1, the builtin monitor, is not
  displayed in the arrangement area.  The monitor icons show up, left to
  right, in the order 4, 3, 2.  It is almost impossible to change that
  order.  I have managed, in 1 out of 20 attempts, to get the display
  icons into a 4, 2, 3 order, but in no case have I been able to apply
  any arrangement changes.  The Apply button is never displayed.  I want
  to get them into a 2, 4, 3 order.  This was not an issue in Ubuntu
  Gnome 17.04, in that version everything worked fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  8 10:51:08 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 

[Touch-packages] [Bug 1730993] [NEW] Bluetooth stops shortly working after connecting to WiFI

[John W. Galvin]

Public bug reported:

On a Lenovo T570 laptop with an Intel Dual Band Wireless-AC 8265, Wi-Fi,
2x2 802.11ac + BT4.2 chipset and a fresh install of Ubuntu 17.10, when
using WiFi, bluetooth will stop working within a minute or two of
connecting to WiFI.  Specifically a bluetooth mouse (Logitech
MXAnywhere2) will stop working under these circumstances and will not
work again until the laptop is restarted.  This does not happen when
WiFi is not in use (no network or wired network).  This did not happen
at all in Ubuntu 17.04.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: network-manager 1.8.4-1ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Nov  8 10:16:05 2017
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2017-11-06 (1 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
IpRoute:
 default via 192.168.18.1 dev enp0s31f6 proto static metric 100 
 169.254.0.0/16 dev enp0s31f6 scope link metric 1000 
 172.16.208.0/24 dev vmnet1 proto kernel scope link src 172.16.208.1 
 192.168.18.0/24 dev enp0s31f6 proto kernel scope link src 192.168.18.39 metric 
100 
 192.168.85.0/24 dev vmnet8 proto kernel scope link src 192.168.85.1
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled

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


** Tags: amd64 apport-bug artful wayland-session

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

Title:
  Bluetooth stops shortly working after connecting to WiFI

Status in network-manager package in Ubuntu:
  New

Bug description:
  On a Lenovo T570 laptop with an Intel Dual Band Wireless-AC 8265, Wi-
  Fi, 2x2 802.11ac + BT4.2 chipset and a fresh install of Ubuntu 17.10,
  when using WiFi, bluetooth will stop working within a minute or two of
  connecting to WiFI.  Specifically a bluetooth mouse (Logitech
  MXAnywhere2) will stop working under these circumstances and will not
  work again until the laptop is restarted.  This does not happen when
  WiFi is not in use (no network or wired network).  This did not happen
  at all in Ubuntu 17.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.4-1ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  8 10:16:05 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-11-06 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  IpRoute:
   default via 192.168.18.1 dev enp0s31f6 proto static metric 100 
   169.254.0.0/16 dev enp0s31f6 scope link metric 1000 
   172.16.208.0/24 dev vmnet1 proto kernel scope link src 172.16.208.1 
   192.168.18.0/24 dev enp0s31f6 proto kernel scope link src 192.168.18.39 
metric 100 
   192.168.85.0/24 dev vmnet8 proto kernel scope link src 192.168.85.1
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1727401] Re: Corruption on windowed 3D apps running on dGPU (Intel/AMD)

[Bug Watch Updater]

** Changed in: mesa
   Status: Unknown => In Progress

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

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

Title:
  Corruption on windowed 3D apps running on dGPU (Intel/AMD)

Status in Mesa:
  In Progress
Status in mesa package in Ubuntu:
  New
Status in mesa source package in Xenial:
  New
Status in mesa source package in Artful:
  New

Bug description:
  [Impact]

  Corruption is seen on windowed 3D apps running on dGPU

  [Test case]

  Get a certain Intel/AMD hybrid machine, run 'DRI_PRIME=1 glxgears',
  see how the window has corrupted gfx.

  The fix is to patch Intel i965_dri driver.

  [Regression potential]

  There could be a slight loss of performance, but corruption free
  behaviour.

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

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

[Touch-packages] [Bug 1722162] Re: gold: Fix internal error when applying TLSDESC relocations with no TLS segment.

[Timo Aaltonen]

** Description changed:

+ [Impact]
+ 
  llvm-5.0 fails to build on arm64/xenial because of gold/19353.
+ 
+ [Test case]
+ 
+ backport the upstream commit, test llvm-5 build ond arm64
+ 
+ [Regression potential]
+ Unknown

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

Title:
  gold: Fix internal error when applying TLSDESC relocations with no TLS
  segment.

Status in binutils:
  Fix Released
Status in binutils package in Ubuntu:
  Invalid
Status in binutils source package in Xenial:
  New

Bug description:
  [Impact]

  llvm-5.0 fails to build on arm64/xenial because of gold/19353.

  [Test case]

  backport the upstream commit, test llvm-5 build ond arm64

  [Regression potential]
  Unknown

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

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

[Touch-packages] [Bug 1720126] Re: [ip link] Message truncated error for large number of passthrough VFs

[Nish Aravamudan]

If someone is interested in the proper upstream fixes, please file a new
bug and we will need to fix bionic and prepare a distinct SRU for the
existing releases.

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

Title:
  [ip link] Message truncated error for large number of passthrough VFs

Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Trusty:
  Fix Committed
Status in iproute2 source package in Xenial:
  Fix Released
Status in iproute2 source package in Zesty:
  Fix Released
Status in iproute2 package in CentOS:
  In Progress

Bug description:
  [Impact]

  When querying a Physical Function netdev with a large amount of VF's
  (more than 30), the resulting return message can overflow the 16K
  netlink message buffer.

  This can be fixed by enabling message peeking on the socket and
  resizing the buffer on receive, or by simply enlarging the receive
  buffer.

  Since there's an upper limit to the number of VF's per PF, it's
  relatively sane to just enlarge the receive buffer. Please see the
  attached patch.

  [Test Case]

  # Set up 60 VF's on an SR-IOV device
  ip link show > /dev/null

  Observe the following:
  Message truncated
  Message truncated
  Message truncated

  [Regression Potential]

  1) Applications relying on the broken behaviour will need to be updated, but 
it would be a really dubious use case.
  2) Increasing the rx buffer size increases the memory footprint (but 
realistically, this is tiny).
  3) Extra processing time is now needed to parse the larger buffer, in the 
case that a call to "ip link" is on the critical time path of an application, 
(called multiple times in a tight loop, for example), it would affect load.

  [Other Info]

  Observed on Ubuntu kernel 4.4.0-93-generic on both 14.04 and 16.04

  
=
  Ubuntu16 system

  stack@cluster04:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial

  stack@cluster04:~$ uname -r
  4.4.0-93-generic

  stack@cluster04:~$ apt-cache policy iproute2
  iproute2:
    Installed: 4.3.0-1ubuntu3.16.04.1
  Version table:
  *** 4.3.0-1ubuntu3.16.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  
=

  Ubuntu14 system:
  root@boomslang:~# lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 14.04.3 LTS
  Release:  14.04
  Codename: trusty

  root@boomslang:~# uname -r
  4.4.0-96-generic

  root@boomslang:~# apt-cache policy iproute2
  iproute2:
    Installed: 3.12.0-2ubuntu1
    Version table:
   *** 3.12.0-2ubuntu1 0
  500 http://za.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages

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

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

[Touch-packages] [Bug 1727401] Re: Corruption on windowed 3D apps running on dGPU (Intel/AMD)

[Timo Aaltonen]

** Bug watch added: freedesktop.org Bugzilla #101691
   https://bugs.freedesktop.org/show_bug.cgi?id=101691

** Also affects: mesa via
   https://bugs.freedesktop.org/show_bug.cgi?id=101691
   Importance: Unknown
   Status: Unknown

** Changed in: mesa (Ubuntu)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

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

Title:
  Corruption on windowed 3D apps running on dGPU (Intel/AMD)

Status in Mesa:
  Unknown
Status in mesa package in Ubuntu:
  New
Status in mesa source package in Xenial:
  New
Status in mesa source package in Artful:
  New

Bug description:
  [Impact]

  Corruption is seen on windowed 3D apps running on dGPU

  [Test case]

  Get a certain Intel/AMD hybrid machine, run 'DRI_PRIME=1 glxgears',
  see how the window has corrupted gfx.

  The fix is to patch Intel i965_dri driver.

  [Regression potential]

  There could be a slight loss of performance, but corruption free
  behaviour.

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

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

[Touch-packages] [Bug 1730744] Re: sudo is slow (10 seconds) when hostname is not resolvable

[Scott Moser]

Output of recreate script:
$ /tmp/lp-1730744-reproduce-lxc 
=== launch container testme50 ===
Creating testme50
Starting testme50
=== wait for boot ===
.1 degraded 7.00
=== set hostname to bogus value: testme50-foo ===
=== show slow sudo ===
sudo: unable to resolve host bogus-testme50: Connection timed out
real 20.02
user 0.00
sys 0.01
FAIL: 20s
=== delete-testme50 ===

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

Title:
  sudo is slow (10 seconds) when hostname is not resolvable

Status in systemd package in Ubuntu:
  New

Bug description:
  I'm seeing very slow 'sudo' times in a qemu guest when the host uses 
systemd-resolved.
  If I change /etc/resolv.conf on the host to point directly to a dns server 
(8.8.8.8) then the problem goes away.

  
  To recreate, you can download a cloud image and boot it under qemu with a 
command line like:
cloud-localds seed.img user-data meta-data 
qemu-system-x86_64 -enable-kvm \
   -device virtio-net-pci,netdev=net00 \
   -netdev type=user,id=net00 \
   -drive file=root.img,id=disk00,if=none,index=0 \
   -device virtio-blk,drive=disk00,serial=root.img \
   -drive file=seed.img,id=disk01,if=none,index=1 \
   -device virtio-blk,drive=disk01,serial=seed.img \
   -m 768

  Make sure that your hostname does not resolve (change it to 'bogus-host1').
  Log into the guest and then just try sudo, you'll see something like:
  # time sudo ls
  sudo: unable to resolve host rooturl-trusty

  real0m10.029s
  user0m0.006s
  sys 0m0.011s

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

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

[Touch-packages] [Bug 1730744] Re: sudo is slow (10 seconds) when hostname is not resolvable

[Scott Moser]

** Attachment added: "script with full reproduce."
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1730744/+attachment/5005923/+files/lp-1730744-reproduce-lxc

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

Title:
  sudo is slow (10 seconds) when hostname is not resolvable

Status in systemd package in Ubuntu:
  New

Bug description:
  I'm seeing very slow 'sudo' times in a qemu guest when the host uses 
systemd-resolved.
  If I change /etc/resolv.conf on the host to point directly to a dns server 
(8.8.8.8) then the problem goes away.

  
  To recreate, you can download a cloud image and boot it under qemu with a 
command line like:
cloud-localds seed.img user-data meta-data 
qemu-system-x86_64 -enable-kvm \
   -device virtio-net-pci,netdev=net00 \
   -netdev type=user,id=net00 \
   -drive file=root.img,id=disk00,if=none,index=0 \
   -device virtio-blk,drive=disk00,serial=root.img \
   -drive file=seed.img,id=disk01,if=none,index=1 \
   -device virtio-blk,drive=disk01,serial=seed.img \
   -m 768

  Make sure that your hostname does not resolve (change it to 'bogus-host1').
  Log into the guest and then just try sudo, you'll see something like:
  # time sudo ls
  sudo: unable to resolve host rooturl-trusty

  real0m10.029s
  user0m0.006s
  sys 0m0.011s

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

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

[Touch-packages] [Bug 1727390] Re: New bugfix release 17.2.4

[Timo Aaltonen]

** Changed in: mesa (Ubuntu)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

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

Title:
  New bugfix release 17.2.4

Status in mesa package in Ubuntu:
  New
Status in mesa source package in Xenial:
  New
Status in mesa source package in Artful:
  New

Bug description:
  [Impact]

  A new upstream bugfix release is available. Release note diff compared
  to 17.2.2:

  "Mesa 17.2.3 is now available.

  In this release we have:

  The Vulkan drivers ANV and RADV have multiple small fixes.

  The EGL code has improved handling of the new wl_dmabuf codepath.

  SWR no longer crashes when checking environment variables.

  Other gallium drivers have also seen updates - freedreno, nouveau and
  radeonsi. The gallivm module, used by llvmpipe et al. has gained little
  endian PPC64 fixes.

  The VA and VDPAU state-trackers have seems improvements handling
  interlaced videos.

  We're using python3 compatible constructs which gives us SCons 3.0
  support."

  "Mesa 17.2.4 is now available.

  In this release we have:

  In Mesa Core we have included a change to prevent KOTOR from breaking
  when in combination with the ATI fragment shader extension. 
  Additionally, NIR has also received a correction.

  Mesa's state tracker has gotten a patch to avoid leaks in certain
  situations like when resizing a window.

  Intel drivers have received several fixes.  The compiler has gotten a
  couple, while anv also received one.  i965 got a patch to avoid VA-
  API, Beignet and other contexts in the system to break when in
  combination with previous versions of Mesa 17.2.x.

  AMD's compiler has received a couple of fixes while radv has also
  received another couple, including one to avoid a hang due to an
  overflow on huge textures.

  Broadcom's vc4 has corrected a problem when compiling with Android's
  clang.

  clover has also seen fixed a problem compiling after a specific clang
  revision.

  Vulkan's WSI has gotten plugged a memory leak for X11."

  
  [Test case]

  Test typical use cases on the most common hw/driver combinations:
  intel/i965
  nvidia/nouveau
  radeon/radeonsi

  [Regression potential]

  These releases are tested against compliance, bugfix releases in
  particular have minimal risk of regressing anything major at least.

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

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

[Touch-packages] [Bug 1728574] Re: Xwayland fails to initialize on miral-desktop

[Alan Griffiths]

Alternative fix: https://github.com/MirServer/mir/pull/19

** Changed in: mir (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  Xwayland fails to initialize on miral-desktop

Status in Mir:
  Triaged
Status in mir package in Ubuntu:
  In Progress

Bug description:
  $ miral-desktop
  $ WAYLAND_DEBUG=1 miral-xrun xeyes

  This outputs:

  [3478171.835]  -> wl_display@1.get_registry(new id wl_registry@2)
  [3478171.859]  -> wl_disp...@1.sync(new id wl_callback@3)
  [3478171.992] wl_display@1.delete_id(3)
  [3478172.018] wl_registry@2.global(1, "wl_compositor", 3)
  [3478172.032]  -> wl_regis...@2.bind(1, "wl_compositor", 1, new id 
[unknown]@4)
  [3478172.056] wl_registry@2.global(2, "wl_seat", 5)
  [3478172.061] wl_registry@2.global(3, "wl_output", 2)
  [3478172.065]  -> wl_regis...@2.bind(3, "wl_output", 2, new id [unknown]@5)
  [3478172.078] wl_registry@2.global(4, "wl_shell", 1)
  [3478172.083]  -> wl_regis...@2.bind(4, "wl_shell", 1, new id [unknown]@6)
  [3478172.087] wl_registry@2.global(5, "wl_shm", 1)
  [3478172.092]  -> wl_regis...@2.bind(5, "wl_shm", 1, new id [unknown]@7)
  [3478172.098] wl_registry@2.global(6, "wl_drm", 2)
  [3478172.104]  -> wl_regis...@2.bind(6, "wl_drm", 2, new id [unknown]@8)
  [3478172.113] wl_callb...@3.done(0)
  [3478172.119]  -> wl_disp...@1.sync(new id wl_callback@3)
  [3478172.227] wl_display@1.delete_id(3)
  [3478172.248] wl_output@5.geometry(0, 0, 310, 170, 0, "Fake manufacturer", 
"Fake model", 0)
  [3478172.271] wl_out...@5.mode(3, 1600, 900, 59970)
  [3478172.277] wl_output@5.scale(1)
  [3478172.280] wl_out...@5.done()
  [3478172.287] wl_drm@8.device("/dev/dri/card0")
  wayland-egl: could not open /dev/dri/card0 (Permission denied)
  [3478172.300] wl_drm@8.format(875713089)
  [3478172.304] wl_drm@8.format(875713112)
  [3478172.308] wl_drm@8.format(909199186)
  [3478172.312] wl_drm@8.format(961959257)
  [3478172.317] wl_drm@8.format(825316697)
  [3478172.321] wl_drm@8.format(842093913)
  [3478172.325] wl_drm@8.format(909202777)
  [3478172.330] wl_drm@8.format(875713881)
  [3478172.335] wl_drm@8.format(842094158)
  [3478172.339] wl_drm@8.format(909203022)
  [3478172.344] wl_drm@8.format(1448695129)
  [3478172.349] wl_drm@8.capabilities(1)
  [3478172.353] wl_callb...@3.done(0)
  [3478172.359]  -> wl_disp...@1.sync(new id wl_callback@3)
  [3478172.388] wl_display@1.delete_id(3)
  [3478172.399] wl_callb...@3.done(0)
  [3478172.406]  -> wl_disp...@1.sync(new id wl_callback@3)
  [3478172.486] wl_display@1.delete_id(3)
  [3478172.498] wl_callb...@3.done(0)
  [3478172.502]  -> wl_disp...@1.sync(new id wl_callback@3)
  [3478172.532] wl_display@1.delete_id(3)
  [3478172.541] wl_callb...@3.done(0)
  [3478172.560]  -> wl_disp...@1.sync(new id wl_callback@3)
  [3478172.610] wl_display@1.delete_id(3)
  [3478172.623] wl_callb...@3.done(0)

  with a lot of repetition of the last three lines. X11 clients fail to
  connect.

  

  For comparison, the output when connecting to miral-app is:

  [3926349.817]  -> wl_display@1.get_registry(new id wl_registry@2)
  [3926349.862]  -> wl_disp...@1.sync(new id wl_callback@3)
  [3926349.970] wl_display@1.delete_id(3)
  [3926349.994] wl_registry@2.global(1, "wl_compositor", 3)
  [3926350.006]  -> wl_regis...@2.bind(1, "wl_compositor", 1, new id 
[unknown]@4)
  [3926350.025] wl_registry@2.global(2, "wl_seat", 5)
  [3926350.033] wl_registry@2.global(3, "wl_output", 2)
  [3926350.053]  -> wl_regis...@2.bind(3, "wl_output", 2, new id [unknown]@5)
  [3926350.073] wl_registry@2.global(4, "wl_shell", 1)
  [3926350.078]  -> wl_regis...@2.bind(4, "wl_shell", 1, new id [unknown]@6)
  [3926350.083] wl_registry@2.global(5, "wl_shm", 1)
  [3926350.089]  -> wl_regis...@2.bind(5, "wl_shm", 1, new id [unknown]@7)
  [3926350.097] wl_registry@2.global(6, "wl_drm", 2)
  [3926350.101]  -> wl_regis...@2.bind(6, "wl_drm", 2, new id [unknown]@8)
  [3926350.106] wl_callb...@3.done(1)
  [3926350.109]  -> wl_disp...@1.sync(new id wl_callback@3)
  [3926350.184] wl_display@1.delete_id(3)
  [3926350.190] wl_output@5.geometry(0, 0, 338, 198, 0, "Fake manufacturer", 
"Fake model", 0)
  [3926350.201] wl_out...@5.mode(3, 1280, 750, 6)
  [3926350.208] wl_output@5.scale(1)
  [3926350.211] wl_out...@5.done()
  [3926350.219] wl_drm@8.device("/dev/dri/renderD128")
  glamor: EGL version 1.4 (DRI2):
  [3926360.938] wl_drm@8.format(875713089)
  [3926360.952] wl_drm@8.format(875713112)
  [3926360.954] wl_drm@8.format(909199186)
  [3926360.957] wl_drm@8.format(961959257)
  [3926360.959] wl_drm@8.format(825316697)
  [3926360.971] wl_drm@8.format(842093913)
  [3926360.973] wl_drm@8.format(909202777)
  [3926360.975] wl_drm@8.format(875713881)
  [3926360.979] wl_drm@8.format(842094158)
  [3926360.981] wl_drm@8.format(909203022)
  [3926360.983] wl_drm@8.format(1448695129)
  [3926360.985] 

[Touch-packages] [Bug 1730647] Re: on s390x one should alway be able to manipulate z devices

[Dimitri John Ledkov]

Triggered builds of cloud images with proposed enabled:
artful
https://launchpad.net/~cloudware/+livefs/ubuntu/artful/cpc/+build/114279
zesty
https://launchpad.net/~cloudware/+livefs/ubuntu/zesty/cpc/+build/114278
xenial
https://launchpad.net/~cloudware/+livefs/ubuntu/xenial/cpc/+build/114277

In all cases s390-tools is now installed as part of the ubuntu-server
package installation.

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

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

Title:
  on s390x one should alway be able to manipulate z devices

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-meta source package in Xenial:
  Fix Committed
Status in ubuntu-meta source package in Zesty:
  Fix Committed
Status in ubuntu-meta source package in Artful:
  Fix Committed
Status in ubuntu-meta source package in Bionic:
  Fix Released

Bug description:
  [Impact]

   * Currently s390-tools is not installed as part of the server seed,
  which leads to inconsistencies between manually installed systems with
  d-i and systems originating from cloud images - containers, cloud
  images, maas. d-i installs s390-tools, whilst the rest do not.
  However, s390-tools ship tooling to inspect, list, operate on z
  specific devices and should always be available across all of ubuntu,
  including containers, maas, etc. Hence seeding it to server seed.

  [Test Case]

   * s390x containers have s390-tools package installed
   * s390x cloud images have s390-tools package installed
   * s390x maas images have s390-tools package installed

  [Regression Potential]

   * This is calling ubuntu-meta update script only
   * The only other changes are those that have been introduced in other srus.
   * s390-tools is in main

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

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

[Touch-packages] [Bug 1720890] Re: vulkan-smoketest segfaults steam vulkan games segfault

[Timo Aaltonen]

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

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

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

Title:
  vulkan-smoketest segfaults steam vulkan games segfault

Status in mesa package in Ubuntu:
  Triaged
Status in mesa source package in Xenial:
  New
Status in mesa source package in Artful:
  New

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  $ apt-cache policy mesa-vulkan-drivers
  mesa-vulkan-drivers:
Installed: 17.2.1-0ubuntu1
Candidate: 17.2.1-0ubuntu1
Version table:
   *** 17.2.1-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu artful/universe amd64 Packages
  100 /var/lib/dpkg/status

  
  Easily reproducible : apt-get install mesa-vulkan-drivers apt-get install 
vulkan-utils

  Open a terminal type vulkan-smoketest instead of a glxgears type window it 
will segfault.
  message from kernel.log:
  Sep 29 16:23:53 Tardis-1 kernel: [17709.532915] vulkan-smoketes[11798]: 
segfault at 0 ip 7fed61a17914 sp 7ffedcb8f850 error 6 in 
libvulkan_radeon.so[7fed619ab000+18b000]
  syslog:
  Sep 28 10:38:13 Tardis-1 kernel: [18292.174313] vulkan-smoketes[13385]: 
segfault at 0 ip 7f62705a7914 sp 7ffd0edc6260 error 6 in 
libvulkan_radeon.so[7f627053b000+18b000]

  What should happen is a glxgears like window will open and render properly 
instead of segfaulting.
  It appears that the culprit is an old or broken libvulkan_radeon.so provided 
by mesa-vulkan-drivers.

  As a test I renamed the old lib and dropped in a newer version from
  oibaf's ppa. smoketest now passes steam's The Talos Princible and Mad
  Max now work properly in Vulkan mode as well instead of segfaulting.

  This issue is also present on Zesty and fixed in both Oibaf's and
  Padoka's ppa's since April back when they were rolling 17.2 mesa.

  I have no idea if libvulkan_intel.so also needs updating no hardware
  to check.

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

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

[Touch-packages] [Bug 1730908] Re: [ 1549.847151] audit: type=1400 audit(1510129355.497:61): apparmor="DENIED" operation="file_mmap" profile="/usr/bin/evince" name="/usr/lib/x86_64-linux-gnu/libproxy/

[Jamie Strandboge]

G.M. the first denial is because evince doesn't have the necessary rule
for using libproxy (a GNOME 2 technology), but the ntpd denial is
something different. Can you file a separate bug for ntpd?

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

Title:
  [ 1549.847151] audit: type=1400 audit(1510129355.497:61):
  apparmor="DENIED" operation="file_mmap" profile="/usr/bin/evince"
  name="/usr/lib/x86_64-linux-
  gnu/libproxy/0.4.14/modules/network_networkmanager.so" pid=2062
  comm="evince" requested_mask="m" denied_mask="m" fsuid=1000 ouid=0

Status in apparmor package in Ubuntu:
  New

Bug description:
  Since I installed Ubuntu 17.10 I cannot print anymore.

  The only thing I see in the logs are many lines like the following:
  [ 1549.847151] audit: type=1400 audit(1510129355.497:61): apparmor="DENIED" 
operation="file_mmap" profile="/usr/bin/evince" 
name="/usr/lib/x86_64-linux-gnu/libproxy/0.4.14/modules/network_networkmanager.so"
 pid=2062 comm="evince" requested_mask="m" denied_mask="m" fsuid=1000 ouid=0

  I'm not sure it is the cause of my problems, but there is at least a
  problem with apparmor's configuration in Ubuntu 17.10

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

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

[Touch-packages] [Bug 1729910] Re: lp ignores ~/.cups/lpoptions in 17.10

[Eric Desrochers]

Sponsored for Artful.

* Applied cleanly
* Autopkgtest is successfull :
--
adt-run [09:26:47]:  summary
cups-core-driversPASS
cups PASS
--
*...


- Eric

** Tags removed: sts-sponsor-slashd
** Tags added: sts-sponsor-slashd-done

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

Title:
  lp ignores ~/.cups/lpoptions in 17.10

Status in cups package in Ubuntu:
  Fix Released
Status in cups source package in Artful:
  In Progress

Bug description:
  [Impact]

   * During some refactoring done to cupsGetNamedDest function used in
  many different parts of the code a regression has been introduced
  causing the per-user default printer setting (in ~/.cups/lpoptions) to
  be ignored.

  This bug has been introduced in Artful due to the refactoring. Earlier
  releases are fine, similarly this bug is fixed upstream for Bionic.

  [Test Case]

   1. Make sure at least 2 printers are set up in cups.
   2. Set one of them as global default.
   3. Create a user default setting (~/.cups/lpoptions) with the other printer 
set as default:
  Default other_printer
   4. Run lpstat -d.

  Expected result:
  User default printer is displayed.

  Actual result:
  Global default printer is displayed.

  [Regression Potential]

   * The regression potential is minial, as this is a very simple bugfix and is 
already included in the latest (2.2.5+) releases of cups (including Bionic).
   * The only setups affected may be those depending (possibly unintentionally) 
on the incorrect behavior. Their users may observe default printer change.

  [Other Info]

   * Original bug description

  LP ignores the settings defined in ~/cups/lpoptions in artful

  Steps to reproduce:

  1) Define a default print in lpoptions that differs from one in 
/etc/cups/printers.conf
  2) Execute lpstat -d
  3) Above will output default defined in prints.conf instead of 
~/cups/lpoptions

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

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

[Touch-packages] [Bug 1730469] Re: Display session freezes constitently on login after Win10 dual boot crash - Ubuntu 16.04

[Maxime Chambonnet]

Update : the issue looks solved.
I reinstalled all packets containing gtk unity x11, then all xorg packets, and 
those latters seem to have fixed it.

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

Title:
  Display session freezes constitently on login after Win10 dual boot
  crash - Ubuntu 16.04

Status in xorg package in Ubuntu:
  New

Bug description:
  Hello,
  I have a Sandybridge-B970 X301-Asus laptop. I am used to dual boot on it : 
win10 and Ubuntu Xenial on a 275 GB SSD.
  Yesterday I manually forced shut down on win10 which looked hung on 
~"preparation... do not shut down".
  Windows recovered, but Ubuntu was corrupted it seems.
  Grub2 launches, Ubuntu boots. I reach lightdm greeter. Then I cannot input 
mouse nor keyboard, and after a few inputs login prompt hangs. The UI displays 
"connected to ethernet". I cannot Alt Gr Fx to other ttys.
  I can REISUB, I can launch a recovery mode and get a root shell. I can SSH 
after normal boot from an external Debian system.
  Filesystem looks OK. Not sure but for some reason directories seems to have 
appeared in /root (git..)

  My SSD partitions : https://postimg.org/image/2hmo7pgfiz/, on top of
  debug info.

  Best regards!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Mon Nov  6 18:38:53 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family 
Integrated Graphics Controller [1043:14f7]
  InstallationDate: Installed on 2017-03-04 (247 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: ASUSTeK COMPUTER INC. X301A1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-38-generic.efi.signed 
root=UUID=84fd9c9d-fdb2-4ebf-a754-115d068500e0 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/02/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X301A1.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X301A1
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX301A1.204:bd05/02/2012:svnASUSTeKCOMPUTERINC.:pnX301A1:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX301A1:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X301A1
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Mon Nov  6 18:33:32 2017
  xserver.configfile: default
  xserver.devices:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.7
  xserver.video_driver: modeset

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

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

[Touch-packages] [Bug 1276796] Re: Long hostname placeholder for PS1 (\H) fails in Bash

[Marc Bihlmaier]

Same problem here with 16.04 LTS, 17.04 and 17.10 , when not specifying
the FQDN in /etc/hostname:

marc@marcubuntu:~$ hostname --fqdn
marcubuntu.tesdomain.intern
marc@marcubuntu:~$ hostname 
marcubuntu
marc@marcubuntu:~$ head -n 2 /etc/hosts
127.0.0.1   localhost
127.0.1.1   marcubuntu.tesdomain.intern marcubuntu
marc@marcubuntu:~$ grep PS1 .bashrc

PS1='${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\H\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$
 '
PS1='${debian_chroot:+($debian_chroot)}\u@\H:\w\$ '
PS1="\[\e]0;${debian_chroot:+($debian_chroot)}\u@\H: \w\a\]$PS1"
marc@marcubuntu:~$ bash
marc@marcubuntu:~$ cat /etc/hostname
marcubuntu

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

Title:
  Long hostname placeholder for PS1 (\H) fails in Bash

Status in bash package in Ubuntu:
  Confirmed

Bug description:
  When using "\H" in the PS1 prompt value bash is not displaying the
  FQDN but instead only the short form hostname.  This is the same as
  "\h".

  Issue has also been noted at 
  
http://serverfault.com/questions/296970/bash-prompt-on-ubuntu-fqdn-h-same-as-hostname-h
  https://answers.launchpad.net/ubuntu/+source/bash/+question/200900

  This appears related to /etc/hostname only having the host and not the
  FQDN.

  Bash should obtain the \H value from somewhere other than /etc/hostname.
  --- 
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  DistroRelease: Ubuntu 13.10
  InstallationDate: Installed on 2014-01-16 (20 days ago)
  InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Release amd64 
(20131016)
  MarkForUpload: True
  Package: bash 4.2-5ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  Tags:  saucy
  Uname: Linux 3.11.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1706939] Re: A live session can't be shut down due to "[ *** ] (2 of 2) A start job is running for ... (21s / no limit)"

[corrado venturini]

Problem disappeared installing Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20171108)
also disappeared similar bug: 
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1719191

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

Title:
  A live session can't be shut down due to "[ ***  ] (2 of 2) A start
  job is running for ... (21s / no limit)"

Status in Release Notes for Ubuntu:
  Fix Released
Status in gdm3 package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Test case:
  Boot to live session using current or recent image
  Attempt to restart, shutdown or even log out.
  Hangs basically forever with:

  [ ***  ] (2 of 2) A start job is running for Hold until boot process
  finishes up (21s / no limit)

  or

  [ *** ] (2 of 2) A start job is running for Wait for Network to be
  Configured (21s / no limit)

  ---
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gdm3 3.24.2-1ubuntu9
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  CasperVersion: 1.384
  CurrentDesktop: GNOME
  Date: Thu Jul 27 10:15:57 2017
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170723)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm3.custom.conf: 2017-07-27T10:13:04.127685

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1706939/+subscriptions

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

[Touch-packages] [Bug 1729910] Re: lp ignores ~/.cups/lpoptions in 17.10

[Dariusz Gadomski]

** Description changed:

  [Impact]
  
-  * During some refactoring done to cupsGetNamedDest function used in
+  * During some refactoring done to cupsGetNamedDest function used in
  many different parts of the code a regression has been introduced
  causing the per-user default printer setting (in ~/.cups/lpoptions) to
  be ignored.
  
+ This bug has been introduced in Artful due to the refactoring. Earlier
+ releases are fine, similarly this bug is fixed upstream for Bionic.
+ 
  [Test Case]
  
-  1. Make sure at least 2 printers are set up in cups.
-  2. Set one of them as global default.
-  3. Create a user default setting (~/.cups/lpoptions) with the other printer 
set as default:
+  1. Make sure at least 2 printers are set up in cups.
+  2. Set one of them as global default.
+  3. Create a user default setting (~/.cups/lpoptions) with the other printer 
set as default:
  Default other_printer
-  4. Run lpstat -d.
+  4. Run lpstat -d.
  
  Expected result:
  User default printer is displayed.
  
  Actual result:
  Global default printer is displayed.
  
  [Regression Potential]
  
-  * The regression potential is minial, as this is a very simple bugfix and is 
already included in the latest (2.2.5+) releases of cups (including Bionic).
-  * The only setups affected may be those depending (possibly unintentionally) 
on the incorrect behavior. Their users may observe default printer change.
+  * The regression potential is minial, as this is a very simple bugfix and is 
already included in the latest (2.2.5+) releases of cups (including Bionic).
+  * The only setups affected may be those depending (possibly unintentionally) 
on the incorrect behavior. Their users may observe default printer change.
  
  [Other Info]
-  
-  * Original bug description
+ 
+  * Original bug description
  
  LP ignores the settings defined in ~/cups/lpoptions in artful
  
  Steps to reproduce:
  
  1) Define a default print in lpoptions that differs from one in 
/etc/cups/printers.conf
  2) Execute lpstat -d
  3) Above will output default defined in prints.conf instead of 
~/cups/lpoptions

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

Title:
  lp ignores ~/.cups/lpoptions in 17.10

Status in cups package in Ubuntu:
  Fix Released
Status in cups source package in Artful:
  In Progress

Bug description:
  [Impact]

   * During some refactoring done to cupsGetNamedDest function used in
  many different parts of the code a regression has been introduced
  causing the per-user default printer setting (in ~/.cups/lpoptions) to
  be ignored.

  This bug has been introduced in Artful due to the refactoring. Earlier
  releases are fine, similarly this bug is fixed upstream for Bionic.

  [Test Case]

   1. Make sure at least 2 printers are set up in cups.
   2. Set one of them as global default.
   3. Create a user default setting (~/.cups/lpoptions) with the other printer 
set as default:
  Default other_printer
   4. Run lpstat -d.

  Expected result:
  User default printer is displayed.

  Actual result:
  Global default printer is displayed.

  [Regression Potential]

   * The regression potential is minial, as this is a very simple bugfix and is 
already included in the latest (2.2.5+) releases of cups (including Bionic).
   * The only setups affected may be those depending (possibly unintentionally) 
on the incorrect behavior. Their users may observe default printer change.

  [Other Info]

   * Original bug description

  LP ignores the settings defined in ~/cups/lpoptions in artful

  Steps to reproduce:

  1) Define a default print in lpoptions that differs from one in 
/etc/cups/printers.conf
  2) Execute lpstat -d
  3) Above will output default defined in prints.conf instead of 
~/cups/lpoptions

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

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

[Touch-packages] [Bug 1729910] Re: lp ignores ~/.cups/lpoptions in 17.10

[Eric Desrochers]

** Tags added: sts-sponsor-slashd

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

Title:
  lp ignores ~/.cups/lpoptions in 17.10

Status in cups package in Ubuntu:
  Fix Released
Status in cups source package in Artful:
  In Progress

Bug description:
  [Impact]

   * During some refactoring done to cupsGetNamedDest function used in
  many different parts of the code a regression has been introduced
  causing the per-user default printer setting (in ~/.cups/lpoptions) to
  be ignored.

  This bug has been introduced in Artful due to the refactoring. Earlier
  releases are fine, similarly this bug is fixed upstream for Bionic.

  [Test Case]

   1. Make sure at least 2 printers are set up in cups.
   2. Set one of them as global default.
   3. Create a user default setting (~/.cups/lpoptions) with the other printer 
set as default:
  Default other_printer
   4. Run lpstat -d.

  Expected result:
  User default printer is displayed.

  Actual result:
  Global default printer is displayed.

  [Regression Potential]

   * The regression potential is minial, as this is a very simple bugfix and is 
already included in the latest (2.2.5+) releases of cups (including Bionic).
   * The only setups affected may be those depending (possibly unintentionally) 
on the incorrect behavior. Their users may observe default printer change.

  [Other Info]

   * Original bug description

  LP ignores the settings defined in ~/cups/lpoptions in artful

  Steps to reproduce:

  1) Define a default print in lpoptions that differs from one in 
/etc/cups/printers.conf
  2) Execute lpstat -d
  3) Above will output default defined in prints.conf instead of 
~/cups/lpoptions

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

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

[Touch-packages] [Bug 1510570] Re: Bluetooth LE pairing fail

[Yuan-Chen Cheng]

** Also affects: oem-priority
   Importance: Undecided
   Status: New

** Changed in: oem-priority
   Importance: Undecided => Critical

** Changed in: oem-priority
   Status: New => Confirmed

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

Title:
  Bluetooth LE pairing fail

Status in OEM Priority Project:
  Confirmed
Status in bluez package in Ubuntu:
  Fix Released
Status in bluez source package in Xenial:
  New

Bug description:
  [Impact]

  When the Bluetooth adapter is not powered on it is not possible to use
  it in normal way. We used to have a hack to force powering on by using
  an udev rule but this doe snot work anymore. Luckily the BlueZ has
  introduced "AutoEnable" option that makes the stack power on adapters by
  itself.

  Backporting this to xenial will improve life of the desktop users and
  will not require them to hack the solution on their own. The fix itself
  uses the well known solution to this problem that is floating around
  there for a while.

  The upload fixes the bug by enabling the 'AutoEnable' option in the
  bluetoothd config file.

  [Original Report]

  . 15.10 we now have bluez 5 so we can pair BLE devices like the
  Microsoft Arc Touch Bluetooth Mouse.

  But this pairing doesn't work very well. Mouse is seen but pairing fail.
  More information: https://bugzilla.kernel.org/show_bug.cgi?id=104011#c5

  This is due to udev rule that use "hcitool" to power on device.
  Hopefully, bluez 5.35 has a new parameter "AutoEnable" who can be used
  instead of udev rules.

  here is a commit with this parameter:
  http://bazaar.launchpad.net/~guilhem-fr/bluez/autoenable/revision/138

  [Test Case]

  Edit the /etc/bluetooth/main.conf and disable the 'AutoEnable' option.
  Remove file 50-bluetooth-hci-auto-poweron.rules located in
  /lib/udev/rules.d. Now reboot the machine. The BT adapter shall be
  powered off now.

  [Regression Potential]

  Cannot think of any

  [Other Info]

  This fix is included in the development release, see:
  http://bazaar.launchpad.net/~bluetooth/bluez/ubuntu-zesty/revision/22

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

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

[Touch-packages] [Bug 696435] Re: wait-for-root fails to detect nbd root

[Kleber Sacilotto de Souza]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-xenial

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

Title:
  wait-for-root fails to detect nbd root

Status in linux package in Ubuntu:
  Fix Released
Status in nbd package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed
Status in systemd source package in Xenial:
  Confirmed

Bug description:
  [Impact]
  Kernel does not generate any events when ndb-client connects /dev/nbd0 
devices, therefore it is impossible to monitor/react to the state of /dev/nbd0.

  [Fix]
  Generate change uevent when size of /dev/nbd0 changes

  [Testcase]
  * Start udevadm monitor
  * modprobe nbd
  * use ndb-client to connect something to /dev/nbd0
  * observe that there are change udev events generated on /dev/nbd0 itself

  [Regression Potential]
  There is no change to existing uevents, or their ordering.
  There is now an addition change event which will cause systemd to mark ndb 
devices as ready and trigger appropriate actions

  [Original Bug Report]

  When using an nbd root, wait-for-root blocks for 30 seconds before
  booting continues successfully.

  Using Ubuntu Natty, related packages versions:
  nbd-client 1:2.9.16-6ubuntu1
  initramfs-tools 0.98.1ubuntu9

  The wait-for-root call from /usr/share/initramfs-tools/scripts/local:
   while [ -z "${FSTYPE}" ]; do
    FSTYPE=$(wait-for-root "${ROOT}" ${ROOTDELAY:-30})

    # Run failure hooks, hoping one of them can fix up the system
    # and we can restart the wait loop.  If they all fail, abort
    # and move on to the panic handler and shell.
    if [ -z "${FSTYPE}" ] && ! try_failure_hooks; then
     break
    fi
   done

  I replaced wait-for-root with a sh script that did `set >&2`, here are the 
relevant environment variables at the time wait-for-root was called:
  ROOT='/dev/nbd0'
  ROOTDELAY=''
  ROOTFLAGS=''
  ROOTFSTYPE=''
  nbdroot='192.168.0.1,2011'

  It's probably worth noting that "nbd0: unknown partition table" was
  displayed asynchronously 1-2 seconds after wait-for-root was invoked
  and while it was still waiting. But I tried adding a "sleep 5" as the
  last line of local-top/nbd, so that the nbd message was displayed a
  lot before wait-for-root was called, and it didn't make a difference.
  So I don't think a race condition is involved in this problem.

  Temporarily I'm passing rootdelay=1 in the kernel command line to work
  around the problem.

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

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

[Touch-packages] [Bug 1729910] Re: lp ignores ~/.cups/lpoptions in 17.10

[Dariusz Gadomski]

SRU proposal for Artful.

** Patch removed: "artful_cups_2.2.4-7ubuntu3.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1729910/+attachment/5005833/+files/artful_cups_2.2.4-7ubuntu3.debdiff

** Patch added: "artful_cups_2.2.4-7ubuntu3.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1729910/+attachment/5005852/+files/artful_cups_2.2.4-7ubuntu3.debdiff

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

Title:
  lp ignores ~/.cups/lpoptions in 17.10

Status in cups package in Ubuntu:
  Fix Released
Status in cups source package in Artful:
  In Progress

Bug description:
  [Impact]

   * During some refactoring done to cupsGetNamedDest function used in
  many different parts of the code a regression has been introduced
  causing the per-user default printer setting (in ~/.cups/lpoptions) to
  be ignored.

  [Test Case]

   1. Make sure at least 2 printers are set up in cups.
   2. Set one of them as global default.
   3. Create a user default setting (~/.cups/lpoptions) with the other printer 
set as default:
  Default other_printer
   4. Run lpstat -d.

  Expected result:
  User default printer is displayed.

  Actual result:
  Global default printer is displayed.

  [Regression Potential]

   * The regression potential is minial, as this is a very simple bugfix and is 
already included in the latest (2.2.5+) releases of cups (including Bionic).
   * The only setups affected may be those depending (possibly unintentionally) 
on the incorrect behavior. Their users may observe default printer change.

  [Other Info]
   
   * Original bug description

  LP ignores the settings defined in ~/cups/lpoptions in artful

  Steps to reproduce:

  1) Define a default print in lpoptions that differs from one in 
/etc/cups/printers.conf
  2) Execute lpstat -d
  3) Above will output default defined in prints.conf instead of 
~/cups/lpoptions

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

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

[Touch-packages] [Bug 1729910] Re: lp ignores ~/.cups/lpoptions in 17.10

[Eric Desrochers]

** Changed in: cups (Ubuntu Artful)
   Status: Triaged => In Progress

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

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

Title:
  lp ignores ~/.cups/lpoptions in 17.10

Status in cups package in Ubuntu:
  Fix Released
Status in cups source package in Artful:
  In Progress

Bug description:
  [Impact]

   * During some refactoring done to cupsGetNamedDest function used in
  many different parts of the code a regression has been introduced
  causing the per-user default printer setting (in ~/.cups/lpoptions) to
  be ignored.

  [Test Case]

   1. Make sure at least 2 printers are set up in cups.
   2. Set one of them as global default.
   3. Create a user default setting (~/.cups/lpoptions) with the other printer 
set as default:
  Default other_printer
   4. Run lpstat -d.

  Expected result:
  User default printer is displayed.

  Actual result:
  Global default printer is displayed.

  [Regression Potential]

   * The regression potential is minial, as this is a very simple bugfix and is 
already included in the latest (2.2.5+) releases of cups (including Bionic).
   * The only setups affected may be those depending (possibly unintentionally) 
on the incorrect behavior. Their users may observe default printer change.

  [Other Info]
   
   * Original bug description

  LP ignores the settings defined in ~/cups/lpoptions in artful

  Steps to reproduce:

  1) Define a default print in lpoptions that differs from one in 
/etc/cups/printers.conf
  2) Execute lpstat -d
  3) Above will output default defined in prints.conf instead of 
~/cups/lpoptions

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

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

[Touch-packages] [Bug 1729910] Re: lp ignores ~/.cups/lpoptions in 17.10

[Dariusz Gadomski]

** Description changed:

+ [Impact]
+ 
+  * During some refactoring done to cupsGetNamedDest function used in
+ many different parts of the code a regression has been introduced
+ causing the per-user default printer setting (in ~/.cups/lpoptions) to
+ be ignored.
+ 
+ [Test Case]
+ 
+  1. Make sure at least 2 printers are set up in cups.
+  2. Set one of them as global default.
+  3. Create a user default setting (~/.cups/lpoptions) with the other printer 
set as default:
+ Default other_printer
+  4. Run lpstat -d.
+ 
+ Expected result:
+ User default printer is displayed.
+ 
+ Actual result:
+ Global default printer is displayed.
+ 
+ [Regression Potential]
+ 
+  * The regression potential is minial, as this is a very simple bugfix and is 
already included in the latest (2.2.5+) releases of cups (including Bionic).
+  * The only setups affected may be those depending (possibly unintentionally) 
on the incorrect behavior. Their users may observe default printer change.
+ 
+ [Other Info]
+  
+  * Original bug description
+ 
  LP ignores the settings defined in ~/cups/lpoptions in artful
  
  Steps to reproduce:
  
  1) Define a default print in lpoptions that differs from one in 
/etc/cups/printers.conf
  2) Execute lpstat -d
  3) Above will output default defined in prints.conf instead of 
~/cups/lpoptions

** Changed in: cups (Ubuntu Artful)
 Assignee: (unassigned) => Dariusz Gadomski (dgadomski)

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

Title:
  lp ignores ~/.cups/lpoptions in 17.10

Status in cups package in Ubuntu:
  Fix Released
Status in cups source package in Artful:
  Triaged

Bug description:
  [Impact]

   * During some refactoring done to cupsGetNamedDest function used in
  many different parts of the code a regression has been introduced
  causing the per-user default printer setting (in ~/.cups/lpoptions) to
  be ignored.

  [Test Case]

   1. Make sure at least 2 printers are set up in cups.
   2. Set one of them as global default.
   3. Create a user default setting (~/.cups/lpoptions) with the other printer 
set as default:
  Default other_printer
   4. Run lpstat -d.

  Expected result:
  User default printer is displayed.

  Actual result:
  Global default printer is displayed.

  [Regression Potential]

   * The regression potential is minial, as this is a very simple bugfix and is 
already included in the latest (2.2.5+) releases of cups (including Bionic).
   * The only setups affected may be those depending (possibly unintentionally) 
on the incorrect behavior. Their users may observe default printer change.

  [Other Info]
   
   * Original bug description

  LP ignores the settings defined in ~/cups/lpoptions in artful

  Steps to reproduce:

  1) Define a default print in lpoptions that differs from one in 
/etc/cups/printers.conf
  2) Execute lpstat -d
  3) Above will output default defined in prints.conf instead of 
~/cups/lpoptions

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

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

[Touch-packages] [Bug 1728773] Re: [235.2ubuntu1] systemd upgrade set a read only filesystem

[Dimitri John Ledkov]

the ordering cycle... if one looks for full journal log, rather than
just that line is due to freindly recovery unit, not anything systemd
ships.

Sharing configs between multiple distributions is not guaranteed to work
correctly, due to app settings changes/migrations between distributions.

Booting systemd from proposed, works correctly here for me with/without
full disk encryption.

** Tags removed: block-proposed

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

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

Title:
  [235.2ubuntu1] systemd upgrade set a read only filesystem

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  systemd update on Bionic  ends with a read only filesystem, and startx
  also fails.

  Looks like it is related to the tmpfiles right change in systemd:

  [ Michael Biebl ]
  * New upstream version 235
  - cryptsetup-generator: use remote-cryptsetup.target when _netdev is
  present (Closes: #852534)
  - tmpfiles: change btmp mode 0600 → 0660 (Closes: #870638)
  ---
  
  note: ran apport-collect from a 17.10 install, so the info is not about the 
Bionic install indeed.
  

  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: systemd 234-2ubuntu12.1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=8a00317c-669e-447c-bc40-1e06010b49ca ro
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P7.00
  dmi.board.name: B150M-HDV
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP7.00:bd10/07/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-HDV:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Touch-packages] [Bug 1729910] Re: lp ignores ~/.cups/lpoptions in 17.10

[Dariusz Gadomski]

SRU proposal for artful.

Previous releases are not affected, as this was introduced with some
refactoring done to cupsGetNamedDest (cups/dest.c).

** Patch added: "artful_cups_2.2.4-7ubuntu3.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1729910/+attachment/5005833/+files/artful_cups_2.2.4-7ubuntu3.debdiff

** Tags added: sts sts-sru-needed

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

Title:
  lp ignores ~/.cups/lpoptions in 17.10

Status in cups package in Ubuntu:
  Fix Released
Status in cups source package in Artful:
  Triaged

Bug description:
  [Impact]

   * During some refactoring done to cupsGetNamedDest function used in
  many different parts of the code a regression has been introduced
  causing the per-user default printer setting (in ~/.cups/lpoptions) to
  be ignored.

  [Test Case]

   1. Make sure at least 2 printers are set up in cups.
   2. Set one of them as global default.
   3. Create a user default setting (~/.cups/lpoptions) with the other printer 
set as default:
  Default other_printer
   4. Run lpstat -d.

  Expected result:
  User default printer is displayed.

  Actual result:
  Global default printer is displayed.

  [Regression Potential]

   * The regression potential is minial, as this is a very simple bugfix and is 
already included in the latest (2.2.5+) releases of cups (including Bionic).
   * The only setups affected may be those depending (possibly unintentionally) 
on the incorrect behavior. Their users may observe default printer change.

  [Other Info]
   
   * Original bug description

  LP ignores the settings defined in ~/cups/lpoptions in artful

  Steps to reproduce:

  1) Define a default print in lpoptions that differs from one in 
/etc/cups/printers.conf
  2) Execute lpstat -d
  3) Above will output default defined in prints.conf instead of 
~/cups/lpoptions

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

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

[Touch-packages] [Bug 1722528] Re: find buffer-overflow with -printf '%T+'

[Bug Watch Updater]

** Changed in: findutils (Debian)
   Status: Unknown => Fix Released

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

Title:
   find buffer-overflow with -printf '%T+'

Status in findutils:
  Unknown
Status in findutils package in Ubuntu:
  Confirmed
Status in findutils package in Debian:
  Fix Released

Bug description:
  This has already been reported upstream. Just reporting it here
  because I observed it in artful.

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

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

[Touch-packages] [Bug 1730744] Re: sudo is slow (10 seconds) when hostname is not resolvable

[Dimitri John Ledkov]

I do wonder if we need libnss-myhostname to be installed. I hoped that
with the stub resolver, we do not. But it depends if the hostname change
made it into resolved state or not.

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

Title:
  sudo is slow (10 seconds) when hostname is not resolvable

Status in systemd package in Ubuntu:
  New

Bug description:
  I'm seeing very slow 'sudo' times in a qemu guest when the host uses 
systemd-resolved.
  If I change /etc/resolv.conf on the host to point directly to a dns server 
(8.8.8.8) then the problem goes away.

  
  To recreate, you can download a cloud image and boot it under qemu with a 
command line like:
cloud-localds seed.img user-data meta-data 
qemu-system-x86_64 -enable-kvm \
   -device virtio-net-pci,netdev=net00 \
   -netdev type=user,id=net00 \
   -drive file=root.img,id=disk00,if=none,index=0 \
   -device virtio-blk,drive=disk00,serial=root.img \
   -drive file=seed.img,id=disk01,if=none,index=1 \
   -device virtio-blk,drive=disk01,serial=seed.img \
   -m 768

  Make sure that your hostname does not resolve (change it to 'bogus-host1').
  Log into the guest and then just try sudo, you'll see something like:
  # time sudo ls
  sudo: unable to resolve host rooturl-trusty

  real0m10.029s
  user0m0.006s
  sys 0m0.011s

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

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

[Touch-packages] [Bug 1730915] Re: mount overlayfs command in lxc-test-unpriv is missing a workdir assignment

[Po-Hsu Lin]

Pull request:
https://github.com/lxc/lxc/pull/1908

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

Title:
  mount overlayfs command in lxc-test-unpriv is missing a workdir
  assignment

Status in lxc package in Ubuntu:
  In Progress

Bug description:
  While running the lxc-test-unpriv test, it will complain about:

  $ sudo /usr/bin/lxc-test-unpriv 
  mount: wrong fs type, bad option, bad superblock on none,
 missing codepage or helper program, or other error

 In some cases useful info is found in syslog - try
 dmesg | tail or so.

  Check the dmesg output it will tell you that the mount option needs a workdir 
assignment as well:
  $ dmesg
  [89761.978272] overlayfs: missing 'workdir'

  This error does not affect the test result, but good to be fixed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lxc-tests 2.0.8-0ubuntu1~16.04.2
  ProcVersionSignature: User Name 4.4.0-98.121-generic 4.4.90
  Uname: Linux 4.4.0-98-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Wed Nov  8 08:50:31 2017
  KernLog:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: lxc
  UpgradeStatus: No upgrade log present (probably fresh install)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx

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

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

[Touch-packages] [Bug 1730915] [NEW] mount overlayfs command in lxc-test-unpriv is missing a workdir assignment

[Po-Hsu Lin]

Public bug reported:

While running the lxc-test-unpriv test, it will complain about:

$ sudo /usr/bin/lxc-test-unpriv 
mount: wrong fs type, bad option, bad superblock on none,
   missing codepage or helper program, or other error

   In some cases useful info is found in syslog - try
   dmesg | tail or so.

Check the dmesg output it will tell you that the mount option needs a workdir 
assignment as well:
$ dmesg
[89761.978272] overlayfs: missing 'workdir'

This error does not affect the test result, but good to be fixed.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: lxc-tests 2.0.8-0ubuntu1~16.04.2
ProcVersionSignature: User Name 4.4.0-98.121-generic 4.4.90
Uname: Linux 4.4.0-98-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Wed Nov  8 08:50:31 2017
KernLog:
 
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: lxc
UpgradeStatus: No upgrade log present (probably fresh install)
defaults.conf:
 lxc.network.type = veth
 lxc.network.link = lxcbr0
 lxc.network.flags = up
 lxc.network.hwaddr = 00:16:3e:xx:xx:xx

** Affects: lxc (Ubuntu)
 Importance: Undecided
 Assignee: Po-Hsu Lin (cypressyew)
 Status: In Progress


** Tags: amd64 apport-bug uec-images xenial

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

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

Title:
  mount overlayfs command in lxc-test-unpriv is missing a workdir
  assignment

Status in lxc package in Ubuntu:
  In Progress

Bug description:
  While running the lxc-test-unpriv test, it will complain about:

  $ sudo /usr/bin/lxc-test-unpriv 
  mount: wrong fs type, bad option, bad superblock on none,
 missing codepage or helper program, or other error

 In some cases useful info is found in syslog - try
 dmesg | tail or so.

  Check the dmesg output it will tell you that the mount option needs a workdir 
assignment as well:
  $ dmesg
  [89761.978272] overlayfs: missing 'workdir'

  This error does not affect the test result, but good to be fixed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lxc-tests 2.0.8-0ubuntu1~16.04.2
  ProcVersionSignature: User Name 4.4.0-98.121-generic 4.4.90
  Uname: Linux 4.4.0-98-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Wed Nov  8 08:50:31 2017
  KernLog:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: lxc
  UpgradeStatus: No upgrade log present (probably fresh install)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx

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

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

[Touch-packages] [Bug 1720126]

[Phil]

A real fix for this issue has been accepted upstream and was applied to
net-next branch:

commit 2d34851cd341f0e1b3fc17ca3e6e874229f3a1f8
Author: Hangbin Liu 
Date:   Thu Oct 26 09:41:46 2017 +0800

lib/libnetlink: re malloc buff if size is not enough

commit 86bf43c7c2fdc33d7c021b4a1add1c8facbca51c
Author: Hangbin Liu 
Date:   Thu Oct 26 09:41:47 2017 +0800

lib/libnetlink: update rtnl_talk to support malloc buff at run time


Alan, are you able to compile iproute2 by yourself? If so, could you please
give upstream's 'net-next' branch a try? It should solve the issue you are
seeing.

Thanks, Phil

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

Title:
  [ip link] Message truncated error for large number of passthrough VFs

Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Trusty:
  Fix Committed
Status in iproute2 source package in Xenial:
  Fix Released
Status in iproute2 source package in Zesty:
  Fix Released
Status in iproute2 package in CentOS:
  In Progress

Bug description:
  [Impact]

  When querying a Physical Function netdev with a large amount of VF's
  (more than 30), the resulting return message can overflow the 16K
  netlink message buffer.

  This can be fixed by enabling message peeking on the socket and
  resizing the buffer on receive, or by simply enlarging the receive
  buffer.

  Since there's an upper limit to the number of VF's per PF, it's
  relatively sane to just enlarge the receive buffer. Please see the
  attached patch.

  [Test Case]

  # Set up 60 VF's on an SR-IOV device
  ip link show > /dev/null

  Observe the following:
  Message truncated
  Message truncated
  Message truncated

  [Regression Potential]

  1) Applications relying on the broken behaviour will need to be updated, but 
it would be a really dubious use case.
  2) Increasing the rx buffer size increases the memory footprint (but 
realistically, this is tiny).
  3) Extra processing time is now needed to parse the larger buffer, in the 
case that a call to "ip link" is on the critical time path of an application, 
(called multiple times in a tight loop, for example), it would affect load.

  [Other Info]

  Observed on Ubuntu kernel 4.4.0-93-generic on both 14.04 and 16.04

  
=
  Ubuntu16 system

  stack@cluster04:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial

  stack@cluster04:~$ uname -r
  4.4.0-93-generic

  stack@cluster04:~$ apt-cache policy iproute2
  iproute2:
    Installed: 4.3.0-1ubuntu3.16.04.1
  Version table:
  *** 4.3.0-1ubuntu3.16.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  
=

  Ubuntu14 system:
  root@boomslang:~# lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 14.04.3 LTS
  Release:  14.04
  Codename: trusty

  root@boomslang:~# uname -r
  4.4.0-96-generic

  root@boomslang:~# apt-cache policy iproute2
  iproute2:
    Installed: 3.12.0-2ubuntu1
    Version table:
   *** 3.12.0-2ubuntu1 0
  500 http://za.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages

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

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

[Touch-packages] [Bug 1730914] [NEW] upgrade to Ubuntu 17.10 => send_packet: Operation not permitted

[G.M.]

Public bug reported:

Hi,

Since I upgraded to Ubuntu 17.10, I have a lot of lines like the
following in my logs...

Nov  8 09:33:43 gotm dhclient[1788]: DHCPREQUEST of 192.168.30.xx on wlan8 to 
192.168.30.yy port 67 (xid=0x54c31dc8)
Nov  8 09:33:43 gotm dhclient[1788]: send_packet: Operation not permitted
Nov  8 09:33:43 gotm dhclient[1788]: dhclient.c:2743: Failed to send 300 byte 
long packet over fallback interface.

** Affects: isc-dhcp (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

  Hi,
  
  Since I upgraded to Ubuntu 17.10, I have a lot of lines like the
  following in my logs...
  
- Nov  8 09:33:43 gyom dhclient[1788]: DHCPREQUEST of 192.168.30.xx on wlan1 to 
192.168.30.yy port 67 (xid=0x54c31dc8)
- Nov  8 09:33:43 gyom dhclient[1788]: send_packet: Operation not permitted
- Nov  8 09:33:43 gyom dhclient[1788]: dhclient.c:2743: Failed to send 300 byte 
long packet over fallback interface.
+ Nov  8 09:33:43 gotm dhclient[1788]: DHCPREQUEST of 192.168.30.xx on wlan8 to 
192.168.30.yy port 67 (xid=0x54c31dc8)
+ Nov  8 09:33:43 gotm dhclient[1788]: send_packet: Operation not permitted
+ Nov  8 09:33:43 gotm dhclient[1788]: dhclient.c:2743: Failed to send 300 byte 
long packet over fallback interface.

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

Title:
  upgrade to Ubuntu 17.10 => send_packet: Operation not permitted

Status in isc-dhcp package in Ubuntu:
  New

Bug description:
  Hi,

  Since I upgraded to Ubuntu 17.10, I have a lot of lines like the
  following in my logs...

  Nov  8 09:33:43 gotm dhclient[1788]: DHCPREQUEST of 192.168.30.xx on wlan8 to 
192.168.30.yy port 67 (xid=0x54c31dc8)
  Nov  8 09:33:43 gotm dhclient[1788]: send_packet: Operation not permitted
  Nov  8 09:33:43 gotm dhclient[1788]: dhclient.c:2743: Failed to send 300 byte 
long packet over fallback interface.

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

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

[Touch-packages] [Bug 1730908] [NEW] [ 1549.847151] audit: type=1400 audit(1510129355.497:61): apparmor="DENIED" operation="file_mmap" profile="/usr/bin/evince" name="/usr/lib/x86_64-linux-gnu/libprox

[G.M.]

Public bug reported:

Since I installed Ubuntu 17.10 I cannot print anymore.

The only thing I see in the logs are many lines like the following:
[ 1549.847151] audit: type=1400 audit(1510129355.497:61): apparmor="DENIED" 
operation="file_mmap" profile="/usr/bin/evince" 
name="/usr/lib/x86_64-linux-gnu/libproxy/0.4.14/modules/network_networkmanager.so"
 pid=2062 comm="evince" requested_mask="m" denied_mask="m" fsuid=1000 ouid=0

I'm not sure it is the cause of my problems, but there is at least a
problem with apparmor's configuration in Ubuntu 17.10

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

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

Title:
  [ 1549.847151] audit: type=1400 audit(1510129355.497:61):
  apparmor="DENIED" operation="file_mmap" profile="/usr/bin/evince"
  name="/usr/lib/x86_64-linux-
  gnu/libproxy/0.4.14/modules/network_networkmanager.so" pid=2062
  comm="evince" requested_mask="m" denied_mask="m" fsuid=1000 ouid=0

Status in apparmor package in Ubuntu:
  New

Bug description:
  Since I installed Ubuntu 17.10 I cannot print anymore.

  The only thing I see in the logs are many lines like the following:
  [ 1549.847151] audit: type=1400 audit(1510129355.497:61): apparmor="DENIED" 
operation="file_mmap" profile="/usr/bin/evince" 
name="/usr/lib/x86_64-linux-gnu/libproxy/0.4.14/modules/network_networkmanager.so"
 pid=2062 comm="evince" requested_mask="m" denied_mask="m" fsuid=1000 ouid=0

  I'm not sure it is the cause of my problems, but there is at least a
  problem with apparmor's configuration in Ubuntu 17.10

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

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

[Touch-packages] [Bug 1730908] Re: [ 1549.847151] audit: type=1400 audit(1510129355.497:61): apparmor="DENIED" operation="file_mmap" profile="/usr/bin/evince" name="/usr/lib/x86_64-linux-gnu/libproxy/

[G.M.]

There are apparently also problems with ntpd...

Nov  8 09:35:00 gyom kernel: [ 2294.930091] audit: type=1400
audit(1510130100.589:62): apparmor="DENIED" operation="sendmsg"
info="Failed name lookup - disconnected path" error=-13
profile="/usr/sbin/ntpd" name="run/systemd/journal/dev-log" pid=1883
comm="ntpd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0

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

Title:
  [ 1549.847151] audit: type=1400 audit(1510129355.497:61):
  apparmor="DENIED" operation="file_mmap" profile="/usr/bin/evince"
  name="/usr/lib/x86_64-linux-
  gnu/libproxy/0.4.14/modules/network_networkmanager.so" pid=2062
  comm="evince" requested_mask="m" denied_mask="m" fsuid=1000 ouid=0

Status in apparmor package in Ubuntu:
  New

Bug description:
  Since I installed Ubuntu 17.10 I cannot print anymore.

  The only thing I see in the logs are many lines like the following:
  [ 1549.847151] audit: type=1400 audit(1510129355.497:61): apparmor="DENIED" 
operation="file_mmap" profile="/usr/bin/evince" 
name="/usr/lib/x86_64-linux-gnu/libproxy/0.4.14/modules/network_networkmanager.so"
 pid=2062 comm="evince" requested_mask="m" denied_mask="m" fsuid=1000 ouid=0

  I'm not sure it is the cause of my problems, but there is at least a
  problem with apparmor's configuration in Ubuntu 17.10

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

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