date:20190408

** Summary changed:

- SRU: update Python 3.7 to the 3.7.3 release and 3.6 to the 3.6.8 release
+ SRU: update Python 2.7 to 2.7.16, Python 3.7 to 3.7.3 and 3.6 to 3.6.8

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

** Also affects: python2.7 (Ubuntu)
   Importance: Undecided
   Status: New

** Description changed:

  SRU: update Python 3.7 to the 3.7.3 release, update Python 3.6 to the
  3.6.8 release.
  
  python3-stdlib-extensions also updates the modules to the 3.6.8 release
  for Python 3.6.
  
  Acceptance Criteria: The package builds, and the test suite doesn't show
  regressions. The test suite passes in the autopkg tests.  The new
  packages don't cause regressions in a test rebuild of the main
  component.
  
+ 
http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20190404-cosmic.html
+ 
http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20190404-gcc8-cosmic.html
+ 
+ The test rebuilds are finished, and don't show any regressions for the
+ main component.
+ 
  Regression Potential: Python 3.7 isn't used by default, so we don't have many 
default users.
  Regression Potential: Python 3.6 could see some regressions, although we are 
trying to minimize the risk by doing the test rebuild.

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

Title:
  SRU: update Python 2.7 to 2.7.16, Python 3.7 to 3.7.3 and 3.6 to 3.6.8

Status in python-stdlib-extensions package in Ubuntu:
  New
Status in python2.7 package in Ubuntu:
  New
Status in python3-stdlib-extensions package in Ubuntu:
  New
Status in python3.6 package in Ubuntu:
  New
Status in python3.7 package in Ubuntu:
  New

Bug description:
  SRU: update Python 3.7 to the 3.7.3 release, update Python 3.6 to the
  3.6.8 release.

  python3-stdlib-extensions also updates the modules to the 3.6.8
  release for Python 3.6.

  Acceptance Criteria: The package builds, and the test suite doesn't
  show regressions. The test suite passes in the autopkg tests.  The new
  packages don't cause regressions in a test rebuild of the main
  component.

  
http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20190404-cosmic.html
  
http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20190404-gcc8-cosmic.html

  The test rebuilds are finished, and don't show any regressions for the
  main component.

  Regression Potential: Python 3.7 isn't used by default, so we don't have many 
default users.
  Regression Potential: Python 3.6 could see some regressions, although we are 
trying to minimize the risk by doing the test rebuild.

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

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

[Touch-packages] [Bug 1823834] [NEW] Firefox doesn't correctly display color emoji because Dejavu includes b emoji

2019-04-08 Thread Asif Youssuff

Public bug reported:

As seen on:

https://bugzilla.mozilla.org/show_bug.cgi?id=1516445
https://bugzilla.mozilla.org/show_bug.cgi?id=1323050

STR:

I am using Firefox nightly, but the installed Firefox built into ubuntu
works as well. Firefox comes with a font "TwemojiMozilla.ttf" which
includes emojis in color.

1. Go to https://en.wikipedia.org/wiki/Emoji#Unicode_blocks
2. Scroll to row U+1F60x 

What happens:

The emoji are not displayed in color, because Dejvu Sans seems to be
rendered instead of TwemojiMozilla (the font built into Firefox).

Expected result:

Color emoji. Since Dejavu doesn't display color emoji and Firefox was
kind enough to include a font that includes color emoji, Ubuntu's
fontconfig should let Firefox do the right thing.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: fontconfig 2.13.1-2ubuntu2
ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
Uname: Linux 5.0.0-8-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.10-0ubuntu25
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr  9 00:32:37 2019
InstallationDate: Installed on 2018-10-31 (160 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: fontconfig
UpgradeStatus: Upgraded to disco on 2018-11-02 (157 days ago)

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


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

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

Title:
  Firefox doesn't correctly display color emoji because Dejavu includes
  b emoji

Status in fontconfig package in Ubuntu:
  New

Bug description:
  As seen on:

  https://bugzilla.mozilla.org/show_bug.cgi?id=1516445
  https://bugzilla.mozilla.org/show_bug.cgi?id=1323050

  STR:

  I am using Firefox nightly, but the installed Firefox built into
  ubuntu works as well. Firefox comes with a font "TwemojiMozilla.ttf"
  which includes emojis in color.

  1. Go to https://en.wikipedia.org/wiki/Emoji#Unicode_blocks
  2. Scroll to row U+1F60x 

  What happens:

  The emoji are not displayed in color, because Dejvu Sans seems to be
  rendered instead of TwemojiMozilla (the font built into Firefox).

  Expected result:

  Color emoji. Since Dejavu doesn't display color emoji and Firefox was
  kind enough to include a font that includes color emoji, Ubuntu's
  fontconfig should let Firefox do the right thing.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: fontconfig 2.13.1-2ubuntu2
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.10-0ubuntu25
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  9 00:32:37 2019
  InstallationDate: Installed on 2018-10-31 (160 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: fontconfig
  UpgradeStatus: Upgraded to disco on 2018-11-02 (157 days ago)

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

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

[Touch-packages] [Bug 1814905] Re: dash exits when receiving wall message

[Expired for dash (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  dash exits when receiving wall message

Status in dash package in Ubuntu:
  Expired

Bug description:
  When using "/bin/sh" (dash) as a shell for ssh, or just starting
  /bin/sh in a terminal, when the shell receives a wall message (from
  another user or root), it just quits.

  How to reproduce:
  - start a terminal (xterm, gnome-terminal, etc), usually starts with bash
  - from bash run 'sh' command to open a dash shell
  - start another terminal, and run: echo "foo" | wall
  - the broadcast message appears on both terminals
  - in the first terminal you are thrown back to bash, because dash exits

  I've tried this on Ubuntu 14.04, 16.04, 18.04 (64bits) latest updates
  and it's happening on all of them. I've also tried with latest dash
  from git, compiled on Ubuntu 16.04, same problem, that's why I don't
  think it's dash's problem.

  Also tried on CentOS 7, there is no problem there.

  The problem appears this morning (6 February) after updating to latest
  version of 16.04, 18.04. I also have a box with 16.04 but not the
  latest updates, and on that box the problem does not happen.

  If one uses dash as a login shell, and enters on a remote box with SSH
  for example, the connection can be terminated by another user simply
  wall'ing a broadcast message (or a system daemon like NUT). This could
  be taken as a potential security issue.

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

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

[Touch-packages] [Bug 1799048] Re: package libffi6:i386 3.2.1-8 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

[Expired for libffi (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  package libffi6:i386 3.2.1-8 failed to install/upgrade: package is in
  a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in libffi package in Ubuntu:
  Expired

Bug description:
  1 st time system get restart

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libffi6:i386 3.2.1-8
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Sat Oct 20 23:57:30 2018
  Dependencies:
   gcc-8-base 8.2.0-1ubuntu2~18.04
   libc6 2.27-3ubuntu1
   libgcc1 1:8.2.0-1ubuntu2~18.04
  DuplicateSignature:
   package:libffi6:i386:3.2.1-8
   Setting up vlc-plugin-visualization:amd64 (3.0.3-1-1ubuntu1) ...
   dpkg: error processing package libffi6:i386 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2018-10-20 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: i386
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3
  SourcePackage: libffi
  Title: package libffi6:i386 3.2.1-8 failed to install/upgrade: package is in 
a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1814501] Re: package libgssapi-krb5-2:amd64 1.16-2ubuntu0.1 failed to install/upgrade: függőségi hibák - e csomag beállítatlan maradt

[Expired for krb5 (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  package libgssapi-krb5-2:amd64 1.16-2ubuntu0.1 failed to
  install/upgrade: függőségi hibák - e csomag beállítatlan maradt

Status in krb5 package in Ubuntu:
  Expired

Bug description:
  I want it to try installation Google Earth Pro but all time
  collapsing.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libgssapi-krb5-2:amd64 1.16-2ubuntu0.1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  AptOrdering:
   google-earth-pro-stable:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Mon Feb  4 10:23:29 2019
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-osp1-20150720-0
  DpkgHistoryLog:
   Start-Date: 2019-02-04  10:23:09
   Commandline: packagekit role='install-files'
   Requested-By: paluch (1001)
   Install: google-earth-pro-stable:amd64 (7.3.2.5495-r0)
  ErrorMessage: függőségi hibák - e csomag beállítatlan maradt
  InstallationDate: Installed on 2016-10-05 (852 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150720-04:06
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: krb5
  Title: package libgssapi-krb5-2:amd64 1.16-2ubuntu0.1 failed to 
install/upgrade: függőségi hibák - e csomag beállítatlan maradt
  UpgradeStatus: Upgraded to bionic on 2019-01-11 (23 days ago)

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

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

[Touch-packages] [Bug 1823698] Re: dont know

2019-04-08 Thread Daniel van Vugt

** Package changed: xorg (Ubuntu) => 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/1823698

Title:
  dont know

Status in Ubuntu:
  Incomplete

Bug description:
  could be via email ?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
  Uname: Linux 4.15.0-47-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Mon Apr  8 12:14:53 2019
  DistUpgraded: 2018-08-28 23:59:06,593 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 4 Series Chipset Integrated Graphics Controller 
[8086:2e32] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 4 Series Chipset Integrated Graphics 
Controller [1043:836d]
  InstallationDate: Installed on 2012-03-13 (2582 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-47-generic 
root=UUID=b5d5d6d6-6240-4254-9586-c18faee66775 ro splash quiet
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-08-28 (222 days ago)
  dmi.bios.date: 11/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0405
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5G41T-M LX2/GB
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0405:bd11/22/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5G41T-MLX2/GB:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Tue Aug 28 20:10:43 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputMicrosoft Natural® Ergonomic Keyboard 4000 KEYBOARD, id 8
   inputMicrosoft Natural® Ergonomic Keyboard 4000 KEYBOARD, id 9
   inputLogitech USB-PS/2 Optical Mouse MOUSE, id 10
  xserver.errors:
   /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
   /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1432 
   vendor SAM
  xserver.version: 2:1.18.4-0ubuntu0.8

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

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

[Touch-packages] [Bug 1823550] Re: GtkSourceView wrongly has monospaced font in dropdown (context) menu

2019-04-08 Thread Daniel van Vugt

** Tags removed: artful zesty

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

Title:
  GtkSourceView wrongly has monospaced font in dropdown (context) menu

Status in GtkSourceView:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Invalid
Status in gtksourceview3 package in Ubuntu:
  Invalid
Status in mate-themes package in Ubuntu:
  Confirmed
Status in pluma package in Ubuntu:
  Invalid
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 17.04 or later installed
  2. Open any application with GtkSourceView component - such as Pluma, Gedit, 
Giggle, Gitg, gnome-builder and maybe others (see complete list with `apt-cache 
rdepends libgtksourceview-3.0-1`)
  3. Click right mouse button on text zone

  Expected result:
  * dropdown menu has normal font as all other interface elements

  Actual result:
  * dropdwon menu wrongly has monospaced font

  Notes:
  * first seen in 17.04, but persists in 17.10, 18.04 LTS, 18.10, 19.04 
releases.
  * seems to be caused by GTK3 library

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: pluma 1.18.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.10
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sun Apr  7 20:13:24 2019
  InstallationDate: Installed on 2018-08-07 (243 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: pluma
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1823550] Re: GtkSourceView wrongly has monospaced font in dropdown (context) menu

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

** Changed in: mate-themes (Ubuntu)
   Status: New => Confirmed

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

Title:
  GtkSourceView wrongly has monospaced font in dropdown (context) menu

Status in GtkSourceView:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Invalid
Status in gtksourceview3 package in Ubuntu:
  Invalid
Status in mate-themes package in Ubuntu:
  Confirmed
Status in pluma package in Ubuntu:
  Invalid
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 17.04 or later installed
  2. Open any application with GtkSourceView component - such as Pluma, Gedit, 
Giggle, Gitg, gnome-builder and maybe others (see complete list with `apt-cache 
rdepends libgtksourceview-3.0-1`)
  3. Click right mouse button on text zone

  Expected result:
  * dropdown menu has normal font as all other interface elements

  Actual result:
  * dropdwon menu wrongly has monospaced font

  Notes:
  * first seen in 17.04, but persists in 17.10, 18.04 LTS, 18.10, 19.04 
releases.
  * seems to be caused by GTK3 library

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: pluma 1.18.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.10
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sun Apr  7 20:13:24 2019
  InstallationDate: Installed on 2018-08-07 (243 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: pluma
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1823550] Re: GtkSourceView wrongly has monospaced font in dropdown (context) menu

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

** Changed in: ubuntu-themes (Ubuntu)
   Status: New => Confirmed

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

Title:
  GtkSourceView wrongly has monospaced font in dropdown (context) menu

Status in GtkSourceView:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Invalid
Status in gtksourceview3 package in Ubuntu:
  Invalid
Status in mate-themes package in Ubuntu:
  Confirmed
Status in pluma package in Ubuntu:
  Invalid
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 17.04 or later installed
  2. Open any application with GtkSourceView component - such as Pluma, Gedit, 
Giggle, Gitg, gnome-builder and maybe others (see complete list with `apt-cache 
rdepends libgtksourceview-3.0-1`)
  3. Click right mouse button on text zone

  Expected result:
  * dropdown menu has normal font as all other interface elements

  Actual result:
  * dropdwon menu wrongly has monospaced font

  Notes:
  * first seen in 17.04, but persists in 17.10, 18.04 LTS, 18.10, 19.04 
releases.
  * seems to be caused by GTK3 library

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: pluma 1.18.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.10
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sun Apr  7 20:13:24 2019
  InstallationDate: Installed on 2018-08-07 (243 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: pluma
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1742997] Re: Newly installed applications are not showing in "Installed"

2019-04-08 Thread Robert Ancell

I was reproducing this, but when I added instrumentation it started
working. It does reproduce in a VM, so will keep investigating. The code
that adds the installed apps to the installation page seems fairly
robust, so not sure what might be breaking it.

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

Title:
  Newly installed applications are not showing in "Installed"

Status in GNOME Software:
  Expired
Status in gnome-software package in Ubuntu:
  Fix Released
Status in packagekit package in Ubuntu:
  Invalid
Status in gnome-software source package in Bionic:
  Confirmed
Status in packagekit source package in Bionic:
  Invalid

Bug description:
  If you install any application using GNOME Software (Ubuntu Software),
  the newly installed application is not displayed on the "Installed"
  tab. It starts showing after the next system reboot.

  Steps to Reproduce:
  1. Find any application that is not installed and install it.
  2. Switch to the "Installed" tab and try to find the newly installed 
application.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-software/+bug/1742997/+subscriptions

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

[Touch-packages] [Bug 1822426] Re: 19.04 Built in Intel HDA sound is disabled upon resume

2019-04-08 Thread Darin Miller

Sound is still working today with the 4.20.17 kernel.  I will give it
another day before I draw any conclusions.

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

Title:
  19.04 Built in Intel HDA sound is disabled upon resume

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  With 19.04, Intel Corporation 8 Series/C220 Series Chipset High
  Definition Audio Controller intermittently is not enabled when
  resuming from sleep. The HDMI sound device is enabled but that is not
  hooked up on my system.  New with 19.04, when sound works after
  resume, an icon labeled "Built in Audio Stereo" appears during the
  resume process.

  Unsure if this is related, but sound seems to sleep when not in use.
  Launching sound enabled apps produces a quiet "tick, thud" sound as
  sound system turns on.

  When sound is not working, killall pusleaudio "fixes" the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  darin  4814 F pulseaudio
   /dev/snd/controlC1:  darin  4814 F pulseaudio
   /dev/snd/controlC0:  darin  4814 F pulseaudio
  CurrentDesktop: KDE
  Date: Sat Mar 30 10:20:24 2019
  InstallationDate: Installed on 2018-01-13 (441 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180112)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to disco on 2019-03-27 (3 days ago)
  dmi.bios.date: 08/18/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2103
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z87-PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2103:bd08/18/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.sku: All
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

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

[Touch-packages] [Bug 1794629] Re: CVE-2018-15473 - User enumeration vulnerability

2019-04-08 Thread Seth Arnold

Vital, just scanning version banners is what leads to this problem.
Inspecting the package database would be far more reliable.

Thanks

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

Title:
  CVE-2018-15473 - User enumeration vulnerability

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

Bug description:
  https://nvd.nist.gov/vuln/detail/CVE-2018-15473

  OpenSSH through 7.7 is prone to a user enumeration vulnerability due
  to not delaying bailout for an invalid authenticating user until after
  the packet containing the request has been fully parsed, related to
  auth2-gss.c, auth2-hostbased.c, and auth2-pubkey.c.

  Fixed in Debian: https://www.debian.org/security/2018/dsa-4280

  Currently pending triage? https://people.canonical.com/~ubuntu-
  security/cve/2018/CVE-2018-15473.html

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

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

[Touch-packages] [Bug 1794629] Re: CVE-2018-15473 - User enumeration vulnerability

2019-04-08 Thread Seth Arnold

Root, that script is suitable for timing attacks against ssh. This issue
is easier to use to enumerate users, but does require a different
approach. There was a tool posted to oss-security for this:
https://www.openwall.com/lists/oss-security/2018/08/16/1

Thanks

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

Title:
  CVE-2018-15473 - User enumeration vulnerability

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

Bug description:
  https://nvd.nist.gov/vuln/detail/CVE-2018-15473

  OpenSSH through 7.7 is prone to a user enumeration vulnerability due
  to not delaying bailout for an invalid authenticating user until after
  the packet containing the request has been fully parsed, related to
  auth2-gss.c, auth2-hostbased.c, and auth2-pubkey.c.

  Fixed in Debian: https://www.debian.org/security/2018/dsa-4280

  Currently pending triage? https://people.canonical.com/~ubuntu-
  security/cve/2018/CVE-2018-15473.html

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

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

[Touch-packages] [Bug 1823578] Re: scp doesn't work; required GLIBC versions not found; connection lost

2019-04-08 Thread Talib Pierson

I've just tested and had the same problem on Fedora 28, so it is highly
likely that it is my fault (user error) or syccuxas01.pcc.edu's fault
(server error).

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

Title:
  scp doesn't work; required GLIBC versions not found; connection lost

Status in openssh package in Ubuntu:
  New

Bug description:
  Command:
  scp -r '/home/talib/Desktop/Week 2 Lab' 
talib.pier...@syccuxas01.pcc.edu:/home/student/talib.pierson/
  Password:
  scp: /lib64/libc.so.6: version `GLIBC_2.25' not found (required by scp)
  scp: /lib64/libc.so.6: version `GLIBC_2.26' not found (required by scp)
  lost connection

  Notes:
  ldd (Ubuntu GLIBC 2.28-0ubuntu1) 2.28

  libc6 is already the newest version (2.28-0ubuntu1)

  I created symlink to libc.so.6 to see if that was the problem:
  sudo ln -s /lib/x86_64-linux-gnu/libc.so.6 /lib64/libc.so.6
  yet the problem persisted

  Does this have anything to do with
  [https://wiki.ubuntu.com/MultiarchSpec Multiarch]?

  
  List installed packages:
  glibc-doc-reference/cosmic,cosmic,now 2.27-1 all [installed]
  glibc-doc/cosmic,cosmic,now 2.28-0ubuntu1 all [installed]
  glibc-source/cosmic,cosmic,now 2.28-0ubuntu1 all [installed]
  libc6-amd64/cosmic,now 2.28-0ubuntu1 i386 [installed]
  libc6-dbg/cosmic,now 2.28-0ubuntu1 amd64 [installed]
  libc6-dev/cosmic,now 2.28-0ubuntu1 amd64 [installed]
  libc6-pic/cosmic,now 2.28-0ubuntu1 amd64 [installed]
  libc6/cosmic,now 2.28-0ubuntu1 amd64 [installed]
  libc6/cosmic,now 2.28-0ubuntu1 i386 [installed,automatic]
  libklibc/cosmic,now 2.0.4-9ubuntu2 amd64 [installed,automatic]

  Diagnostic information:
  ldd /usr/bin/scp
  linux-vdso.so.1 (0x7ffd04f57000)
  libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f92f9424000)
  /lib64/ld-linux-x86-64.so.2 (0x7f92f964a000)

  Diagnostic information:
  strings /lib64/libc.so.6 | grep GLIBC
  GLIBC_2.2.5
  GLIBC_2.2.6
  GLIBC_2.3
  GLIBC_2.3.2
  GLIBC_2.3.3
  GLIBC_2.3.4
  GLIBC_2.4
  GLIBC_2.5
  GLIBC_2.6
  GLIBC_2.7
  GLIBC_2.8
  GLIBC_2.9
  GLIBC_2.10
  GLIBC_2.11
  GLIBC_2.12
  GLIBC_2.13
  GLIBC_2.14
  GLIBC_2.15
  GLIBC_2.16
  GLIBC_2.17
  GLIBC_2.18
  GLIBC_2.22
  GLIBC_2.23
  GLIBC_2.24
  GLIBC_2.25
  GLIBC_2.26
  GLIBC_2.27
  GLIBC_2.28
  GLIBC_PRIVATE

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: openssh-client 1:7.7p1-4ubuntu0.3
  ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20
  Uname: Linux 4.18.0-17-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr  7 17:20:03 2019
  InstallationDate: Installed on 2019-02-11 (55 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  RelatedPackageVersions:
   ssh-askpass   N/A
   libpam-sshN/A
   keychain  N/A
   ssh-askpass-gnome N/A
  SSHClientVersion: OpenSSH_7.7p1 Ubuntu-4ubuntu0.3, OpenSSL 1.0.2n  7 Dec 2017
  SourcePackage: openssh
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1823817] [NEW] package libkmod2:amd64 25-1ubuntu1.2 failed to install/upgrade: package libkmod2:amd64 is already installed and configured

2019-04-08 Thread Ted Bruns

Public bug reported:

failed on update

ProblemType: Package
DistroRelease: Ubuntu 18.10
Package: libkmod2:amd64 25-1ubuntu1.2
ProcVersionSignature: Ubuntu 4.18.0-17.18-lowlatency 4.18.20
Uname: Linux 4.18.0-17-lowlatency x86_64
ApportVersion: 2.20.10-0ubuntu13.2
AptdaemonVersion: 1.1.1+bzr982-0ubuntu20
Architecture: amd64
Date: Sat Apr  6 08:44:58 2019
ErrorMessage: package libkmod2:amd64 is already installed and configured
InstallationDate: Installed on 2017-09-11 (573 days ago)
InstallationMedia: Ubuntu-Studio 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.10
PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu5
 apt  1.7.4
SourcePackage: kmod
Title: package libkmod2:amd64 25-1ubuntu1.2 failed to install/upgrade: package 
libkmod2:amd64 is already installed and configured
UpgradeStatus: Upgraded to cosmic on 2018-12-21 (108 days ago)

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


** Tags: already-installed amd64 apport-package cosmic

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

Title:
  package libkmod2:amd64 25-1ubuntu1.2 failed to install/upgrade:
  package libkmod2:amd64 is already installed and configured

Status in kmod package in Ubuntu:
  New

Bug description:
  failed on update

  ProblemType: Package
  DistroRelease: Ubuntu 18.10
  Package: libkmod2:amd64 25-1ubuntu1.2
  ProcVersionSignature: Ubuntu 4.18.0-17.18-lowlatency 4.18.20
  Uname: Linux 4.18.0-17-lowlatency x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  AptdaemonVersion: 1.1.1+bzr982-0ubuntu20
  Architecture: amd64
  Date: Sat Apr  6 08:44:58 2019
  ErrorMessage: package libkmod2:amd64 is already installed and configured
  InstallationDate: Installed on 2017-09-11 (573 days ago)
  InstallationMedia: Ubuntu-Studio 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.10
  PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu5
   apt  1.7.4
  SourcePackage: kmod
  Title: package libkmod2:amd64 25-1ubuntu1.2 failed to install/upgrade: 
package libkmod2:amd64 is already installed and configured
  UpgradeStatus: Upgraded to cosmic on 2018-12-21 (108 days ago)

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

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

[Touch-packages] [Bug 1804478] Re: netplan dhcp interface with no default route causes systemd-networkd-wait-online to hang

** Description changed:

+ [impact]
+ 
+ systemd-networkd, when configured to use ipv4 dhcp for an interface, if
+ also configured to ignore the dhcp server's route (or if the server
+ provides no route), systemd-networkd will hang waiting for the
+ interface's configuration to complete (until it times out).
+ 
+ This delays boot as well as any restart to systemd-networkd.
+ 
+ [test case]
+ 
+ configure an interface using systemd-networkd:
+ 
+ $ cat /etc/systemd/network/20-ens7.network 
+ [Match]
+ Name=ens7
+ 
+ [Network]
+ DHCP=ipv4
+ 
+ [DHCP]
+ UseRoutes=false
+ 
+ 
+ then reboot, and check:
+ 
+ $ systemctl status systemd-networkd-wait-online
+ ● systemd-networkd-wait-online.service - Wait for Network to be Configured
+Loaded: loaded (/lib/systemd/system/systemd-networkd-wait-online.service; 
enabled; vendor preset: enabled)
+Active: failed (Result: exit-code) since Mon 2019-04-08 23:59:26 UTC; 2min 
59s ago
+  Docs: man:systemd-networkd-wait-online.service(8)
+   Process: 593 ExecStart=/lib/systemd/systemd-networkd-wait-online 
(code=exited, status=1/FAILURE)
+  Main PID: 593 (code=exited, status=1/FAILURE)
+ 
+ Apr 08 23:57:27 lp1804478 systemd[1]: Starting Wait for Network to be 
Configured...
+ Apr 08 23:57:30 lp1804478 systemd-networkd-wait-online[593]: managing: ens3
+ Apr 08 23:57:30 lp1804478 systemd-networkd-wait-online[593]: ignoring: lo
+ Apr 08 23:59:26 lp1804478 systemd-networkd-wait-online[593]: Event loop 
failed: Connection timed out
+ Apr 08 23:59:26 lp1804478 systemd[1]: systemd-networkd-wait-online.service: 
Main process exited, code=exited, status=1/FAILURE
+ Apr 08 23:59:26 lp1804478 systemd[1]: systemd-networkd-wait-online.service: 
Failed with result 'exit-code'.
+ Apr 08 23:59:26 lp1804478 systemd[1]: Failed to start Wait for Network to be 
Configured.
+ 
+ [regression potential]
+ 
+ this alters how systemd-networkd works when it starts or restarts,
+ specifically how it handles dhcp4; regressions would be around setting
+ up interface(s) using dhcpv4, possibly failing to correctly configure
+ dhcpv4 interface(s) or even failing internal assertions and exiting.
+ 
+ [other info]
+ 
+ original description:
+ 
+ --
+ 
  root cause in systemd bug fixed in Commit
  223932c786ada7f758a7b7878a6ad2dae0d1e5fb:
  https://github.com/systemd/systemd/pull/8728
  
  Environment:
  Ubuntu 18.04 LTS amd64
  systemd package version 237-3ubuntu10.9
  
  How to trigger:
  1. add netplan interface with dhcpv4 client enabled:
  enp0s8:
  addresses: []
  dhcp4: true
  2. configure dhcp server to NOT give a default route, or any route for that 
matter
  3. reboot
  4. systemd-networkd-wait-online will block until dhcp renew is triggered
  root@sensor1:~# /lib/systemd/systemd-networkd-wait-online --timeout=3
  Event loop failed: Connection timed out
  root@sensor1:~# /lib/systemd/systemd-networkd-wait-online --timeout=3 
--ignore=enp0s8
  managing: enp0s3
  ignoring: lo
  ignoring: enp0s8
  
  How to fix:
  Backport upstream changes from systemd (see related systemd ticket).

** Changed in: systemd (Ubuntu Bionic)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

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

** Changed in: systemd (Ubuntu Bionic)
   Status: Confirmed => In Progress

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

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

Title:
  netplan dhcp interface with no default route causes systemd-networkd-
  wait-online to hang

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  In Progress

Bug description:
  [impact]

  systemd-networkd, when configured to use ipv4 dhcp for an interface,
  if also configured to ignore the dhcp server's route (or if the server
  provides no route), systemd-networkd will hang waiting for the
  interface's configuration to complete (until it times out).

  This delays boot as well as any restart to systemd-networkd.

  [test case]

  configure an interface using systemd-networkd:

  $ cat /etc/systemd/network/20-ens7.network 
  [Match]
  Name=ens7

  [Network]
  DHCP=ipv4

  [DHCP]
  UseRoutes=false

  
  then reboot, and check:

  $ systemctl status systemd-networkd-wait-online
  ● systemd-networkd-wait-online.service - Wait for Network to be Configured
 Loaded: loaded (/lib/systemd/system/systemd-networkd-wait-online.service; 
enabled; vendor preset: enabled)
 Active: failed (Result: exit-code) since Mon 2019-04-08 23:59:26 UTC; 2min 
59s ago
   Docs: man:systemd-networkd-wait-online.service(8)
Process: 593 ExecStart=/lib/systemd/systemd-networkd-wait-online 
(code=exited, status=1/FAILURE)
   Main PID: 593 (code=exited, status=1/FAILURE)

  Apr 08 23:57:27 lp1804478 systemd[1]:

[Touch-packages] [Bug 1821343] Re: slapd process failure is not detected by systemd

2019-04-08 Thread Bug Watch Updater

** Changed in: openldap (Debian)
   Status: Unknown => New

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

Title:
  slapd process failure is not detected by systemd

Status in openldap package in Ubuntu:
  Confirmed
Status in openldap source package in Xenial:
  Confirmed
Status in openldap source package in Bionic:
  Confirmed
Status in openldap source package in Cosmic:
  Confirmed
Status in openldap package in Debian:
  New

Bug description:
  [Impact]
  Systemd service reports slapd as active, even though it may have failed

  [Description]
  The slapd package for OpenLDAP is shipped with a SysV-style init script 
(/etc/init.d/slapd). Systemd automatically converts this to a systemd service 
by generating the unit file using the systemd-sysv-generator(8) utility. The 
generated unit file contains Type=forking and RemainAfterExit=yes directives.

  If the slapd daemon process exits due to some failure (e.g., it
  receives a SIGTERM or SIGKILL), the failure is not detected properly
  by systemd. The service is still reported as active even though the
  child (daemon) process has exited with a signal.

  We can easily fix this by including a proper systemd service file for
  slapd in the openldap package. Since the init.d script already does
  most of the necessary work (parsing configs, setting up PID files,
  etc.), we don't need anything complicated for the systemd unit file.
  Just making sure that RemainAfterExit is set to "no" makes the systemd
  service behave in the expected way.

  [Test Case]
  1) Deploy a disco container
  $ lxc launch images:ubuntu/disco disco

  2) Install slapd
  ubuntu@disco:~$ sudo apt update && sudo apt install slapd -y

  3) Verify that slapd is running with the auto-generated service
  ubuntu@disco:~$ systemctl status slapd
  ● slapd.service - LSB: OpenLDAP standalone server (Lightweight Directory 
Access Protocol)
 Loaded: loaded (/etc/init.d/slapd; generated)
 Active: active (running) since Fri 2019-03-22 11:51:22 UTC; 40min ago
   Docs: man:systemd-sysv-generator(8)
Process: 1103 ExecStart=/etc/init.d/slapd start (code=exited, 
status=0/SUCCESS)
  Tasks: 3 (limit: 4915)
 Memory: 712.6M
 CGroup: /system.slice/slapd.service
 └─1109 /usr/sbin/slapd -h ldap:/// ldapi:/// -g openldap -u 
openldap -F /etc/ldap/slapd.d

  4) SIGKILL the slapd process (PID is displayed in systemctl status output)
  ubuntu@disco:~$ sudo kill -9 1109

  5) Check if systemd service lists slapd as still active, even though it was 
terminated
  ubuntu@disco:~$ systemctl status slapd
  ● slapd.service - LSB: OpenLDAP standalone server (Lightweight Directory 
Access Protocol)
 Loaded: loaded (/etc/init.d/slapd; generated)
 Active: active (exited) since Fri 2019-03-22 11:51:22 UTC; 42min ago
   Docs: man:systemd-sysv-generator(8)
Process: 1103 ExecStart=/etc/init.d/slapd start (code=exited, 
status=0/SUCCESS)

  [Regression Potential]
  The regression potential for this fix should be very low, if we keep the new 
systemd unit file close to the one generated by systemd-sysv-generator(8). The 
only significant change would be the RemainAfterExit directive, and this should 
make the slapd service behave like a "normal" forking service. Nonetheless, 
we'll perform scripted test runs to make sure no regressions arise.

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

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

[Touch-packages] [Bug 1823422] Re: heimdal ftbfs in disco

2019-04-08 Thread Seth Arnold

Hmm, also ugly:

test-normalize.c: In function ‘main’:
test-normalize.c:159:49: warning: ‘__builtin___snprintf_chk’ output may be 
truncated before the last format character [-Wformat-truncation=]
  snprintf(longname, sizeof(longname), "%s/%s", srcdir, filename);
 ^
In file included from /usr/include/stdio.h:867,
 from test-normalize.c:37:
/usr/include/x86_64-linux-gnu/bits/stdio2.h:67:10: note: 
‘__builtin___snprintf_chk’ output 2 or more bytes (assuming 257) into a 
destination of size 256
   return __builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL - 1,
  ^~~~
__bos (__s), __fmt, __va_arg_pack ());
~

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

Title:
  heimdal ftbfs in disco

Status in Heimdal:
  New
Status in heimdal package in Ubuntu:
  New

Bug description:
  https://launchpadlibrarian.net/417925401/buildlog_ubuntu-disco-
  amd64.heimdal_7.5.0+dfsg-2.1_BUILDING.txt.gz

  =
 Heimdal 7.5.0: lib/hx509/test-suite.log
  =

  # TOTAL: 16
  # PASS:  15
  # SKIP:  0
  # XFAIL: 0
  # FAIL:  1
  # XPASS: 0
  # ERROR: 0

  .. contents:: :depth: 2

  FAIL: test_chain
  

  cert -> root
  cert -> root
  cert -> root
  sub-cert -> root
  sub-cert -> sub-ca -> root
  sub-cert -> sub-ca
  sub-cert -> sub-ca -> root
  sub-cert -> sub-ca -> root
  sub-cert -> sub-ca -> root
  max depth 2 (ok)
  max depth 1 (fail)
  ocsp non-ca responder
  ocsp ca responder
  ocsp no-ca responder, missing cert
  ocsp no-ca responder, missing cert, in pool
  ocsp no-ca responder, keyHash
  ocsp revoked cert
  ocsp print reply resp1-ocsp-no-cert
  ocsp print reply resp1-ca
  ocsp print reply resp1-keyhash
  ocsp print reply resp2
  ocsp verify exists
  ocsp verify not exists
  ocsp verify revoked
  crl non-revoked cert
  FAIL test_chain (exit status: 1)

  
  Testsuite summary for Heimdal 7.5.0
  
  # TOTAL: 16
  # PASS:  15
  # SKIP:  0
  # XFAIL: 0
  # FAIL:  1
  # XPASS: 0
  # ERROR: 0
  
  See lib/hx509/test-suite.log
  Please report to https://github.com/heimdal/heimdal/issues

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

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

[Touch-packages] [Bug 1786574] Re: remove i2c-i801 from blacklist

This bug was fixed in the package kmod - 25-1ubuntu3

---
kmod (25-1ubuntu3) disco; urgency=medium

  * Drop i2c_i801 from the blacklist again, things work fine with
current kernels. (LP: #1786574)

 -- Timo Aaltonen   Thu, 04 Apr 2019 11:30:14 +0300

** Changed in: kmod (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  remove i2c-i801 from blacklist

Status in HWE Next:
  In Progress
Status in OEM Priority Project:
  New
Status in kmod package in Ubuntu:
  Fix Released
Status in kmod source package in Xenial:
  In Progress
Status in kmod source package in Bionic:
  In Progress
Status in kmod source package in Cosmic:
  In Progress

Bug description:
  SRU justification
  

  [Impact]
  Many modern notebooks need i2c-i801 kernel module to function, but it is 
blacklisted by /etc/modprobe/blacklist.conf, which gives a very poor user 
experience.

  [Test case]
  1. Install Ubuntu
  2. Check touchpad works or not
  3. Install the fixed kmod package
  4. Confirm touchpad works

  [Regression Potential]
  i2c-i801 was blacklisted due to bug 16602. The user complains an HP Compaq 
nc6000 notebook cannot suspend without blacklisting i2c-i801. While this is a 
way to workaround the suspend issue, the proper fix should be in linux kernel. 
Since nc6000 was a machine sold in 2004, it is too difficult to find someone to 
verify if it will regress due to this SRU. The rationale to blacklist it is: 
https://bugs.launchpad.net/ubuntu/+source/hotplug/+bug/16602/comments/5, 
however it is no longer valid nowadays on modern computers.

  Besides, there look like to be a quirk in linux kernel that fixes it:
  https://github.com/torvalds/linux/blame/master/drivers/pci/quirks.c#L1434

  [Other Info]
  rationale of i2c_i801 driver blacklist: 
https://answers.launchpad.net/ubuntu/+source/kmod/+question/269329

  
---
  Original bug report:

  We have a Lenovo Thinkpad machine that requires i2c-i801 kernel module
  to work, but it is listed in /etc/modprobe/blacklist.conf in Ubuntu.
  To use the touchpad, users have to remove the i2c-i801 line manually.

  i2c-i801 in blacklist.conf is a very old workaround to fix HP compaq nc6000
  (Bug #16602), this module should be removed from blacklist.

  There is also another bug (Bug #1475945) that needs this module for
  Acer trackpad to work.

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

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

[Touch-packages] [Bug 1742941] Comment bridged from LTC Bugzilla

2019-04-08 Thread bugproxy

--- Comment From danie...@au1.ibm.com 2019-04-08 18:59 EDT---
Significant background talks are taking place with Mark Adler about the 
maintenance of zlib for arch specific performance.

Lets see what happens in the next 3 months.

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

Title:
  [18.10] zlib: improve  crc32 performance on P8

Status in The Ubuntu-power-systems project:
  Incomplete
Status in zlib package in Ubuntu:
  New

Bug description:
  Calculate the checksum of data that is 16 byte aligned and a multiple
  of  16 bytes.

  The first step is to reduce it to 1024 bits. We do this in 8 parallel
   chunks in order to mask the latency of the vpmsum instructions. If we
   have more than 32 kB of data to checksum we repeat this step multiple
   times, passing in the previous 1024 bits.

   The next step is to reduce the 1024 bits to 64 bits. This step adds
   32 bits of 0s to the end - this matches what a CRC does. We just
   calculate constants that land the data in this 32 bits.

   We then use fixed point Barrett reduction to compute a mod n over GF(2)
   for n = CRC using POWER8 instructions. We use x = 32.

   http://en.wikipedia.org/wiki/Barrett_reduction

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

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

[Touch-packages] [Bug 1816530] Re: DNS servers are not being set in the system correctly when you upgrade from 16.04 to 18.04

> nameserver 8.8.8.8

to confirm, you added this line yourself, right?

Assuming you did, can you please reboot, and make sure that 8.8.8.8 is
no longer in your /etc/resolv.conf file, and re-gather the info?  Also,
after rebooting, please get the output from:

$ SYSTEMD_LOG_LEVEL=debug systemd-resolve google.com


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

** Changed in: resolvconf (Ubuntu)
 Assignee: Dimitri John Ledkov (xnox) => Dan Streetman (ddstreet)

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

Title:
  DNS servers are not being set in the system correctly when you upgrade
  from 16.04 to 18.04

Status in resolvconf package in Ubuntu:
  Incomplete

Bug description:
  I upgraded my 16.04 to 18.04 before the official release. After the
  upgrade I noticed that I don't have internet access. The wired network
  and the wifi settings looked good, but the internet didn't work. After
  the login the system always switched itself into airplane mode. I
  tethered the network via USB and Bluetooth by my mobile but they also
  didn't work.

  I found a useful answer from @andrew-woodhead666:
  https://answers.launchpad.net/ubuntu/+question/665374

  it seems this bug is still not fixed for the upgraded dists in the main 
release and affects a few dozens of ubuntu users.
  
https://askubuntu.com/questions/1021884/no-internet-after-upgrade-from-16-04-to-18-04

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

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

[Touch-packages] [Bug 1804478] Re: netplan dhcp interface with no default route causes systemd-networkd-wait-online to hang

2019-04-08 Thread dann frazier

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

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

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

Title:
  netplan dhcp interface with no default route causes systemd-networkd-
  wait-online to hang

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Triaged
Status in systemd source package in Bionic:
  Confirmed

Bug description:
  root cause in systemd bug fixed in Commit
  223932c786ada7f758a7b7878a6ad2dae0d1e5fb:
  https://github.com/systemd/systemd/pull/8728

  Environment:
  Ubuntu 18.04 LTS amd64
  systemd package version 237-3ubuntu10.9

  How to trigger:
  1. add netplan interface with dhcpv4 client enabled:
  enp0s8:
  addresses: []
  dhcp4: true
  2. configure dhcp server to NOT give a default route, or any route for that 
matter
  3. reboot
  4. systemd-networkd-wait-online will block until dhcp renew is triggered
  root@sensor1:~# /lib/systemd/systemd-networkd-wait-online --timeout=3
  Event loop failed: Connection timed out
  root@sensor1:~# /lib/systemd/systemd-networkd-wait-online --timeout=3 
--ignore=enp0s8
  managing: enp0s3
  ignoring: lo
  ignoring: enp0s8

  How to fix:
  Backport upstream changes from systemd (see related systemd ticket).

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

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

[Touch-packages] [Bug 1615381] Re: apt-get autoremove may remove current kernel

2019-04-08 Thread Balint Reczey

@jarnos, this is a separate issue fixed later, calculating upgradable packages 
leaves the upgradable packages in the cache, and u-u counts them as the reverse 
dependencies of the first kernel to be removed.
This keeps the first kernel on the system, but when there are no upgradable 
packages in a later run this kernel can be removed, too.

See:
https://github.com/mvo5/unattended-upgrades/commit/93d43fbcd53c5df5ce69a16b26a981bf06ce3085
https://github.com/mvo5/unattended-upgrades/commit/654898b05c933047ca8c97df655743aab0898db1
https://github.com/mvo5/unattended-upgrades/commit/1a39eb257ad786902de11add212879241919be44

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

Title:
  apt-get autoremove may remove current kernel

Status in apt package in Ubuntu:
  Won't Fix
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in apt source package in Trusty:
  Won't Fix
Status in unattended-upgrades source package in Trusty:
  New
Status in apt source package in Xenial:
  Won't Fix
Status in unattended-upgrades source package in Xenial:
  Fix Committed
Status in apt source package in Artful:
  Won't Fix
Status in unattended-upgrades source package in Artful:
  Won't Fix

Bug description:
  This may happen, if you boot one of the older kernels, that is not
  protected by /etc/apt/apt.conf.d/01autoremove-kernels

  Workaround: run
  /etc/kernel/postinst.d/apt-auto-removal
  during each boot (e.g. by using cron).
  Note: The workaround breaks autoremoving feature of new unneeded kernels in  
unattended-upgrades i.e. the setting 
'Unattended-Upgrade::Remove-New-Unused-Dependencies "true"' (which is default 
in 16.04 unless 'Unattended-Upgrade::Remove-Unused-Dependencies "true"' is set 
in '/etc/apt/apt.conf.d/50unattended-upgrades'.

  
  In shell:

  $ uname -r
  4.4.0-22-generic
  $ apt-get -s autoremove
  NOTE: This is only a simulation!
    apt-get needs root privileges for real execution.
    Keep also in mind that locking is deactivated,
    so don't depend on the relevance to the real current situation!
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  The following packages will be REMOVED:
    linux-headers-4.4.0-21 linux-headers-4.4.0-21-generic linux-headers-4.4.0-22
    linux-headers-4.4.0-22-generic linux-headers-4.4.0-31-generic
    linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic
    linux-image-4.4.0-31-generic linux-image-extra-4.4.0-21-generic
    linux-image-extra-4.4.0-22-generic linux-image-extra-4.4.0-31-generic
  0 upgraded, 0 newly installed, 11 to remove and 13 not upgraded.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.12~ubuntu16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Aug 21 16:11:27 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-28 (114 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.kernel.postinst.d.apt-auto-removal: [modified]
  mtime.conffile..etc.kernel.postinst.d.apt-auto-removal: 
2016-07-30T12:15:32.706300

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

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

[Touch-packages] [Bug 1816530] Re: DNS servers are not being set in the system correctly when you upgrade from 16.04 to 18.04

2019-04-08 Thread Zoltán Süle

$ ls -l /etc/resolv.conf

lrwxrwxrwx 1 root root 29 Aug  4  2016 /etc/resolv.conf ->
../run/resolvconf/resolv.conf


$ cat /etc/resolv.conf

# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual nameservers.

nameserver 8.8.8.8
nameserver 127.0.0.53
search home
options edns0


$ systemd-resolve --status

Global
 DNS Servers: 8.8.8.8
  DNSSEC NTA: 10.in-addr.arpa
  16.172.in-addr.arpa
  168.192.in-addr.arpa
  17.172.in-addr.arpa
  18.172.in-addr.arpa
  19.172.in-addr.arpa
  20.172.in-addr.arpa
  21.172.in-addr.arpa
  22.172.in-addr.arpa
  23.172.in-addr.arpa
  24.172.in-addr.arpa
  25.172.in-addr.arpa
  26.172.in-addr.arpa
  27.172.in-addr.arpa
  28.172.in-addr.arpa
  29.172.in-addr.arpa
  30.172.in-addr.arpa
  31.172.in-addr.arpa
  corp
  d.f.ip6.arpa
  home
  internal
  intranet
  lan
  local
  private
  test

Link 5 (virbr0-nic)
  Current Scopes: none
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: no
DNSSEC supported: no

Link 4 (virbr0)
  Current Scopes: none
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: no
DNSSEC supported: no
Link 3 (wlp2s0)
  Current Scopes: none
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: no
DNSSEC supported: no

Link 2 (eno1)
  Current Scopes: DNS
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: no
DNSSEC supported: no
 DNS Servers: 195.34.133.21
  212.186.211.21
  DNS Domain: home


$ grep . /run/resolvconf/interface/*

nameserver 127.0.0.53
options edns0
search home

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

Title:
  DNS servers are not being set in the system correctly when you upgrade
  from 16.04 to 18.04

Status in resolvconf package in Ubuntu:
  New

Bug description:
  I upgraded my 16.04 to 18.04 before the official release. After the
  upgrade I noticed that I don't have internet access. The wired network
  and the wifi settings looked good, but the internet didn't work. After
  the login the system always switched itself into airplane mode. I
  tethered the network via USB and Bluetooth by my mobile but they also
  didn't work.

  I found a useful answer from @andrew-woodhead666:
  https://answers.launchpad.net/ubuntu/+question/665374

  it seems this bug is still not fixed for the upgraded dists in the main 
release and affects a few dozens of ubuntu users.
  
https://askubuntu.com/questions/1021884/no-internet-after-upgrade-from-16-04-to-18-04

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

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

[Touch-packages] [Bug 1822370] Re: 19.04 beta openssh-client broken pipe

2019-04-08 Thread Bug Watch Updater

** Changed in: openssh (Debian)
   Status: New => Fix Released

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

Title:
  19.04 beta openssh-client broken pipe

Status in openssh package in Ubuntu:
  Triaged
Status in openssh source package in Disco:
  Triaged
Status in openssh package in Debian:
  Fix Released

Bug description:
  New versions of openssh (as in Ubuntu 19.04) are reported to trigger a
  connection issue:

 packet_write_wait: Connection to x.x.x.x port 22: Broken pipe

  In most of the cases this seems to affect VMWare based environments as
  there is a bug in their implementation in regard to the traffic
  shaping protocols.

  Until resolved by VMWare the workarounds for now are:

  Configure your client to use the old defaults permanently in
  =>  /etc/ssh/ssh_config 
  Host *
  IPQoS lowdelay throughput 
  # You might want to limit to your VMware based systems

  Or per command via:
   $ ssh IPQoS="latency throughput" user@host

  Two values as one is for interactive and one for non-interactive use
  cases.

   original report 

  Upgrade to Xubuntu 19.04 beta from 18.10

  openssh-client

  when trying to ssh into another system, following error:

  packet_write_wait: Connection to x.x.x.x port 22: Broken pipe

  Problem is consistent on trying to connect to various systems.

  Can confirm was able to ssh prior to upgrade and can ssh into these
  systems from other systems.

  Can use putty on this system to ssh into these boxes as well.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: openssh-client 1:7.9p1-9
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Mar 29 13:36:38 2019
  InstallationDate: Installed on 2018-11-14 (135 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions:
   ssh-askpass   N/A
   libpam-sshN/A
   keychain  N/A
   ssh-askpass-gnome N/A
  SSHClientVersion: OpenSSH_7.9p1 Ubuntu-9, OpenSSL 1.1.1b  26 Feb 2019
  SourcePackage: openssh
  UpgradeStatus: Upgraded to disco on 2019-03-29 (0 days ago)

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

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

[Touch-packages] [Bug 1823650] Re: v4l-utils ftbfs in cosmic

2019-04-08 Thread Gregor Jasny

I verified that https://git.linuxtv.org/v4l-
utils.git/commit/?h=stable-1.14=b6c3e824967e25857a41e1c0e23d010317566467
and https://git.linuxtv.org/v4l-
utils.git/commit/?h=stable-1.14=65b6f255a02de403621e478aac701e3ee56806a4
fix the build issue. However there are some more fixes (double free and
uninitialised memory) that I'd like to ship as well. The double free
patch backport seems to be incomplete and I asked upstream for
clarification: https://lore.kernel.org/linux-media/cc7fce0b-8db0-ce2c-
e7f0-c6d39f769...@googlemail.com/T/#u

I'd like to way one or two days for upstream, otherwise I'll build a
package without the double-free fix and handle it later.

Thanks,
Gregor

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

Title:
  v4l-utils ftbfs in cosmic

Status in v4l-utils package in Ubuntu:
  New

Bug description:
  https://launchpadlibrarian.net/418304769/buildlog_ubuntu-cosmic-amd64
  .v4l-utils_1.14.2-1_BUILDING.txt.gz

  g++  -I. -I../..  -I../../utils/common -I../../lib/include -Wall 
-Wpointer-arith -D_GNU_SOURCE -I../../include -Wdate-time -D_FORTIFY_SOURCE=2  
-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o v4l2_compliance-v4l2-compliance.o `test -f 
'v4l2-compliance.cpp' || echo './'`v4l2-compliance.cpp
  In file included from v4l2-compliance.h:42,
   from v4l2-compliance.cpp:38:
  ../../utils/common/cv4l-helpers.h: In member function ‘void 
cv4l_buffer::init(const cv4l_buffer&)’:
  ../../utils/common/cv4l-helpers.h:843:29: warning: ‘void* memcpy(void*, const 
void*, size_t)’ writing to an object of type ‘class cv4l_buffer’ with no 
trivial copy-assignment; use copy-assignment or copy-initialization instead 
[-Wclass-memaccess]
 memcpy(this, , sizeof(b));
   ^
  ../../utils/common/cv4l-helpers.h:817:7: note: ‘class cv4l_buffer’ declared 
here
   class cv4l_buffer : public v4l_buffer {
 ^~~
  g++  -I. -I../..  -I../../utils/common -I../../lib/include -Wall 
-Wpointer-arith -D_GNU_SOURCE -I../../include -Wdate-time -D_FORTIFY_SOURCE=2  
-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o v4l2_compliance-v4l2-test-debug.o `test -f 
'v4l2-test-debug.cpp' || echo './'`v4l2-test-debug.cpp
  In file included from v4l2-compliance.h:42,
   from v4l2-test-debug.cpp:35:
  ../../utils/common/cv4l-helpers.h: In member function ‘void 
cv4l_buffer::init(const cv4l_buffer&)’:
  ../../utils/common/cv4l-helpers.h:843:29: warning: ‘void* memcpy(void*, const 
void*, size_t)’ writing to an object of type ‘class cv4l_buffer’ with no 
trivial copy-assignment; use copy-assignment or copy-initialization instead 
[-Wclass-memaccess]
 memcpy(this, , sizeof(b));
   ^
  ../../utils/common/cv4l-helpers.h:817:7: note: ‘class cv4l_buffer’ declared 
here
   class cv4l_buffer : public v4l_buffer {
 ^~~
  g++  -I. -I../..  -I../../utils/common -I../../lib/include -Wall 
-Wpointer-arith -D_GNU_SOURCE -I../../include -Wdate-time -D_FORTIFY_SOURCE=2  
-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o v4l2_compliance-v4l2-test-input-output.o `test -f 
'v4l2-test-input-output.cpp' || echo './'`v4l2-test-input-output.cpp
  In file included from v4l2-compliance.h:42,
   from v4l2-test-input-output.cpp:32:
  ../../utils/common/cv4l-helpers.h: In member function ‘void 
cv4l_buffer::init(const cv4l_buffer&)’:
  ../../utils/common/cv4l-helpers.h:843:29: warning: ‘void* memcpy(void*, const 
void*, size_t)’ writing to an object of type ‘class cv4l_buffer’ with no 
trivial copy-assignment; use copy-assignment or copy-initialization instead 
[-Wclass-memaccess]
 memcpy(this, , sizeof(b));
   ^
  ../../utils/common/cv4l-helpers.h:817:7: note: ‘class cv4l_buffer’ declared 
here
   class cv4l_buffer : public v4l_buffer {
 ^~~
  g++  -I. -I../..  -I../../utils/common -I../../lib/include -Wall 
-Wpointer-arith -D_GNU_SOURCE -I../../include -Wdate-time -D_FORTIFY_SOURCE=2  
-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o v4l2_compliance-v4l2-test-controls.o `test -f 
'v4l2-test-controls.cpp' || echo './'`v4l2-test-controls.cpp
  In file included from v4l2-compliance.h:42,
   from v4l2-test-controls.cpp:33:
  ../../utils/common/cv4l-helpers.h: In member function ‘void 
cv4l_buffer::init(const cv4l_buffer&)’:
  ../../utils/common/cv4l-helpers.h:843:29: warning: ‘void* memcpy(void*, const 
void*, size_t)’ writing to an object of type ‘class cv4l_buffer’ with no 
trivial copy-assignment; use copy-assignment or copy-initialization instead 
[-Wclass-memaccess]
 memcpy(this, , sizeof(b));
   ^

[Touch-packages] [Bug 1615381] Re: apt-get autoremove may remove current kernel

2019-04-08 Thread Jarno Suni

I do not understand why u-u keeps linux-modules-4.15.0-36-generic. How
do those packages depend on that?

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

Title:
  apt-get autoremove may remove current kernel

Status in apt package in Ubuntu:
  Won't Fix
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in apt source package in Trusty:
  Won't Fix
Status in unattended-upgrades source package in Trusty:
  New
Status in apt source package in Xenial:
  Won't Fix
Status in unattended-upgrades source package in Xenial:
  Fix Committed
Status in apt source package in Artful:
  Won't Fix
Status in unattended-upgrades source package in Artful:
  Won't Fix

Bug description:
  This may happen, if you boot one of the older kernels, that is not
  protected by /etc/apt/apt.conf.d/01autoremove-kernels

  Workaround: run
  /etc/kernel/postinst.d/apt-auto-removal
  during each boot (e.g. by using cron).
  Note: The workaround breaks autoremoving feature of new unneeded kernels in  
unattended-upgrades i.e. the setting 
'Unattended-Upgrade::Remove-New-Unused-Dependencies "true"' (which is default 
in 16.04 unless 'Unattended-Upgrade::Remove-Unused-Dependencies "true"' is set 
in '/etc/apt/apt.conf.d/50unattended-upgrades'.

  
  In shell:

  $ uname -r
  4.4.0-22-generic
  $ apt-get -s autoremove
  NOTE: This is only a simulation!
    apt-get needs root privileges for real execution.
    Keep also in mind that locking is deactivated,
    so don't depend on the relevance to the real current situation!
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  The following packages will be REMOVED:
    linux-headers-4.4.0-21 linux-headers-4.4.0-21-generic linux-headers-4.4.0-22
    linux-headers-4.4.0-22-generic linux-headers-4.4.0-31-generic
    linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic
    linux-image-4.4.0-31-generic linux-image-extra-4.4.0-21-generic
    linux-image-extra-4.4.0-22-generic linux-image-extra-4.4.0-31-generic
  0 upgraded, 0 newly installed, 11 to remove and 13 not upgraded.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.12~ubuntu16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Aug 21 16:11:27 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-28 (114 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.kernel.postinst.d.apt-auto-removal: [modified]
  mtime.conffile..etc.kernel.postinst.d.apt-auto-removal: 
2016-07-30T12:15:32.706300

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

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

[Touch-packages] [Bug 1823422] Re: heimdal ftbfs in disco

2019-04-08 Thread Bug Watch Updater

** Changed in: heimdal
   Status: Unknown => New

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

Title:
  heimdal ftbfs in disco

Status in Heimdal:
  New
Status in heimdal package in Ubuntu:
  New

Bug description:
  https://launchpadlibrarian.net/417925401/buildlog_ubuntu-disco-
  amd64.heimdal_7.5.0+dfsg-2.1_BUILDING.txt.gz

  =
 Heimdal 7.5.0: lib/hx509/test-suite.log
  =

  # TOTAL: 16
  # PASS:  15
  # SKIP:  0
  # XFAIL: 0
  # FAIL:  1
  # XPASS: 0
  # ERROR: 0

  .. contents:: :depth: 2

  FAIL: test_chain
  

  cert -> root
  cert -> root
  cert -> root
  sub-cert -> root
  sub-cert -> sub-ca -> root
  sub-cert -> sub-ca
  sub-cert -> sub-ca -> root
  sub-cert -> sub-ca -> root
  sub-cert -> sub-ca -> root
  max depth 2 (ok)
  max depth 1 (fail)
  ocsp non-ca responder
  ocsp ca responder
  ocsp no-ca responder, missing cert
  ocsp no-ca responder, missing cert, in pool
  ocsp no-ca responder, keyHash
  ocsp revoked cert
  ocsp print reply resp1-ocsp-no-cert
  ocsp print reply resp1-ca
  ocsp print reply resp1-keyhash
  ocsp print reply resp2
  ocsp verify exists
  ocsp verify not exists
  ocsp verify revoked
  crl non-revoked cert
  FAIL test_chain (exit status: 1)

  
  Testsuite summary for Heimdal 7.5.0
  
  # TOTAL: 16
  # PASS:  15
  # SKIP:  0
  # XFAIL: 0
  # FAIL:  1
  # XPASS: 0
  # ERROR: 0
  
  See lib/hx509/test-suite.log
  Please report to https://github.com/heimdal/heimdal/issues

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

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

[Touch-packages] [Bug 1659534] Reminder of SRU verification policy change

Thank you for taking the time to verify this stable release fix.  We
have noticed that you have used the verification-done tag for marking
the bug as verified and would like to point out that due to a recent
change in SRU bug verification policy fixes now have to be marked with
per-release tags (i.e. verification-done-$RELEASE).  Please remove the
verification-done tag and add one for the release you have tested the
package in.  Thank you!

https://wiki.ubuntu.com/StableReleaseUpdates#Verification

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

Title:
  userdel doesn't supports extrausers

Status in Snappy:
  In Progress
Status in shadow package in Ubuntu:
  Fix Released
Status in shadow source package in Xenial:
  Fix Committed
Status in shadow source package in Bionic:
  Fix Committed

Bug description:
  TEST CASE:
  - run userdel --extrausers foo on a ubuntu core system

  REGRESSION POTENTIAL:
  - low, this option will only take effect when "userdel --extrauser" is used.

  On an Ubuntu Core system is impossible to delete an user from the
  extrausers db:

  root@localhost:/# userdel --extrausers alice
  userdel: unrecognized option '--extrausers'

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

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

[Touch-packages] [Bug 1823125] Re: tomcat9 fails to install in 18.04

2019-04-08 Thread Tiago Stürmer Daitx

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

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

Title:
  tomcat9 fails to install in 18.04

Status in systemd package in Ubuntu:
  Fix Released
Status in tomcat9 package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Won't Fix
Status in tomcat9 source package in Bionic:
  Fix Committed
Status in systemd source package in Cosmic:
  Fix Released
Status in tomcat9 source package in Cosmic:
  Fix Released
Status in systemd source package in Disco:
  Fix Released
Status in tomcat9 source package in Disco:
  Fix Released

Bug description:
  # apt install tomcat9
  ...
  Setting up tomcat9 (9.0.16-3~18.04) ...
  [/usr/lib/sysusers.d/tomcat9.conf:7] Trailing garbage.

  Creating config file /etc/tomcat9/tomcat-users.xml with new version
  chown: invalid group: ‘root:tomcat’
  dpkg: error processing package tomcat9 (--configure):
   installed tomcat9 package post-installation script subprocess returned error 
exit status 1
  Processing triggers for libc-bin (2.27-3ubuntu1) ...
  Processing triggers for ureadahead (0.100.0-20) ...
  Processing triggers for systemd (237-3ubuntu10.15) ...
  Processing triggers for ca-certificates (20180409) ...
  Updating certificates in /etc/ssl/certs...
  0 added, 0 removed; done.
  Running hooks in /etc/ca-certificates/update.d...

  done.
  done.
  Processing triggers for rsyslog (8.32.0-1ubuntu4) ...
  Errors were encountered while processing:
   tomcat9
  E: Sub-process /usr/bin/dpkg returned an error code (1)

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

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

[Touch-packages] [Bug 1823422] Re: heimdal ftbfs in disco

2019-04-08 Thread Andreas Hasenack

** Bug watch added: github.com/heimdal/heimdal/issues #533
   https://github.com/heimdal/heimdal/issues/533

** Also affects: heimdal via
   https://github.com/heimdal/heimdal/issues/533
   Importance: Unknown
   Status: Unknown

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

Title:
  heimdal ftbfs in disco

Status in Heimdal:
  Unknown
Status in heimdal package in Ubuntu:
  New

Bug description:
  https://launchpadlibrarian.net/417925401/buildlog_ubuntu-disco-
  amd64.heimdal_7.5.0+dfsg-2.1_BUILDING.txt.gz

  =
 Heimdal 7.5.0: lib/hx509/test-suite.log
  =

  # TOTAL: 16
  # PASS:  15
  # SKIP:  0
  # XFAIL: 0
  # FAIL:  1
  # XPASS: 0
  # ERROR: 0

  .. contents:: :depth: 2

  FAIL: test_chain
  

  cert -> root
  cert -> root
  cert -> root
  sub-cert -> root
  sub-cert -> sub-ca -> root
  sub-cert -> sub-ca
  sub-cert -> sub-ca -> root
  sub-cert -> sub-ca -> root
  sub-cert -> sub-ca -> root
  max depth 2 (ok)
  max depth 1 (fail)
  ocsp non-ca responder
  ocsp ca responder
  ocsp no-ca responder, missing cert
  ocsp no-ca responder, missing cert, in pool
  ocsp no-ca responder, keyHash
  ocsp revoked cert
  ocsp print reply resp1-ocsp-no-cert
  ocsp print reply resp1-ca
  ocsp print reply resp1-keyhash
  ocsp print reply resp2
  ocsp verify exists
  ocsp verify not exists
  ocsp verify revoked
  crl non-revoked cert
  FAIL test_chain (exit status: 1)

  
  Testsuite summary for Heimdal 7.5.0
  
  # TOTAL: 16
  # PASS:  15
  # SKIP:  0
  # XFAIL: 0
  # FAIL:  1
  # XPASS: 0
  # ERROR: 0
  
  See lib/hx509/test-suite.log
  Please report to https://github.com/heimdal/heimdal/issues

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

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

[Touch-packages] [Bug 1821343] Re: slapd process failure is not detected by systemd

2019-04-08 Thread Eric Desrochers

[sts-sponsor note]

I am concerned about just adding the service unit, and not making your package 
work
with systemd, especially for maintainer scripts (may break package upgrade... 
would be good to test and add this to the [test case].

May I suggest you look at debian/control and debian/rules to evaluate if :
* Build-Depends of "dh-systemd" (debian/control) for the maintainer scripts to 
contain appropriate code 
* dh --with=systemd (debian/rules) 

are needed ?

https://people.debian.org/~stapelberg/debconf13-making-your-package-
work-with-systemd.pdf

Regards,
Eric

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

Title:
  slapd process failure is not detected by systemd

Status in openldap package in Ubuntu:
  Confirmed
Status in openldap source package in Xenial:
  Confirmed
Status in openldap source package in Bionic:
  Confirmed
Status in openldap source package in Cosmic:
  Confirmed
Status in openldap package in Debian:
  Unknown

Bug description:
  [Impact]
  Systemd service reports slapd as active, even though it may have failed

  [Description]
  The slapd package for OpenLDAP is shipped with a SysV-style init script 
(/etc/init.d/slapd). Systemd automatically converts this to a systemd service 
by generating the unit file using the systemd-sysv-generator(8) utility. The 
generated unit file contains Type=forking and RemainAfterExit=yes directives.

  If the slapd daemon process exits due to some failure (e.g., it
  receives a SIGTERM or SIGKILL), the failure is not detected properly
  by systemd. The service is still reported as active even though the
  child (daemon) process has exited with a signal.

  We can easily fix this by including a proper systemd service file for
  slapd in the openldap package. Since the init.d script already does
  most of the necessary work (parsing configs, setting up PID files,
  etc.), we don't need anything complicated for the systemd unit file.
  Just making sure that RemainAfterExit is set to "no" makes the systemd
  service behave in the expected way.

  [Test Case]
  1) Deploy a disco container
  $ lxc launch images:ubuntu/disco disco

  2) Install slapd
  ubuntu@disco:~$ sudo apt update && sudo apt install slapd -y

  3) Verify that slapd is running with the auto-generated service
  ubuntu@disco:~$ systemctl status slapd
  ● slapd.service - LSB: OpenLDAP standalone server (Lightweight Directory 
Access Protocol)
 Loaded: loaded (/etc/init.d/slapd; generated)
 Active: active (running) since Fri 2019-03-22 11:51:22 UTC; 40min ago
   Docs: man:systemd-sysv-generator(8)
Process: 1103 ExecStart=/etc/init.d/slapd start (code=exited, 
status=0/SUCCESS)
  Tasks: 3 (limit: 4915)
 Memory: 712.6M
 CGroup: /system.slice/slapd.service
 └─1109 /usr/sbin/slapd -h ldap:/// ldapi:/// -g openldap -u 
openldap -F /etc/ldap/slapd.d

  4) SIGKILL the slapd process (PID is displayed in systemctl status output)
  ubuntu@disco:~$ sudo kill -9 1109

  5) Check if systemd service lists slapd as still active, even though it was 
terminated
  ubuntu@disco:~$ systemctl status slapd
  ● slapd.service - LSB: OpenLDAP standalone server (Lightweight Directory 
Access Protocol)
 Loaded: loaded (/etc/init.d/slapd; generated)
 Active: active (exited) since Fri 2019-03-22 11:51:22 UTC; 42min ago
   Docs: man:systemd-sysv-generator(8)
Process: 1103 ExecStart=/etc/init.d/slapd start (code=exited, 
status=0/SUCCESS)

  [Regression Potential]
  The regression potential for this fix should be very low, if we keep the new 
systemd unit file close to the one generated by systemd-sysv-generator(8). The 
only significant change would be the RemainAfterExit directive, and this should 
make the slapd service behave like a "normal" forking service. Nonetheless, 
we'll perform scripted test runs to make sure no regressions arise.

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

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

[Touch-packages] [Bug 1821343] Re: slapd process failure is not detected by systemd

2019-04-08 Thread Eric Desrochers

[sts-sponsor note]

I am concerned about just adding the service unit, and not making your package 
work
with systemd, especially for maintainer scripts (It may possibly break package 
upgrade, ..) 
IMHO it would be good to test and include an upgrade to the actual [Test Case] 
field.

May I suggest you look at evaluating if :
* Build-Depends of "dh-systemd" (debian/control) for the maintainer scripts to 
contain appropriate code
* dh --with=systemd (debian/rules)
* ...

are needed ?

https://people.debian.org/~stapelberg/debconf13-making-your-package-
work-with-systemd.pdf

Regards,
Eric

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

Title:
  slapd process failure is not detected by systemd

Status in openldap package in Ubuntu:
  Confirmed
Status in openldap source package in Xenial:
  Confirmed
Status in openldap source package in Bionic:
  Confirmed
Status in openldap source package in Cosmic:
  Confirmed
Status in openldap package in Debian:
  Unknown

Bug description:
  [Impact]
  Systemd service reports slapd as active, even though it may have failed

  [Description]
  The slapd package for OpenLDAP is shipped with a SysV-style init script 
(/etc/init.d/slapd). Systemd automatically converts this to a systemd service 
by generating the unit file using the systemd-sysv-generator(8) utility. The 
generated unit file contains Type=forking and RemainAfterExit=yes directives.

  If the slapd daemon process exits due to some failure (e.g., it
  receives a SIGTERM or SIGKILL), the failure is not detected properly
  by systemd. The service is still reported as active even though the
  child (daemon) process has exited with a signal.

  We can easily fix this by including a proper systemd service file for
  slapd in the openldap package. Since the init.d script already does
  most of the necessary work (parsing configs, setting up PID files,
  etc.), we don't need anything complicated for the systemd unit file.
  Just making sure that RemainAfterExit is set to "no" makes the systemd
  service behave in the expected way.

  [Test Case]
  1) Deploy a disco container
  $ lxc launch images:ubuntu/disco disco

  2) Install slapd
  ubuntu@disco:~$ sudo apt update && sudo apt install slapd -y

  3) Verify that slapd is running with the auto-generated service
  ubuntu@disco:~$ systemctl status slapd
  ● slapd.service - LSB: OpenLDAP standalone server (Lightweight Directory 
Access Protocol)
 Loaded: loaded (/etc/init.d/slapd; generated)
 Active: active (running) since Fri 2019-03-22 11:51:22 UTC; 40min ago
   Docs: man:systemd-sysv-generator(8)
Process: 1103 ExecStart=/etc/init.d/slapd start (code=exited, 
status=0/SUCCESS)
  Tasks: 3 (limit: 4915)
 Memory: 712.6M
 CGroup: /system.slice/slapd.service
 └─1109 /usr/sbin/slapd -h ldap:/// ldapi:/// -g openldap -u 
openldap -F /etc/ldap/slapd.d

  4) SIGKILL the slapd process (PID is displayed in systemctl status output)
  ubuntu@disco:~$ sudo kill -9 1109

  5) Check if systemd service lists slapd as still active, even though it was 
terminated
  ubuntu@disco:~$ systemctl status slapd
  ● slapd.service - LSB: OpenLDAP standalone server (Lightweight Directory 
Access Protocol)
 Loaded: loaded (/etc/init.d/slapd; generated)
 Active: active (exited) since Fri 2019-03-22 11:51:22 UTC; 42min ago
   Docs: man:systemd-sysv-generator(8)
Process: 1103 ExecStart=/etc/init.d/slapd start (code=exited, 
status=0/SUCCESS)

  [Regression Potential]
  The regression potential for this fix should be very low, if we keep the new 
systemd unit file close to the one generated by systemd-sysv-generator(8). The 
only significant change would be the RemainAfterExit directive, and this should 
make the slapd service behave like a "normal" forking service. Nonetheless, 
we'll perform scripted test runs to make sure no regressions arise.

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

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

[Touch-packages] [Bug 1815309] Re: package avahi-daemon 0.6.32~rc+dfsg-1ubuntu2.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

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

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

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

Title:
  package avahi-daemon 0.6.32~rc+dfsg-1ubuntu2.3 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

Status in avahi package in Ubuntu:
  Confirmed

Bug description:
  Modified .conf file to avoid forgotten problem with avahi daemon.
  Sorry, can't remember the problem tha caused me to modify the conf
  file. Info from the internet suggested.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2.3
  Uname: Linux 4.18.011 x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  AptOrdering:
   avahi-daemon: Configure
   avahi-utils: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sun Feb 10 03:15:04 2019
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.5
   apt  1.2.29ubuntu0.1
  SourcePackage: avahi
  Title: package avahi-daemon 0.6.32~rc+dfsg-1ubuntu2.3 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.avahi-daemon:
   # 1 = Try to detect unicast dns servers that serve .local and disable avahi 
in
   # that case, 0 = Don't try to detect .local unicast dns servers, can cause
   # troubles on misconfigured networks
   AVAHI_DAEMON_DETECT_LOCAL=0
  mtime.conffile..etc.avahi.avahi-daemon.conf: 2019-01-30T19:12:17.651743
  mtime.conffile..etc.default.avahi-daemon: 2019-01-30T19:10:28.949973

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

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

[Touch-packages] [Bug 1815309] Re: package avahi-daemon 0.6.32~rc+dfsg-1ubuntu2.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2019-04-08 Thread malangaman

Don't remember Changing anything

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

Title:
  package avahi-daemon 0.6.32~rc+dfsg-1ubuntu2.3 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

Status in avahi package in Ubuntu:
  Confirmed

Bug description:
  Modified .conf file to avoid forgotten problem with avahi daemon.
  Sorry, can't remember the problem tha caused me to modify the conf
  file. Info from the internet suggested.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2.3
  Uname: Linux 4.18.011 x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  AptOrdering:
   avahi-daemon: Configure
   avahi-utils: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sun Feb 10 03:15:04 2019
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.5
   apt  1.2.29ubuntu0.1
  SourcePackage: avahi
  Title: package avahi-daemon 0.6.32~rc+dfsg-1ubuntu2.3 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.avahi-daemon:
   # 1 = Try to detect unicast dns servers that serve .local and disable avahi 
in
   # that case, 0 = Don't try to detect .local unicast dns servers, can cause
   # troubles on misconfigured networks
   AVAHI_DAEMON_DETECT_LOCAL=0
  mtime.conffile..etc.avahi.avahi-daemon.conf: 2019-01-30T19:12:17.651743
  mtime.conffile..etc.default.avahi-daemon: 2019-01-30T19:10:28.949973

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

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

[Touch-packages] [Bug 1823674] Re: Animation of dash-icon no longer present after locking the screen

** Package changed: ubuntu-meta (Ubuntu) => gnome-desktop (Ubuntu)

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

Title:
  Animation of dash-icon no longer present after locking the screen

Status in gnome-desktop package in Ubuntu:
  New

Bug description:
  As described above. I started to copy some files on some USB-Sticks.
  The dash-icon has been animated. I had to leave my laptop for a second
  so I locked the sreen. After unlocking the animation of the icon has
  been no longer there although the copy process was not yet complete. I
  will attach a screenshot which shows the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: ubuntu-desktop 1.425
  ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  8 11:00:10 2019
  InstallationDate: Installed on 2018-11-30 (128 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-desktop/+bug/1823674/+subscriptions

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

[Touch-packages] [Bug 1821343] Re: slapd process failure is not detected by systemd

2019-04-08 Thread Heitor R. Alves de Siqueira

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

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

** Patch added: "lp1821343-disco.debdiff"
   
https://bugs.launchpad.net/debian/+source/openldap/+bug/1821343/+attachment/5254240/+files/lp1821343-disco.debdiff

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

Title:
  slapd process failure is not detected by systemd

Status in openldap package in Ubuntu:
  Confirmed
Status in openldap source package in Xenial:
  Confirmed
Status in openldap source package in Bionic:
  Confirmed
Status in openldap source package in Cosmic:
  Confirmed
Status in openldap package in Debian:
  Unknown

Bug description:
  [Impact]
  Systemd service reports slapd as active, even though it may have failed

  [Description]
  The slapd package for OpenLDAP is shipped with a SysV-style init script 
(/etc/init.d/slapd). Systemd automatically converts this to a systemd service 
by generating the unit file using the systemd-sysv-generator(8) utility. The 
generated unit file contains Type=forking and RemainAfterExit=yes directives.

  If the slapd daemon process exits due to some failure (e.g., it
  receives a SIGTERM or SIGKILL), the failure is not detected properly
  by systemd. The service is still reported as active even though the
  child (daemon) process has exited with a signal.

  We can easily fix this by including a proper systemd service file for
  slapd in the openldap package. Since the init.d script already does
  most of the necessary work (parsing configs, setting up PID files,
  etc.), we don't need anything complicated for the systemd unit file.
  Just making sure that RemainAfterExit is set to "no" makes the systemd
  service behave in the expected way.

  [Test Case]
  1) Deploy a disco container
  $ lxc launch images:ubuntu/disco disco

  2) Install slapd
  ubuntu@disco:~$ sudo apt update && sudo apt install slapd -y

  3) Verify that slapd is running with the auto-generated service
  ubuntu@disco:~$ systemctl status slapd
  ● slapd.service - LSB: OpenLDAP standalone server (Lightweight Directory 
Access Protocol)
 Loaded: loaded (/etc/init.d/slapd; generated)
 Active: active (running) since Fri 2019-03-22 11:51:22 UTC; 40min ago
   Docs: man:systemd-sysv-generator(8)
Process: 1103 ExecStart=/etc/init.d/slapd start (code=exited, 
status=0/SUCCESS)
  Tasks: 3 (limit: 4915)
 Memory: 712.6M
 CGroup: /system.slice/slapd.service
 └─1109 /usr/sbin/slapd -h ldap:/// ldapi:/// -g openldap -u 
openldap -F /etc/ldap/slapd.d

  4) SIGKILL the slapd process (PID is displayed in systemctl status output)
  ubuntu@disco:~$ sudo kill -9 1109

  5) Check if systemd service lists slapd as still active, even though it was 
terminated
  ubuntu@disco:~$ systemctl status slapd
  ● slapd.service - LSB: OpenLDAP standalone server (Lightweight Directory 
Access Protocol)
 Loaded: loaded (/etc/init.d/slapd; generated)
 Active: active (exited) since Fri 2019-03-22 11:51:22 UTC; 42min ago
   Docs: man:systemd-sysv-generator(8)
Process: 1103 ExecStart=/etc/init.d/slapd start (code=exited, 
status=0/SUCCESS)

  [Regression Potential]
  The regression potential for this fix should be very low, if we keep the new 
systemd unit file close to the one generated by systemd-sysv-generator(8). The 
only significant change would be the RemainAfterExit directive, and this should 
make the slapd service behave like a "normal" forking service. Nonetheless, 
we'll perform scripted test runs to make sure no regressions arise.

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

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

[Touch-packages] [Bug 1823098] Re: /etc/init.d/ntp prefers DHCP over configured /etc/ntp.conf

** Also affects: cloud-images
   Importance: Undecided
   Status: New

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

Title:
  /etc/init.d/ntp prefers DHCP over configured /etc/ntp.conf

Status in cloud-images:
  New
Status in ntp package in Ubuntu:
  New
Status in ntp source package in Xenial:
  New

Bug description:
  Hi,

  On a few instances in a public cloud, mostly seen in GCE, ntp seems
  incorrectly set up with:

  | ubuntu@juju-453c71-0:~$ ntpq -pn
  |  remote   refid  st t when poll reach   delay   offset  
jitter
  | 
==
  | *169.254.169.254 71.79.79.71  2 u  737 1024  3770.6570.136   
0.147

  We have /etc/ntp.conf configured to use ntp.ubuntu.com as a 'pool'
  host. Turns out, it seems the /etc/init.d/ntp prefers the DHCP version
  over our configured ntp.conf:

  | if [ /var/lib/ntp/ntp.conf.dhcp -nt /etc/ntp.conf ]; then
  | NTPD_OPTS="$NTPD_OPTS -c /var/lib/ntp/ntp.conf.dhcp"
  | fi

  | ubuntu@juju-453c71-0:/etc$ ls -la /var/lib/ntp/ntp.conf.dhcp /etc/ntp.conf
  | -rw-r--r-- 1 root root 626 Feb 25 08:54 /etc/ntp.conf
  | -rw-r--r-- 1 root root 897 Mar 29 21:00 /var/lib/ntp/ntp.conf.dhcp

  I think this is wrong, if /etc/ntp.conf is configured, it should use
  that over what DHCP/dhclient provides.

  | ubuntu@juju-453c71-0:~$ cat /etc/*release
  | DISTRIB_RELEASE=16.04
  | DISTRIB_DESCRIPTION="Ubuntu 16.04.6 LTS"
  | VERSION_ID="16.04"

  | ubuntu@juju-453c71-0:~$ dpkg-query -S /etc/init.d/ntp
  | ntp: /etc/init.d/ntp

  | ubuntu@juju-453c71-0:~$ apt-cache policy ntp
  | ntp:
  |   Installed: 1:4.2.8p4+dfsg-3ubuntu5.9
  |   Candidate: 1:4.2.8p4+dfsg-3ubuntu5.9
  |   Version table:
  |  *** 1:4.2.8p4+dfsg-3ubuntu5.9 500
  | 500 http://us-central1.gce.archive.ubuntu.com/ubuntu 
xenial-updates/main amd64 Packages
  | 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages


  Thanks,

  Haw

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

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

[Touch-packages] [Bug 1812760] Please test proposed package

Hello Daniel, or anyone else affected,

Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.20 in a few
hours, and then in the -proposed repository.

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

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

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

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

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

Title:
  networkd: [Route] PreferredSource not working in *.network files

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Cosmic:
  Fix Committed
Status in systemd source package in Disco:
  Fix Released

Bug description:
  [Impact]

  Users cannot create IPv6 routes that specify PreferredSource. This
  means that users cannot specify a number of valid IPv6 routes that are
  useful in some circumstances. These routes can be created with the
  'ip' tool, just not with systemd.

  This was reported upstream in systemd issue #5882 is fixed by pulling
  in the changes in systemd PR #11375 -
  https://github.com/systemd/systemd/pull/11375

  [Test Case]

  Start a Bionic or Cosmic VM.

  Add the following netplan yaml (adjust for ethernet card and MAC):

  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:e2:c2:d7
  set-name: ens3
  addresses: ["fd8f:1d7d:b141::2/64", "fd8f:1d7d:b141::200/64"]
  routes:
    - to: "a::/16"
  via: "fd8f:1d7d:b141::1"
  from: "fd8f:1d7d:b141::2"
    - to: "fd8f:1d7d:b141::/64"
  scope: link
  from: "fd8f:1d7d:b141::2"
  metric: 255

  Run netplan apply or reboot. Wait ~10s.

  Alternately, to test without netplan, configure systemd-networkd with:

  [Match]
  Name=ens3

  [Network]
  DHCP=ipv4
  LinkLocalAddressing=ipv6
  Address=fd8f:1d7d:b141::2/64
  Address=fd8f:1d7d:b141::200/64

  [Route]
  Destination=a::/16
  Gateway=fd8f:1d7d:b141::1
  PreferredSource=fd8f:1d7d:b141::2

  [Route]
  Destination=fd8f:1d7d:b141::/64
  PreferredSource=fd8f:1d7d:b141::2
  Scope=link
  Metric=255

  [DHCP]
  UseMTU=true
  RouteMetric=100


  Currently, ip -6 route will not include a route to "a::/16", and will
  not include the route to "fd8f:1d7d:b141::/64" that has
  "fd8f:1d7d:b141::2" as the source address - both those addresses will
  be missing.

  Correct behaviour is for ip -6 route to report the following:

  ubuntu@b-np:~$ ip -6 route
  a::/16 via fd8f:1d7d:b141::1 dev ens3 proto static src fd8f:1d7d:b141::2 
metric 1024 pref medium
  fd8f:1d7d:b141::/64 dev ens3 proto static src fd8f:1d7d:b141::2 metric 255 
pref medium
  fd8f:1d7d:b141::/64 dev ens3 proto kernel metric 256 pref medium
  fe80::/64 dev ens3 proto kernel metric 256 pref medium

  Check before and after upgrade that 'systemctl status network-
  online.target' shows that the target has been reached.

  [Regression Potential]

  This changes the state machine in systemd which configures the links.
  It passes systemd's internal tests, and has been approved by systemd
  maintainers, but it remains possible that the changes will break the
  configuration of obscure network setups.

  The backport requires pulling in two further commits that also change
  behaviour: currently systemd deletes all addresses and routes that
  were attached to an interface. With this change, it will only delete
  those that are not specified in the configuration files. A side effect
  of this is that restarting networkd will not cause remove/add netlink
  events to be emitted for these addresses, so if anyone is relying on
  this behavior this will break compatibility; but that is an unlikely
  thing to be relying on, and it seems worth this risk to reduce
  unnecessary network state changes.

To manage notifications

[Touch-packages] [Bug 1818282] Re: systemd-networkd - RoutingPolicyRule does not apply correctly

Hello Ioanna, or anyone else affected,

Accepted systemd into cosmic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/239-7ubuntu10.13 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-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. In either case, without details of
your testing we will not be able to proceed.

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

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

** Changed in: systemd (Ubuntu Cosmic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-cosmic

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

** Tags added: verification-needed-bionic

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

Title:
  systemd-networkd - RoutingPolicyRule does not apply correctly

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Cosmic:
  Fix Committed
Status in systemd source package in Disco:
  Fix Released
Status in systemd package in Debian:
  Fix Committed

Bug description:
  [Impact]

  When attaching multiple IPs on secondary interface the routing policy rules 
do not
  apply for all IPs.
  The rules that are applied after restarting networkd are random.

  The issue has been reported and addressed upstream.

  [Test Case]

  Attach multiple IPs to secondary interface, config file:

  $ cat /etc/systemd/network/ens8.network
  [Match]
  Name=ens8

  [Network]
  Address=172.31.28.195/20
  Address=172.31.24.151/20
  Address=172.31.24.152/20
  Address=172.31.24.153/20

  [Route]
  Destination=0.0.0.0/0
  Gateway=172.31.16.1
  Table=1000

  [Route]
  Destination=172.31.24.153
  Gateway=0.0.0.0
  Scope=link
  Table=1000

  [Route]
  Destination=172.31.28.195
  Gateway=0.0.0.0
  Scope=link
  Table=1000

  [Route]
  Destination=172.31.24.151
  Gateway=0.0.0.0
  Scope=link
  Table=1000

  [Route]
  Destination=172.31.24.152
  Gateway=0.0.0.0
  Scope=link
  Table=1000

  [RoutingPolicyRule]
  From=172.31.24.153
  Table=1000

  [RoutingPolicyRule]
  From=172.31.28.195
  Table=1000

  [RoutingPolicyRule]
  From=172.31.24.152
  Table=1000

  [RoutingPolicyRule]
  From=172.31.24.151
  Table=1000

  $ ip rule show
  0:from all lookup local
  0:from 172.31.24.151 lookup 1000
  32766:from all lookup main
  32767:from all lookup default

  - restart networkd

  $ sudo systemctl restart systemd-networkd

  $ ip rule show
  0:from all lookup local
  0:from 172.31.24.151 lookup 1000
  0:from 172.31.24.153 lookup 1000
  0:from 172.31.28.195 lookup 1000
  32766:from all lookup main
  32767:from all lookup default

  - restart again

  $ sudo systemctl restart systemd-networkd

  $ ip rule show
  0:from all lookup local
  0:from 172.31.24.151 lookup 1000
  0:from 172.31.24.152 lookup 1000
  32766:from all lookup main
  32767:from all lookup default

  The behaviour is random

  [Regression Potential]

  May impact the systemd-networkd service functionality.

  [Other]

  Affects Disco Bionic and Cosmic.

  Upstream bug : https://github.com/systemd/systemd/issues/11280
  Upstream fix : https://github.com/systemd/systemd/pull/11795/commits

  $ lsb_release -rd
  Description:  Ubuntu Disco Dingo (development branch)
  Release:  19.04

  Systemd version :
  systemd:
    Installed: 240-6ubuntu1
    Candidate: 240-6ubuntu1
    Version table:
   *** 240-6ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1818282] Please test proposed package

Hello Ioanna, or anyone else affected,

Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.20 in a few
hours, and then in the -proposed repository.

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

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

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

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

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

Title:
  systemd-networkd - RoutingPolicyRule does not apply correctly

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Cosmic:
  Fix Committed
Status in systemd source package in Disco:
  Fix Released
Status in systemd package in Debian:
  Fix Committed

Bug description:
  [Impact]

  When attaching multiple IPs on secondary interface the routing policy rules 
do not
  apply for all IPs.
  The rules that are applied after restarting networkd are random.

  The issue has been reported and addressed upstream.

  [Test Case]

  Attach multiple IPs to secondary interface, config file:

  $ cat /etc/systemd/network/ens8.network
  [Match]
  Name=ens8

  [Network]
  Address=172.31.28.195/20
  Address=172.31.24.151/20
  Address=172.31.24.152/20
  Address=172.31.24.153/20

  [Route]
  Destination=0.0.0.0/0
  Gateway=172.31.16.1
  Table=1000

  [Route]
  Destination=172.31.24.153
  Gateway=0.0.0.0
  Scope=link
  Table=1000

  [Route]
  Destination=172.31.28.195
  Gateway=0.0.0.0
  Scope=link
  Table=1000

  [Route]
  Destination=172.31.24.151
  Gateway=0.0.0.0
  Scope=link
  Table=1000

  [Route]
  Destination=172.31.24.152
  Gateway=0.0.0.0
  Scope=link
  Table=1000

  [RoutingPolicyRule]
  From=172.31.24.153
  Table=1000

  [RoutingPolicyRule]
  From=172.31.28.195
  Table=1000

  [RoutingPolicyRule]
  From=172.31.24.152
  Table=1000

  [RoutingPolicyRule]
  From=172.31.24.151
  Table=1000

  $ ip rule show
  0:from all lookup local
  0:from 172.31.24.151 lookup 1000
  32766:from all lookup main
  32767:from all lookup default

  - restart networkd

  $ sudo systemctl restart systemd-networkd

  $ ip rule show
  0:from all lookup local
  0:from 172.31.24.151 lookup 1000
  0:from 172.31.24.153 lookup 1000
  0:from 172.31.28.195 lookup 1000
  32766:from all lookup main
  32767:from all lookup default

  - restart again

  $ sudo systemctl restart systemd-networkd

  $ ip rule show
  0:from all lookup local
  0:from 172.31.24.151 lookup 1000
  0:from 172.31.24.152 lookup 1000
  32766:from all lookup main
  32767:from all lookup default

  The behaviour is random

  [Regression Potential]

  May impact the systemd-networkd service functionality.

  [Other]

  Affects Disco Bionic and Cosmic.

  Upstream bug : https://github.com/systemd/systemd/issues/11280
  Upstream fix : https://github.com/systemd/systemd/pull/11795/commits

  $ lsb_release -rd
  Description:  Ubuntu Disco Dingo (development branch)
  Release:  19.04

  Systemd version :
  systemd:
    Installed: 240-6ubuntu1
    Candidate: 240-6ubuntu1
    Version table:
   *** 240-6ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1812760] Re: networkd: [Route] PreferredSource not working in *.network files

Hello Daniel, or anyone else affected,

Accepted systemd into cosmic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/239-7ubuntu10.13 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-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. In either case, without details of
your testing we will not be able to proceed.

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

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

** Changed in: systemd (Ubuntu Cosmic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-cosmic

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

** Tags added: verification-needed-bionic

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

Title:
  networkd: [Route] PreferredSource not working in *.network files

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Cosmic:
  Fix Committed
Status in systemd source package in Disco:
  Fix Released

Bug description:
  [Impact]

  Users cannot create IPv6 routes that specify PreferredSource. This
  means that users cannot specify a number of valid IPv6 routes that are
  useful in some circumstances. These routes can be created with the
  'ip' tool, just not with systemd.

  This was reported upstream in systemd issue #5882 is fixed by pulling
  in the changes in systemd PR #11375 -
  https://github.com/systemd/systemd/pull/11375

  [Test Case]

  Start a Bionic or Cosmic VM.

  Add the following netplan yaml (adjust for ethernet card and MAC):

  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:e2:c2:d7
  set-name: ens3
  addresses: ["fd8f:1d7d:b141::2/64", "fd8f:1d7d:b141::200/64"]
  routes:
    - to: "a::/16"
  via: "fd8f:1d7d:b141::1"
  from: "fd8f:1d7d:b141::2"
    - to: "fd8f:1d7d:b141::/64"
  scope: link
  from: "fd8f:1d7d:b141::2"
  metric: 255

  Run netplan apply or reboot. Wait ~10s.

  Alternately, to test without netplan, configure systemd-networkd with:

  [Match]
  Name=ens3

  [Network]
  DHCP=ipv4
  LinkLocalAddressing=ipv6
  Address=fd8f:1d7d:b141::2/64
  Address=fd8f:1d7d:b141::200/64

  [Route]
  Destination=a::/16
  Gateway=fd8f:1d7d:b141::1
  PreferredSource=fd8f:1d7d:b141::2

  [Route]
  Destination=fd8f:1d7d:b141::/64
  PreferredSource=fd8f:1d7d:b141::2
  Scope=link
  Metric=255

  [DHCP]
  UseMTU=true
  RouteMetric=100


  Currently, ip -6 route will not include a route to "a::/16", and will
  not include the route to "fd8f:1d7d:b141::/64" that has
  "fd8f:1d7d:b141::2" as the source address - both those addresses will
  be missing.

  Correct behaviour is for ip -6 route to report the following:

  ubuntu@b-np:~$ ip -6 route
  a::/16 via fd8f:1d7d:b141::1 dev ens3 proto static src fd8f:1d7d:b141::2 
metric 1024 pref medium
  fd8f:1d7d:b141::/64 dev ens3 proto static src fd8f:1d7d:b141::2 metric 255 
pref medium
  fd8f:1d7d:b141::/64 dev ens3 proto kernel metric 256 pref medium
  fe80::/64 dev ens3 proto kernel metric 256 pref medium

  Check before and after upgrade that 'systemctl status network-
  online.target' shows that the target has been reached.

  [Regression Potential]

  This changes the state machine in systemd which configures the links.
  It passes systemd's internal tests, and has been approved by systemd
  maintainers, but it remains possible that the changes will break the
  configuration of obscure network setups.

  The backport requires pulling in two further commits that also change
  behaviour: currently systemd deletes all addresses and routes that
  were attached to an interface. With this change, it will only delete
  those that are not specified in the configuration files. A side effect
  of this is that restarting networkd will not cause remove/add

[Touch-packages] [Bug 1615381] Re: apt-get autoremove may remove current kernel

2019-04-08 Thread Balint Reczey

Verified 1.1ubuntu1.18.04.7~16.04.2 on Xenial.

Installed a few linux packages, marked them auto-installed, ran 
/etc/kernel/postinst.d/apt-auto-removal , then booted to a old kernel.
Apt would have removed it, but u-u did not. (The -34- kernel.)

ubuntu@ubuntu-Standard-PC-i440FX-PIIX-1996:~$ uname -a
Linux ubuntu-Standard-PC-i440FX-PIIX-1996 4.15.0-34-generic #37~16.04.1-Ubuntu 
SMP Tue Aug 28 10:44:06 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
ubuntu@ubuntu-Standard-PC-i440FX-PIIX-1996:~$ yes no | apt autoremove 
E: Could not open lock file /var/lib/dpkg/lock-frontend - open (13: Permission 
denied)
E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), are 
you root?
ubuntu@ubuntu-Standard-PC-i440FX-PIIX-1996:~$ yes no | sudo apt autoremove 
[sudo] password for ubuntu: 
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following packages will be REMOVED:
  linux-image-4.15.0-34-generic linux-image-4.15.0-36-generic 
linux-image-4.15.0-38-generic linux-modules-4.15.0-34-generic 
linux-modules-4.15.0-36-generic
  linux-modules-4.15.0-38-generic
0 upgraded, 0 newly installed, 6 to remove and 9 not upgraded.
After this operation, 223 MB disk space will be freed.
Do you want to continue? [Y/n] Abort.
ubuntu@ubuntu-Standard-PC-i440FX-PIIX-1996:~$ sudo unattended-upgrade --dry-run 
--verbose
Initial blacklisted packages: 
Initial whitelisted packages: 
Starting unattended upgrades script
Allowed origins are: o=Ubuntu,a=xenial, o=Ubuntu,a=xenial-security, 
o=UbuntuESM,a=xenial
Removing unused kernel packages: linux-modules-4.15.0-36-generic 
linux-image-4.15.0-36-generic linux-modules-4.15.0-38-generic 
linux-image-4.15.0-38-generic
Keeping auto-removable linux-modules-4.15.0-36-generic package(s) because it 
would also remove the following packages which should be kept in this step: 
libpam-systemd libsmbclient libsystemd0 libudev1 libwbclient0 samba-libs 
systemd systemd-sysv udev
Packages that were successfully auto-removed: 
Packages that are kept back: linux-modules-4.15.0-36-generic
ubuntu@ubuntu-Standard-PC-i440FX-PIIX-1996:~$ dpkg -l unattended-upgrades  | cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ NameVersionArchitecture Description
+++-===-==--===
ii  unattended-upgrades 1.1ubuntu1.18.04.7~16.04.2 all  automatic 
installation of security upgrades


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

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

Title:
  apt-get autoremove may remove current kernel

Status in apt package in Ubuntu:
  Won't Fix
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in apt source package in Trusty:
  Won't Fix
Status in unattended-upgrades source package in Trusty:
  New
Status in apt source package in Xenial:
  Won't Fix
Status in unattended-upgrades source package in Xenial:
  Fix Committed
Status in apt source package in Artful:
  Won't Fix
Status in unattended-upgrades source package in Artful:
  Won't Fix

Bug description:
  This may happen, if you boot one of the older kernels, that is not
  protected by /etc/apt/apt.conf.d/01autoremove-kernels

  Workaround: run
  /etc/kernel/postinst.d/apt-auto-removal
  during each boot (e.g. by using cron).
  Note: The workaround breaks autoremoving feature of new unneeded kernels in  
unattended-upgrades i.e. the setting 
'Unattended-Upgrade::Remove-New-Unused-Dependencies "true"' (which is default 
in 16.04 unless 'Unattended-Upgrade::Remove-Unused-Dependencies "true"' is set 
in '/etc/apt/apt.conf.d/50unattended-upgrades'.

  
  In shell:

  $ uname -r
  4.4.0-22-generic
  $ apt-get -s autoremove
  NOTE: This is only a simulation!
    apt-get needs root privileges for real execution.
    Keep also in mind that locking is deactivated,
    so don't depend on the relevance to the real current situation!
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  The following packages will be REMOVED:
    linux-headers-4.4.0-21 linux-headers-4.4.0-21-generic linux-headers-4.4.0-22
    linux-headers-4.4.0-22-generic linux-headers-4.4.0-31-generic
    linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic
    linux-image-4.4.0-31-generic linux-image-extra-4.4.0-21-generic
    linux-image-extra-4.4.0-22-generic linux-image-extra-4.4.0-31-generic
  0 upgraded, 0 newly installed, 11 to remove and 13 not upgraded.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.12~ubuntu16.04.1
  ProcVersionSignature:

[Touch-packages] [Bug 1823098] Re: /etc/init.d/ntp prefers DHCP over configured /etc/ntp.conf

** Tags added: xenial

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

Title:
  /etc/init.d/ntp prefers DHCP over configured /etc/ntp.conf

Status in ntp package in Ubuntu:
  New
Status in ntp source package in Xenial:
  New

Bug description:
  Hi,

  On a few instances in a public cloud, mostly seen in GCE, ntp seems
  incorrectly set up with:

  | ubuntu@juju-453c71-0:~$ ntpq -pn
  |  remote   refid  st t when poll reach   delay   offset  
jitter
  | 
==
  | *169.254.169.254 71.79.79.71  2 u  737 1024  3770.6570.136   
0.147

  We have /etc/ntp.conf configured to use ntp.ubuntu.com as a 'pool'
  host. Turns out, it seems the /etc/init.d/ntp prefers the DHCP version
  over our configured ntp.conf:

  | if [ /var/lib/ntp/ntp.conf.dhcp -nt /etc/ntp.conf ]; then
  | NTPD_OPTS="$NTPD_OPTS -c /var/lib/ntp/ntp.conf.dhcp"
  | fi

  | ubuntu@juju-453c71-0:/etc$ ls -la /var/lib/ntp/ntp.conf.dhcp /etc/ntp.conf
  | -rw-r--r-- 1 root root 626 Feb 25 08:54 /etc/ntp.conf
  | -rw-r--r-- 1 root root 897 Mar 29 21:00 /var/lib/ntp/ntp.conf.dhcp

  I think this is wrong, if /etc/ntp.conf is configured, it should use
  that over what DHCP/dhclient provides.

  | ubuntu@juju-453c71-0:~$ cat /etc/*release
  | DISTRIB_RELEASE=16.04
  | DISTRIB_DESCRIPTION="Ubuntu 16.04.6 LTS"
  | VERSION_ID="16.04"

  | ubuntu@juju-453c71-0:~$ dpkg-query -S /etc/init.d/ntp
  | ntp: /etc/init.d/ntp

  | ubuntu@juju-453c71-0:~$ apt-cache policy ntp
  | ntp:
  |   Installed: 1:4.2.8p4+dfsg-3ubuntu5.9
  |   Candidate: 1:4.2.8p4+dfsg-3ubuntu5.9
  |   Version table:
  |  *** 1:4.2.8p4+dfsg-3ubuntu5.9 500
  | 500 http://us-central1.gce.archive.ubuntu.com/ubuntu 
xenial-updates/main amd64 Packages
  | 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages


  Thanks,

  Haw

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

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

[Touch-packages] [Bug 1818204] Re: Qualcomm Atheros QCA9377 wireless does not work

2019-04-08 Thread Kai-Heng Feng

It should be 4.18.0-18-generic.

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

Title:
  Qualcomm Atheros QCA9377 wireless does not work

Status in linux package in Ubuntu:
  Fix Committed
Status in network-manager package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Committed
Status in network-manager source package in Bionic:
  Invalid
Status in linux source package in Cosmic:
  Fix Committed
Status in network-manager source package in Cosmic:
  Invalid

Bug description:
  === SRU Justification ===
  [Impact] 
  Lenovo ideapad 530S-14ARR Wifi rfkill hard blocked

  [Fix]
  The platform in question doesn't have hardware RF switch, so quirk it
  off.
   
  [Test]
  User confirm it fixes the issue.

  [Regression Potential]
  Minimal. This fix is limited to one specific platform.

  === Original Bug Report ===
  I have Lenovo 530s laptop with Qualcomm Atheros QCA9377 802.11ac Wireless 
Network Adapter (rev 31).

  The menu shows that wireless is off. Turning on the wireless from the
  menu does not do anything.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1.1
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  1 11:42:34 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-02-20 (8 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IpRoute:
   default via 130.232.69.254 dev enx00e04c704f68 proto dhcp metric 100
   130.232.69.0/24 dev enx00e04c704f68 proto kernel scope link src 
130.232.69.176 metric 100
   169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY 
 READONLY  DBUS-PATH   ACTIVE  DEVICE   
STATE  ACTIVE-PATH  SLAVE
   Wired connection 1  ada277fe-966d-33ff-aba2-8ba32d6ce5a9  ethernet  
155143  pe  1. maaliskuuta 2019 11.42.13  yes  4294966297   
 no/org/freedesktop/NetworkManager/Settings/1  yes enx00e04c704f68  
activated  /org/freedesktop/NetworkManager/ActiveConnection/11  --
   virbr0  dc46fe89-5b22-438a-85d5-37be48a077ea  bridge
155143  pe  1. maaliskuuta 2019 11.42.13  no   0
 no/org/freedesktop/NetworkManager/Settings/2  yes virbr0   
activated  /org/freedesktop/NetworkManager/ActiveConnection/1   --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI  WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
disabled  enabled  enabled
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sami   1315 F pulseaudio
   /dev/snd/controlC0:  sami   1315 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-02-20 (11 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IpRoute:
   default via 130.232.69.254 dev enx00e04c704f68 proto dhcp metric 100
   130.232.69.0/24 dev enx00e04c704f68 proto kernel scope link src 
130.232.69.176 metric 100
   169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  MachineType: LENOVO 81H1
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.10.6-2ubuntu1.1
  PackageArchitecture: amd64
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic 
root=UUID=a6aaac69-de44-4491-bfb7-0e57c9ff25cf ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-15-generic N/A
   linux-backports-modules-4.18.0-15-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic wayland-session wayland-session
  Uname:

[Touch-packages] [Bug 1822416] Re: resolve: do not hit CNAME or DNAME entry in NODATA cache

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

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

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

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

Title:
  resolve: do not hit CNAME or DNAME entry in NODATA cache

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The question: DNS A record lookups fail to resolve due to cached CNAME
  NODATA lookups ...

  https://askubuntu.com/questions/1063462/18-04-server-systemd-resolve-
  returns-cached-cname-nodata-for-a-lookup

  Upstream at Github: Systemd issue 998 - Cached cname NODATA returned
  for A lookup ...

  https://github.com/systemd/systemd/issues/9833

  
  Please patch ...

  
https://github.com/systemd/systemd/commit/3740146a4cbd99883af79e375ee4836206dcea4e

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

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

[Touch-packages] [Bug 1818814] Re: systemd-tmpfiles-setup.services fails to create /var/run directories

@kalle-tuulos,

are you able to test with the latest systemd pkgs to see if this still
happens?  If it does, can you paste the output of:

$ grep . /etc/tmpfiles.d/* /run/tmpfiles.d/* /usr/lib/tmpfiles.d/*

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

Title:
  systemd-tmpfiles-setup.services fails to create /var/run directories

Status in systemd package in Ubuntu:
  New

Bug description:
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  Description:Ubuntu 16.04.6 LTS
   
  Release:16.04 
   

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  systemd:  
   
Installed: 229-4ubuntu21.16 
   
Candidate: 229-4ubuntu21.16 
   
Version table:  
   
   *** 229-4ubuntu21.16 500 
   
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages  
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status  
   
   229-4ubuntu4 500 
   
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages   
 

  3) What you expected to happen
  4) What happened instead

  Ubuntu server (running in OpenVZ VPS farm, thus the old kernel
  version) has been up and running happily, until I performed apt-get
  upgrade and rebooted the server. After reboot, I could not establish
  SSH connection to server, port 22 connection was refused.

  I opened a HTML console to my server instance and checked logs. From
  the logs, it was shown, that SSH server could not start, as it did not
  have the /var/run/sshd directory. After scrolling back the
  /var/log/syslog, I noticed that there were lots of other /var/run
  subdirectories, which were not created. Here is cut from
  /var/log/syslog, related to systemd-tmpfiles:

  ---8<---8<---
  Mar  6 12:32:54 vspk systemd-tmpfiles[81]: 
[/usr/lib/tmpfiles.d/00rsyslog.conf:6] Duplicate line for path "/v
  ar/log", ignoring.
   
  Mar  6 12:32:54 vspk systemd[1]: Starting Raise network interfaces... 
   
  Mar  6 12:32:54 vspk systemd-tmpfiles[81]: fchownat() of /run/named failed: 
Invalid argument 
  Mar  6 12:32:54 vspk systemd-tmpfiles[81]: Failed to validate path 
/var/run/fail2ban: Too many levels of symb
  olic links
   
  Mar  6 12:32:54 vspk systemd-tmpfiles[81]: Failed to validate path 
/var/run/screen: Too many levels of symbol
  ic links  
   
  Mar  6 12:32:54 vspk systemd-tmpfiles[81]: Failed to validate path 
/var/run/sshd: Too many levels of symbolic
   links
   
  Mar  6 12:32:54 vspk systemd-tmpfiles[81]: Failed to validate path 
/var/run/sudo: Too many levels of symbolic
   links
   
  Mar  6 12:32:54 vspk systemd-tmpfiles[81]: Failed to validate path 
/var/run/sudo/ts: Too many levels of symbo
  lic links 
   
  Mar  6 12:32:54 vspk systemd-tmpfiles[81]: fchownat() of /run/utmp failed: 
Invalid argument  
  Mar  6 12:32:54 vspk systemd-tmpfiles[81]: fchownat() of /run/systemd/netif 
failed: Invalid argument 
  Mar  6 12:32:54 vspk systemd-tmpfiles[81]: fchownat() of 
/run/systemd/netif/links failed: Invalid argument   
  Mar  6 12:32:54 vspk systemd-tmpfiles[81]: fchownat() of 
/run/systemd/netif/leases failed: Invalid argument  
  Mar  6 12:32:54 vspk systemd-tmpfiles[81]: Failed to validate path 
/var/run/zabbix: Too many levels of symbol
  ic links

[Touch-packages] [Bug 1823550] Re: GtkSourceView wrongly has monospaced font in dropdown (context) menu

I'm using default clean installation of Ubuntu with default settings of
GNOME desktop (say 18.04 LTS).

> Did you try changing font by de-selecting "use system fixed width
font" ?

Going to Preferences → Font & Colors → Font, and deselecting "use system
fixed width font" substitutes font with other monospaced font - see
image.


So this is not a solution.

** Attachment added: ""use system fixed width font" unchecked"
   
https://bugs.launchpad.net/ubuntu/+source/pluma/+bug/1823550/+attachment/5254209/+files/unchecked.png

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

Title:
  GtkSourceView wrongly has monospaced font in dropdown (context) menu

Status in GtkSourceView:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Invalid
Status in gtksourceview3 package in Ubuntu:
  Invalid
Status in mate-themes package in Ubuntu:
  New
Status in pluma package in Ubuntu:
  Invalid
Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 17.04 or later installed
  2. Open any application with GtkSourceView component - such as Pluma, Gedit, 
Giggle, Gitg, gnome-builder and maybe others (see complete list with `apt-cache 
rdepends libgtksourceview-3.0-1`)
  3. Click right mouse button on text zone

  Expected result:
  * dropdown menu has normal font as all other interface elements

  Actual result:
  * dropdwon menu wrongly has monospaced font

  Notes:
  * first seen in 17.04, but persists in 17.10, 18.04 LTS, 18.10, 19.04 
releases.
  * seems to be caused by GTK3 library

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: pluma 1.18.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.10
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sun Apr  7 20:13:24 2019
  InstallationDate: Installed on 2018-08-07 (243 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: pluma
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1821343] Re: slapd process failure is not detected by systemd

2019-04-08 Thread Heitor R. Alves de Siqueira

I've been doing some research on how we could implement a proper systemd
unit file for slapd, and came up with interesting results.

There are a number of options that we can pass to the slapd service that will 
give us lots of troubles on an "idiomatic" service file. To give some examples:
- The PID file can be directly obtained from /etc/default/slapd if set, or it
  has to be parsed from /etc/ldap/slapd.d or /etc/ldap/slapd.conf. The /etc/ldap
  files don't follow the /etc/default syntax, so we can't just pass them with
  "EnvironmentFile=" in the systemd service. We would have to parse those files
  as is currently done by the init script.
- slapd has the "-f" and "-F" flags that can be used to specify a config file or
  directory, respectively. It does not accept both at the same time, but
  SLAPD_CONF in /etc/default/slapd allows either a file or directory. The init
  script will figure out which of those is set, and pass the correct flag
  accordingly. I don't see a simple way of doing this in systemd without either
  polluting the SLAPD_CONF option with the necessary flag, or delegating it to a
  helper script which would check whether the option meant a file or a
  directory.
- The slapd.conf file is used by other related tools (see slapd.conf(5)), which
  prevents us from pulling some of the options to another centralized file
  without also updating these tools

I hoped that the upstream package would have some insight on the proper
way of writing the service file, but unfortunately it seems that
upstream Openldap devs are very much against the idea of shipping them
(be they sysv-init or systemd files). There are some discussions on the
openldap lists, one of which deals specifically with adding systemd
support for slapd [0]. From that discussion, it's clear that upstream
openldap is not ready to provide the necessary systemd files out-of-the-
box, even when approached with relevant patches.

I also checked how CentOS implement their slapd.service file since they don't 
seem to run into these problems. They don't use an autogenerated unit file, and 
have a proper one instead [1]. From what I've checked, this is easier for them 
for two reasons:
1) The CentOS configs for slapd are much simpler than what we have in 
Debian/Ubuntu (their defaults don't include most of the options that we do)
2) They use helper scripts for the funky parsing we have in the sysv-init 
script ("ExecStartPre=/usr/libexec/openldap/check-config.sh", which also 
invokes some other helper scripts)

On Debian/Ubuntu, the autogenerated unit file for slapd uses the sysv-init 
script as a "shim" to manage the service, which makes it possible to keep the 
whole config-parsing insanity consistent between sysv-init and systemd.
It's not the most elegant solution, but for now I believe it makes sense to 
include an override file for the "RemainAfterExit=" option until we have a 
native systemd unit file for slapd (similar to what was done for apache2 in bug 
1488962 mentioned by Ryan Tandy).

[0] https://www.openldap.org/its/index.cgi/Incoming?id=8707
[1] https://git.centos.org/blob/rpms!openldap.git/c7/SOURCES!slapd.service

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

Title:
  slapd process failure is not detected by systemd

Status in openldap package in Ubuntu:
  Confirmed
Status in openldap source package in Xenial:
  Confirmed
Status in openldap source package in Bionic:
  Confirmed
Status in openldap source package in Cosmic:
  Confirmed

Bug description:
  [Impact]
  Systemd service reports slapd as active, even though it may have failed

  [Description]
  The slapd package for OpenLDAP is shipped with a SysV-style init script 
(/etc/init.d/slapd). Systemd automatically converts this to a systemd service 
by generating the unit file using the systemd-sysv-generator(8) utility. The 
generated unit file contains Type=forking and RemainAfterExit=yes directives.

  If the slapd daemon process exits due to some failure (e.g., it
  receives a SIGTERM or SIGKILL), the failure is not detected properly
  by systemd. The service is still reported as active even though the
  child (daemon) process has exited with a signal.

  We can easily fix this by including a proper systemd service file for
  slapd in the openldap package. Since the init.d script already does
  most of the necessary work (parsing configs, setting up PID files,
  etc.), we don't need anything complicated for the systemd unit file.
  Just making sure that RemainAfterExit is set to "no" makes the systemd
  service behave in the expected way.

  [Test Case]
  1) Deploy a disco container
  $ lxc launch images:ubuntu/disco disco

  2) Install slapd
  ubuntu@disco:~$ sudo apt update && sudo apt install slapd -y

  3) Verify that slapd is running with the auto-generated service
  ubuntu@disco:~$ systemctl status slapd
  ● slapd.service -

[Touch-packages] [Bug 1796501] Re: systemd-resolved tries to mitigate DVE-2018-0001 even if DNSSEC=yes

2019-04-08 Thread jrb0001

Has there been any progress so far? systemd-resolved would be nice in
theory, but not if it breaks half of the websites like it did before I
stopped using it.

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

Title:
  systemd-resolved tries to mitigate DVE-2018-0001 even if DNSSEC=yes

Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Cosmic:
  In Progress
Status in systemd source package in Disco:
  In Progress

Bug description:
  I ask systemd-resolved through dig to resolve the SOA of test.asdf. (doesn't 
exist) but it returns SERVFAIL instead of NXDOMAIN. It seems to do the 
following steps:
  1. Ask upstream for SOA of test.asdf. with EDNS0, DO-bit and 4k size.
  2. Ask upstream for SOA of test.asdf. with EDNS0 and DO-bit.
  3. Ask upstream for SOA of test.asdf. with EDNS0.
  4. Ask upstream for SOA of test.asdf. without EDNS0.
  5. Repeat 1-4 for DS of test.asdf.
  6. Repeat 1-5 for asdf.
  7. Ask upstream for SOA of . with EDNS0, DO-bit and 4k size.
  8. Ask upstream for DNSKEY of . with EDNS0, DO-bit and 4k size.

  The upstream returns an unfragmented NXDOMAIN response for steps 1-6,
  an unfragmented NOERROR response for step 7 and a fragmented NOERROR
  response for step 8 which is the correct behaviour. DNSSEC records are
  included in the response if the DO-bit in the request was set.

  systemd-resolved should take the response from step 1 and start with
  validation instead of starting useless retries with reduced feture
  set. Step 3 and 4 are completely useless and probably lead to the
  SERVFAIL because I have configured it with DNSSEC=yes to prevent
  downgrade attacks.

  This regression seems to be caused by the patch resolved-Mitigate-
  DVE-2018-0001-by-retrying-NXDOMAIN-with.patch. The downgrade logic
  should only be executed if it is configured as DNSSEC=allow-downgrade
  or DNSSEC=no. See also
  https://github.com/systemd/systemd/pull/8608#issuecomment-396927885.

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

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

[Touch-packages] [Bug 1823423] Re: ibus ftbfs in disco

This bug was fixed in the package ibus - 1.5.19-1ubuntu2

---
ibus (1.5.19-1ubuntu2) disco; urgency=medium

  * Fix FTBFS for Vala >= 0.34.4 (LP: #1823423)
- debian/patches/delete-weak-pointer.patch: from Upstream

 -- Mitsuya Shibata   Sat, 06 Apr 2019 20:15:52
+0900

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

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

Title:
  ibus ftbfs in disco

Status in ibus package in Ubuntu:
  Fix Released

Bug description:
  https://launchpadlibrarian.net/417924597/buildlog_ubuntu-disco-
  amd64.ibus_1.5.19-1ubuntu1_BUILDING.txt.gz

  multiple vala/glib errors

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

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

[Touch-packages] [Bug 1816530] Re: DNS servers are not being set in the system correctly when you upgrade from 16.04 to 18.04

@zoltan-sule,

can you add the results of running:

$ ls -l /etc/resolv.conf

$ cat /etc/resolv.conf

$ systemd-resolve --status

$ grep . /run/resolvconf/interface/*

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

Title:
  DNS servers are not being set in the system correctly when you upgrade
  from 16.04 to 18.04

Status in resolvconf package in Ubuntu:
  New

Bug description:
  I upgraded my 16.04 to 18.04 before the official release. After the
  upgrade I noticed that I don't have internet access. The wired network
  and the wifi settings looked good, but the internet didn't work. After
  the login the system always switched itself into airplane mode. I
  tethered the network via USB and Bluetooth by my mobile but they also
  didn't work.

  I found a useful answer from @andrew-woodhead666:
  https://answers.launchpad.net/ubuntu/+question/665374

  it seems this bug is still not fixed for the upgraded dists in the main 
release and affects a few dozens of ubuntu users.
  
https://askubuntu.com/questions/1021884/no-internet-after-upgrade-from-16-04-to-18-04

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

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

[Touch-packages] [Bug 1823550] Re: GtkSourceView wrongly has monospaced font in dropdown (context) menu

2019-04-08 Thread Khurshid Alam

Did you try changing font by de-selecting "use system fixed width font"
?

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

Title:
  GtkSourceView wrongly has monospaced font in dropdown (context) menu

Status in GtkSourceView:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Invalid
Status in gtksourceview3 package in Ubuntu:
  Invalid
Status in mate-themes package in Ubuntu:
  New
Status in pluma package in Ubuntu:
  Invalid
Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 17.04 or later installed
  2. Open any application with GtkSourceView component - such as Pluma, Gedit, 
Giggle, Gitg, gnome-builder and maybe others (see complete list with `apt-cache 
rdepends libgtksourceview-3.0-1`)
  3. Click right mouse button on text zone

  Expected result:
  * dropdown menu has normal font as all other interface elements

  Actual result:
  * dropdwon menu wrongly has monospaced font

  Notes:
  * first seen in 17.04, but persists in 17.10, 18.04 LTS, 18.10, 19.04 
releases.
  * seems to be caused by GTK3 library

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: pluma 1.18.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.10
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sun Apr  7 20:13:24 2019
  InstallationDate: Installed on 2018-08-07 (243 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: pluma
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1553466] Re: org.gnome.SessionManager was not provided by any .service files

2019-04-08 Thread josergc

I got this in lubuntu 18.04 running dolphin-emu

org.freedesktop.DBus.Error.ServiceUnknown: The name
org.gnome.SessionManager was not provided by any .service files

my uname -a values:

Linux my-ubuntu 4.15.0-47-generic #50-Ubuntu SMP Wed Mar 13 10:44:52 UTC
2019 x86_64 x86_64 x86_64 GNU/Linux

any update on this issue?

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

Title:
  org.gnome.SessionManager was not provided by any .service files

Status in dbus package in Ubuntu:
  Confirmed

Bug description:
  This is logged into journalctl:

   org.gnome.ScreenSaver[1755]: ** (gnome-screensaver:1868): WARNING **:
  Couldn't get presence status: The name org.gnome.SessionManager was
  not provided by any .service files

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: dbus 1.10.6-1ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
  Uname: Linux 4.4.0-10-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Mar  5 08:37:25 2016
  ExecutablePath: /usr/bin/dbus-daemon
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: dbus
  UpgradeStatus: No upgrade log present (probably fresh install)
  upstart.dbus.log:
   Activating service name='org.gnome.Terminal'
   Successfully activated service 'org.gnome.Terminal'
   Activating service name='org.gnome.Terminal'
   Successfully activated service 'org.gnome.Terminal'

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

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

[Touch-packages] [Bug 1636708] Re: ifup -a does not start dependants last, causes deadlocks with vlans/bonding

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

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

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

Title:
  ifup -a does not start dependants last, causes deadlocks with
  vlans/bonding

Status in ifupdown package in Ubuntu:
  Incomplete
Status in ifupdown source package in Xenial:
  Incomplete

Bug description:
  This is a problem I've been struggling with since moving to 16.04.1
  from 14.04 (fresh install)

  I don't believe this problem affected 14.04. I have used an almost
  identical interfaces file on 14.04 without problem.

  On 16.04.1, however, 9/10 boots would hang during network
  configuration and leave the network incorrectly configured.

  When calling "ifup -a" all candidate interfaces appear to be started
  in parallel leading to collisions with locks. This causes hanging
  (until timeout) during booting and the network interfaces left
  incorrectly configured

  Imagine this /etc/network/interfaces

  auto eno1 bond0 bond0.1

  iface eno1 inet manual
  bond-master bond0

  iface bond0 inet manual
  bond-slaves eno1
  bond-mode   4
  bond-lacp-rate  1
  bond-miimon 100
  bond-updelay200
  bond-downdelay  200

  iface bond0.5 inet dhcp
  vlan-raw-device bond0

  
  eno1 -> bond0 -> bond0.5 -> dhcp

  When calling "ifup -a" at boot time all three interfaces are started
  at the same time.

  bond0 and bond0.5 both attempt to share the same lock file:

/run/network/ifstate.bond0

  If bond0 wins the race, the system will start correctly (1/10):

* bond0 starts and creates the bond0 device and the ifenslave.bond0 file to 
indicate the bond is ready
* eno1 polls for the ifenslave.bond0 file, when it appears it attaches eno1 
to bond0
* bond0 finishes and releases the lock
* bond0.5 now acquires the lock.
* bond0.5 starts dhclient, which can talk to the network and configure the 
interface

  
  If, however, bond0.2 wins the lock race, the system will hang at boot (5 
mins) and fail to set up the network.

* bond0.5 is awarded the ifstate.bond0 lockfile
* bond0.5 starts dhclient waiting to hear from the network
* bond0 is blocked, so bond0 is not created nor is the bond0.ifenslave file 
* eno1 polls but never finds the ifenslave.bond0 file so never attaches to 
bond0
* bond0.5's dhclient is trying to talk to a disconnected network and never 
receives an answer

! bond0.5 is stuck running dhclient
! bond0 is stuck waiting for bond0.5 to finish
! eno1 is stuck waiting for bond0 to create the ifenslave.bond0 file

  
  I believe ifup should start interfaces (that share lock files) in dependant 
order. The most basic interface must be awarded the lock over its dependants. 
In this case:

1 eno1
2 bond0
3 bond0.5

  but never:

1 eno1
2 bond0.5
3 bond0

  
  As a work arouund, in /etc/network/interfaces

  -auto   eno1 bond0 bond0.1
  +auto   eno1 bond0
  +allow-bond bond0.1

  And also in /lib/systemd/system/networking.service

   ExecStart=/sbin/ifup -a --read-environment
  +ExecStart=/sbin/ifup -a --allow=bond --read-environment
   ExecStop=/sbin/ifdown -a --read-environment

  Then run:

systemctl dameon-reload

  This causes all "auto" interfaces to start then, when they've
  completed, all allow-bond interfaces to start.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ifupdown 0.8.10ubuntu1.1 [modified: 
lib/systemd/system/networking.service]
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Wed Oct 26 06:32:57 2016
  InstallationDate: Installed on 2016-10-24 (1 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: ifupdown
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.init.networking.conf: [modified]
  mtime.conffile..etc.init.networking.conf: 2016-10-26T04:52:05.750927

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

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

[Touch-packages] [Bug 1823425] Re: libdmapsharing ftbfs in disco

This bug was fixed in the package libdmapsharing - 2.9.39-4ubuntu1

---
libdmapsharing (2.9.39-4ubuntu1) disco; urgency=medium

  * debian/patches/new_vala_build.patch:
- changes to fix the build with the new vala version, thanks ricotz!
  (lp: #1823425)

 -- Sebastien Bacher   Mon, 08 Apr 2019 13:51:00
+0200

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

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

Title:
  libdmapsharing ftbfs in disco

Status in libdmapsharing package in Ubuntu:
  Fix Released

Bug description:
  https://launchpadlibrarian.net/417924367/buildlog_ubuntu-disco-
  amd64.libdmapsharing_2.9.39-4_BUILDING.txt.gz

  Making all in tests
  make[3]: Entering directory '/<>/tests'
  /usr/bin/valac --vapidir=../vala --pkg gee-0.8 --pkg gstreamer-1.0 --pkg 
libdmapsharing-3.0 --pkg libsoup-2.4 --pkg gio-2.0 --pkg avahi-gobject  
dacplisten.vala vala-dmap-db.vala vala-dmap-container-db.vala -C
  /usr/bin/valac --vapidir=../vala --pkg gee-0.8 --pkg gtk+-2.0 --pkg 
gstreamer-1.0 --pkg libdmapsharing-3.0 --pkg libsoup-2.4 --pkg gio-2.0 --pkg 
avahi-gobject dpapview.vala vala-dmap-db.vala vala-dpap-record.vala -C
  /usr/bin/valac --vapidir=../vala --pkg gee-0.8 --pkg gstreamer-1.0 --pkg 
libdmapsharing-3.0 --pkg libsoup-2.4 --pkg gio-2.0 --pkg avahi-gobject 
dmapcopy.vala vala-dmap-db.vala vala-dpap-record.vala -C
  /usr/bin/valac --vapidir=../vala --pkg gee-0.8 --pkg gstreamer-1.0 --pkg 
libdmapsharing-3.0 --pkg libsoup-2.4 --pkg gio-2.0 --pkg avahi-gobject 
dmapserve.vala vala-dmap-db.vala vala-dpap-record.vala 
vala-dmap-container-db.vala -C
  vala-dpap-record.vala:120.3-120.42: warning: unhandled error `GLib.FileError'
GLib.FileUtils.get_data (path, out data);

  vala-dmap-db.vala:27.2-27.46: error: Cannot convert from 
`Gee.ArrayList' to `Gee.ArrayList'
private Gee.ArrayList db = new 
Gee.ArrayList ();
^
  vala-dmap-db.vala:30.3-30.8: error: The name `add' does not exist in the 
context of `ValaDMAPDb.db'
db.add (((DMAP.Record) record));
^^
  vala-dmap-db.vala:27.2-27.46: vala-dmap-db.vala:31.10-31.16: error: The name 
`size' does not exist in the context of `ValaDMAPDb.db'
return db.size;
   ^^^
  vala-dmap-db.vala:43.10-43.16: error: The name `size' does not exist in the 
context of `ValaDMAPDb.db'
return db.size;
   ^^^
  vala-dmap-db.vala:48.19-48.25: error: The name `size' does not exist in the 
context of `ValaDMAPDb.db'
for (i = 0; i < db.size; i++) {
^^^
  error: Cannot convert from 
`Gee.ArrayList'vala-dmap-db.vala:58.10-58.15: error: The name 
`get' does not exist in the context of `ValaDMAPDb.db'
return db.get ((int) id - 1);
   ^^
  vala-dmap-container-db.vala:27.2-27.46: error: Cannot convert from 
`Gee.ArrayList' to `Gee.ArrayList'
   to `Gee.ArrayList'
private Gee.ArrayList db = new 
Gee.ArrayList ();
private Gee.ArrayList db = new 
Gee.ArrayList ();
^
  vala-dmap-container-db.vala:30.10-30.16: error: The name `size' does not 
exist in the context of `ValaDMAPContainerDb.db'
return db.size;
   ^^   ^
  ^^^vala-dmap-container-db.vala:35.19-35.25: 
^^
  vala-dmap-db.vala:30.3-30.8: error: The name `add' does not exist in the 
context of `ValaDMAPDb.db'error: The name `size' does not exist in the context 
of `ValaDMAPContainerDb.db'
for (i = 0; i < db.size; i++) {
^^^

db.add (((DMAP.Record) record));
  dmapserve.vala:34.40-34.43:   ^^
  vala-dmap-db.vala:31.10-31.16: error: The name `size' does not exist in the 
context of `ValaDMAPDb.db'
return db.size;
   ^^^
  warning: Argument 2: Cannot pass null to non-null parameter type
  vala-dmap-db.vala:43.10-43.16: error: The nameshare = new 
DPAP.Share ("dmapserve", null, db, container_db, null);
 
  dmapserve.vala:34.64-34.67: warning: Argument 5: Cannot pass null to non-null 
parameter type
share = new DPAP.Share ("dmapserve", null, db, container_db, 
null);
 

  `size' does not exist in the context of 
`ValaDMAPDb.db'dmapserve.vala:57.6-57.32: 
return db.size;
   ^^^
  warning: unhandled error `GLib.Error'
  vala-dmap-db.vala:48.19-48.25:

[Touch-packages] [Bug 1742941] Re: [18.10] zlib: improve crc32 performance on P8

2019-04-08 Thread Manoj Iyer

Looks like this patch is still waiting to be merged upstream, looking at
this link: https://github.com/madler/zlib/pull/335 Could you please
advice if this is being considered to be merged upstream by the
maintainer?

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

Title:
  [18.10] zlib: improve  crc32 performance on P8

Status in The Ubuntu-power-systems project:
  Incomplete
Status in zlib package in Ubuntu:
  New

Bug description:
  Calculate the checksum of data that is 16 byte aligned and a multiple
  of  16 bytes.

  The first step is to reduce it to 1024 bits. We do this in 8 parallel
   chunks in order to mask the latency of the vpmsum instructions. If we
   have more than 32 kB of data to checksum we repeat this step multiple
   times, passing in the previous 1024 bits.

   The next step is to reduce the 1024 bits to 64 bits. This step adds
   32 bits of 0s to the end - this matches what a CRC does. We just
   calculate constants that land the data in this 32 bits.

   We then use fixed point Barrett reduction to compute a mod n over GF(2)
   for n = CRC using POWER8 instructions. We use x = 32.

   http://en.wikipedia.org/wiki/Barrett_reduction

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

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

[Touch-packages] [Bug 1796501] Re: systemd-resolved tries to mitigate DVE-2018-0001 even if DNSSEC=yes

** Tags removed: sts

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

Title:
  systemd-resolved tries to mitigate DVE-2018-0001 even if DNSSEC=yes

Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Cosmic:
  In Progress
Status in systemd source package in Disco:
  In Progress

Bug description:
  I ask systemd-resolved through dig to resolve the SOA of test.asdf. (doesn't 
exist) but it returns SERVFAIL instead of NXDOMAIN. It seems to do the 
following steps:
  1. Ask upstream for SOA of test.asdf. with EDNS0, DO-bit and 4k size.
  2. Ask upstream for SOA of test.asdf. with EDNS0 and DO-bit.
  3. Ask upstream for SOA of test.asdf. with EDNS0.
  4. Ask upstream for SOA of test.asdf. without EDNS0.
  5. Repeat 1-4 for DS of test.asdf.
  6. Repeat 1-5 for asdf.
  7. Ask upstream for SOA of . with EDNS0, DO-bit and 4k size.
  8. Ask upstream for DNSKEY of . with EDNS0, DO-bit and 4k size.

  The upstream returns an unfragmented NXDOMAIN response for steps 1-6,
  an unfragmented NOERROR response for step 7 and a fragmented NOERROR
  response for step 8 which is the correct behaviour. DNSSEC records are
  included in the response if the DO-bit in the request was set.

  systemd-resolved should take the response from step 1 and start with
  validation instead of starting useless retries with reduced feture
  set. Step 3 and 4 are completely useless and probably lead to the
  SERVFAIL because I have configured it with DNSSEC=yes to prevent
  downgrade attacks.

  This regression seems to be caused by the patch resolved-Mitigate-
  DVE-2018-0001-by-retrying-NXDOMAIN-with.patch. The downgrade logic
  should only be executed if it is configured as DNSSEC=allow-downgrade
  or DNSSEC=no. See also
  https://github.com/systemd/systemd/pull/8608#issuecomment-396927885.

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

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

[Touch-packages] [Bug 1759014] Re: Netplan has no way to control DHCP client

2019-04-08 Thread Michael Steffens

Submitted
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1823730.

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

Title:
  Netplan has no way to control DHCP client

Status in netplan:
  Fix Released
Status in netplan.io package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed
Status in netplan.io source package in Bionic:
  Fix Committed
Status in systemd source package in Bionic:
  Confirmed
Status in netplan.io source package in Cosmic:
  Fix Committed
Status in systemd source package in Cosmic:
  Confirmed
Status in netplan.io source package in Disco:
  Fix Released
Status in systemd source package in Disco:
  Confirmed

Bug description:
  [Impact]
  DHCP configurations where custom settings (routes, nameservers, etc.) need to 
be applied.

  [Test case]
  1) Configure netplan for the particulars of the network by configuring an 
appropriate dhcp{4,6}-override stanza:

  network:
version: 2
ethernets:
  engreen:
dhcp4: true
dhcp4-overrides:
  use-dns: false
  use-routes: false
  route-metric: 

  Additionally, if so required, add a custom DNS / routes to the
  configuration. e.g.

nameservers:
  search: [lab, kitchen]
  addresses: [8.8.8.8]

  (See https://netplan.io/reference#dhcp-overrides for the available
  options)

  2) Run 'netplan apply' or reboot to have the configuration applied.
  3) Validate that the routes / DNS are properly ignored and/or replaced by the 
defined values.

  [Regression potential]
  Minimal; this adds new values to the configuration generated for networkd or 
NetworkManager. Existing configurations will remain unchanged, but new 
configurations using the dhcp{4,6}-overrides fields will benefit from 
additional flexibility.

  
  ---

  
  Currently DHCP appears to be an all or nothing boolean, which is insufficient 
for many network configurations.

  Ideally all of the DHCP configuration options supported by systemd would also 
be supported in netplan:
  
https://www.freedesktop.org/software/systemd/man/systemd.network.html#%5BDHCP%5D%20Section%20Options

  As an example, consider the following netplan configuration:

  network:
    version: 2
    renderer: networkd
    ethernets:
  enp0s3:
    dhcp4: yes
    nameservers: [8.8.8.8,8.8.4.4]

  After running netplan apply I check the nameservers with systemd-
  resolve --status and it shows:

  DNS Servers: 8.8.8.8
   8.8.4.4
   192.168.1.1

  Here, "192.168.1.1" was provided by my DHCP server.  On this
  particular node, I only want the manually configured DNS servers, but
  netplan has no way to indicate this.

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

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

[Touch-packages] [Bug 1823730] [NEW] Bionic: interface stuck in state "configuring" on a VM with two NICs, DHCP, and the secondary NIC configured to ignore routes from DHCP

2019-04-08 Thread Michael Steffens

Public bug reported:

[Impact]

Network interfaces not using route information from DHCP4 do not reach
configured state, but remain 'configuring' on Bionic.

[Test Case]

 1) Launch a VM with two network interfaces connected to ports on
distinct network, each configured using DHCP4.

 2) Configure systemd-networkd to set up both interfaces via DHCP, but to 
ignore DHCP route information (plus possibly other system wide configuration 
supposed to be unambiguous, like DNS) from secondary interface. You can do so
* either directly in /etc/systemd/network/, as shown in 
https://github.com/systemd/systemd/issues/9289,
* or via netplan.io 0.96-0ubuntu0.18.04.2, as shown in 
https://bugs.launchpad.net/netplan/+bug/1759014/comments/48.

 3) Reboot.

 4) Both interfaces should now be reported as configured:

# networkctl -a
IDX LINK TYPE   OPERATIONAL SETUP
  1 lo   loopback   carrier unmanaged
  2 ens3 ether  routableconfigured
  3 ens4 ether  routableconfigured

3 links listed.

[Other Info]

The issue is known for systemd releases before 239, and was fixed with
https://github.com/systemd/systemd/commit/223932c786ada7f758a7b7878a6ad2dae0d1e5fb.

I have tested it by manually merging that fix into sources of systemd
237-3ubuntu10.15, rebuilding and installing the package. Worked fine.

See also https://bugs.launchpad.net/netplan/+bug/1759014 and
https://bugs.launchpad.net/netplan/+bug/1776228.

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


** Tags: bionic dhcp4

** Tags added: bionic dhcp4

** Description changed:

  [Impact]
  
  Network interfaces not using route information from DHCP4 do not reach
  configured state, but remain 'configuring' on Bionic.
  
  [Test Case]
  
-  1) Launch a VM with two network interfaces connected to ports on
+  1) Launch a VM with two network interfaces connected to ports on
  distinct network, each configured using DHCP4.
  
-  2) Configure systemd-networkd to set up both interfaces via DHCP, but to 
ignore DHCP route information (plus possibly other system wide configuration 
supposed to be unambiguous, like DNS) from secondary interface. You can do so
- * either directly in /etc/systemd/network/, as shown in 
https://github.com/systemd/systemd/issues/9289,
- * or via netplan.io 0.96-0ubuntu0.18.04.2, as shown in 
https://bugs.launchpad.net/netplan/+bug/1759014/comments/48.
+  2) Configure systemd-networkd to set up both interfaces via DHCP, but to 
ignore DHCP route information (plus possibly other system wide configuration 
supposed to be unambiguous, like DNS) from secondary interface. You can do so
+ * either directly in /etc/systemd/network/, as shown in 
https://github.com/systemd/systemd/issues/9289,
+ * or via netplan.io 0.96-0ubuntu0.18.04.2, as shown in 
https://bugs.launchpad.net/netplan/+bug/1759014/comments/48.
  
-  3) Reboot.
+  3) Reboot.
  
-  4) Both interfaces should now be reported as configured:
+  4) Both interfaces should now be reported as configured:
  
- # networkctl -a
- IDX LINK TYPE   OPERATIONAL SETUP 
-   1 lo   loopback   carrier unmanaged 
-   2 ens3 ether  routableconfigured
-   3 ens4 ether  routableconfigured
+ # networkctl -a
+ IDX LINK TYPE   OPERATIONAL SETUP
+   1 lo   loopback   carrier unmanaged
+   2 ens3 ether  routableconfigured
+   3 ens4 ether  routableconfigured
  
- 3 links listed.
+ 3 links listed.
  
  [Other Info]
  
  The issue is known for systemd releases before 239, and was fixed with
  
https://github.com/systemd/systemd/commit/223932c786ada7f758a7b7878a6ad2dae0d1e5fb.
  
  I have tested it by manually merging that fix into sources of systemd
  237-3ubuntu10.15, rebuilding and installing the package. Worked fine.
  
  See also https://bugs.launchpad.net/netplan/+bug/1759014 and
- https://bugs.launchpad.net/netplan/+bug/1771736.
+ https://bugs.launchpad.net/netplan/+bug/1776228.

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

Title:
  Bionic: interface stuck in state "configuring" on a VM with two NICs,
  DHCP, and the secondary NIC configured to ignore routes from DHCP

Status in systemd package in Ubuntu:
  New

Bug description:
  [Impact]

  Network interfaces not using route information from DHCP4 do not reach
  configured state, but remain 'configuring' on Bionic.

  [Test Case]

   1) Launch a VM with two network interfaces connected to ports on
  distinct network, each configured using DHCP4.

   2) Configure systemd-networkd to set up both

[Touch-packages] [Bug 1823721] Re: systemctl fstrim.timer freeze computer with a SSD on a dual boot system Windows 10/Ubuntu 18.04

2019-04-08 Thread Eliastik

** Description changed:

  The default systemctl fstrim.timer on Ubuntu 18.04 entirely freeze the
  computer once a week (usually on Monday midnight) in the case of a dual
  boot system installed on a SSD (Windows/Ubuntu) due to high IO overhead.
  I also had several freeze at boot due to the same problem.
  
  When the freeze occur I can open a tty terminal and type the command
  iotop to see the process which use that amount of IO. It was mount.ntfs-
  3g which point to my mount point to my Windows 10 install on my SSD.
  
  When the freeze occur the system is not responsive for about 10-15
  minutes.
  
  I solved my issue by disabling the fstrim.timer entirely with this
  command:
  
  sudo systemctl disable fstrim.timer
  
  I can reproduce the problem on my installation by launching the fstrim-
  timer:
  
  sudo systemctl start fstrim.timer
  
  Imediately after launching fstrim.timer, iotop display this line at top,
  with my Windows 10 mount point:
  
    TID  PRIO  USER DISK READ  DISK WRITE  SWAPIN IO>COMMAND
    893 be/4 root0.00 B/s0.00 B/s  0.00 % 99.10 % mount.ntfs-3g 
/dev/sda1 /media/systeme_windows -o 
rw,noatime,noexec,nosuid,nodev,gid=100,uid=1000,nls=utf8,windows_names,umask=002,user
  
  And a few minutes later:
  
-   TID  PRIO  USER DISK READ  DISK WRITE  SWAPIN IO>COMMAND
+   TID  PRIO  USER DISK READ  DISK WRITE  SWAPIN IO>COMMAND
  20077 be/4 root0.00 B/s0.00 B/s  0.00 % 99.45 % fstrim -av
  
  
  Systemd 237-3ubuntu10.19
  Ubuntu 18.04.2
+ Linux 4.18.0-17-generic

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

Title:
  systemctl fstrim.timer freeze computer with a SSD  on a dual boot
  system Windows 10/Ubuntu 18.04

Status in systemd package in Ubuntu:
  New

Bug description:
  The default systemctl fstrim.timer on Ubuntu 18.04 entirely freeze the
  computer once a week (usually on Monday midnight) in the case of a
  dual boot system installed on a SSD (Windows/Ubuntu) due to high IO
  overhead. I also had several freeze at boot due to the same problem.

  When the freeze occur I can open a tty terminal and type the command
  iotop to see the process which use that amount of IO. It was mount
  .ntfs-3g which point to my mount point to my Windows 10 install on my
  SSD.

  When the freeze occur the system is not responsive for about 10-15
  minutes.

  I solved my issue by disabling the fstrim.timer entirely with this
  command:

  sudo systemctl disable fstrim.timer

  I can reproduce the problem on my installation by launching the
  fstrim-timer:

  sudo systemctl start fstrim.timer

  Imediately after launching fstrim.timer, iotop display this line at
  top, with my Windows 10 mount point:

    TID  PRIO  USER DISK READ  DISK WRITE  SWAPIN IO>COMMAND
    893 be/4 root0.00 B/s0.00 B/s  0.00 % 99.10 % mount.ntfs-3g 
/dev/sda1 /media/systeme_windows -o 
rw,noatime,noexec,nosuid,nodev,gid=100,uid=1000,nls=utf8,windows_names,umask=002,user

  And a few minutes later:

    TID  PRIO  USER DISK READ  DISK WRITE  SWAPIN IO>COMMAND
  20077 be/4 root0.00 B/s0.00 B/s  0.00 % 99.45 % fstrim -av

  
  Systemd 237-3ubuntu10.19
  Ubuntu 18.04.2
  Linux 4.18.0-17-generic

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

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

[Touch-packages] [Bug 1823550] Re: GtkSourceView wrongly has monospaced font in dropdown (context) menu

The problem is also exists in Gedit, which is by default themed with Ambiance 
theme from `light-themes` package.
Problem confirmed on Ubuntu session (means GNOME) of Ubuntu 18.04.2 LTS and in 
upcoming 19.04 while running Unity desktop. Here only Adwaita theme looks 
correct.

So all modern GTK themes should be fixed to correctly show drop-down
menu in GtkSourceView.

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

Title:
  GtkSourceView wrongly has monospaced font in dropdown (context) menu

Status in GtkSourceView:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Invalid
Status in gtksourceview3 package in Ubuntu:
  Invalid
Status in mate-themes package in Ubuntu:
  New
Status in pluma package in Ubuntu:
  Invalid
Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 17.04 or later installed
  2. Open any application with GtkSourceView component - such as Pluma, Gedit, 
Giggle, Gitg, gnome-builder and maybe others (see complete list with `apt-cache 
rdepends libgtksourceview-3.0-1`)
  3. Click right mouse button on text zone

  Expected result:
  * dropdown menu has normal font as all other interface elements

  Actual result:
  * dropdwon menu wrongly has monospaced font

  Notes:
  * first seen in 17.04, but persists in 17.10, 18.04 LTS, 18.10, 19.04 
releases.
  * seems to be caused by GTK3 library

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: pluma 1.18.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.10
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sun Apr  7 20:13:24 2019
  InstallationDate: Installed on 2018-08-07 (243 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: pluma
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1823721] Re: systemctl fstrim.timer freeze computer with a SSD on a dual boot system Windows 10/Ubuntu 18.04

2019-04-08 Thread Eliastik

** Summary changed:

- systemctl fstrim.timer freeze computer with an SSD  with dual boot system 
Windows 10/Ubuntu 18.04
+ systemctl fstrim.timer freeze computer with a SSD  on a dual boot system 
Windows 10/Ubuntu 18.04

** Description changed:

  The default systemctl fstrim.timer on Ubuntu 18.04 entirely freeze the
  computer once a week (usually on Monday midnight) in the case of a dual
  boot system installed on a SSD (Windows/Ubuntu) due to high IO overhead.
  I also had several freeze at boot due to the same problem.
  
  When the freeze occur I can open a tty terminal and type the command
  iotop to see the process which use that amount of IO. It was mount.ntfs-
  3g which point to my mount point to my Windows 10 install on my SSD.
  
  When the freeze occur the system is not responsive for about 10-15
  minutes.
  
  I solved my issue by disabling the fstrim.timer entirely with this
  command:
  
  sudo systemctl disable fstrim.timer
  
  I can reproduce the problem on my installation by launching the fstrim-
  timer:
  
  sudo systemctl start fstrim.timer
  
  Imediately after launching fstrim.timer, iotop display this line at top,
  with my Windows 10 mount point:
  
+   TID  PRIO  USER DISK READ  DISK WRITE  SWAPIN IO>COMMAND
+   893 be/4 root0.00 B/s0.00 B/s  0.00 % 99.10 % mount.ntfs-3g 
/dev/sda1 /media/systeme_windows -o 
rw,noatime,noexec,nosuid,nodev,gid=100,uid=1000,nls=utf8,windows_names,umask=002,user
+ 
+ And a few minutes later:
+ 
TID  PRIO  USER DISK READ  DISK WRITE  SWAPIN IO>COMMAND
-   893 be/4 root0.00 B/s0.00 B/s  0.00 % 99.10 % mount.ntfs-3g 
/dev/sda1 /media/systeme_windows -o 
rw,noatime,noexec,nosuid,nodev,gid=100,uid=1000,nls=utf8,windows_names,umask=002,user
+ 20077 be/4 root0.00 B/s0.00 B/s  0.00 % 99.45 % fstrim -av
  
  
  Systemd 237-3ubuntu10.19
  Ubuntu 18.04.2

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

Title:
  systemctl fstrim.timer freeze computer with a SSD  on a dual boot
  system Windows 10/Ubuntu 18.04

Status in systemd package in Ubuntu:
  New

Bug description:
  The default systemctl fstrim.timer on Ubuntu 18.04 entirely freeze the
  computer once a week (usually on Monday midnight) in the case of a
  dual boot system installed on a SSD (Windows/Ubuntu) due to high IO
  overhead. I also had several freeze at boot due to the same problem.

  When the freeze occur I can open a tty terminal and type the command
  iotop to see the process which use that amount of IO. It was mount
  .ntfs-3g which point to my mount point to my Windows 10 install on my
  SSD.

  When the freeze occur the system is not responsive for about 10-15
  minutes.

  I solved my issue by disabling the fstrim.timer entirely with this
  command:

  sudo systemctl disable fstrim.timer

  I can reproduce the problem on my installation by launching the
  fstrim-timer:

  sudo systemctl start fstrim.timer

  Imediately after launching fstrim.timer, iotop display this line at
  top, with my Windows 10 mount point:

    TID  PRIO  USER DISK READ  DISK WRITE  SWAPIN IO>COMMAND
    893 be/4 root0.00 B/s0.00 B/s  0.00 % 99.10 % mount.ntfs-3g 
/dev/sda1 /media/systeme_windows -o 
rw,noatime,noexec,nosuid,nodev,gid=100,uid=1000,nls=utf8,windows_names,umask=002,user

  And a few minutes later:

    TID  PRIO  USER DISK READ  DISK WRITE  SWAPIN IO>COMMAND
  20077 be/4 root0.00 B/s0.00 B/s  0.00 % 99.45 % fstrim -av

  
  Systemd 237-3ubuntu10.19
  Ubuntu 18.04.2
  Linux 4.18.0-17-generic

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

-- 
Mailing list: https://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 1823650] Re: v4l-utils ftbfs in cosmic

On 08.04.19 14:12, Gregor Jasny wrote:
> How could I re-create your setup?

this is cosmic, -release, -updates, -security. No -proposed.

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

Title:
  v4l-utils ftbfs in cosmic

Status in v4l-utils package in Ubuntu:
  New

Bug description:
  https://launchpadlibrarian.net/418304769/buildlog_ubuntu-cosmic-amd64
  .v4l-utils_1.14.2-1_BUILDING.txt.gz

  g++  -I. -I../..  -I../../utils/common -I../../lib/include -Wall 
-Wpointer-arith -D_GNU_SOURCE -I../../include -Wdate-time -D_FORTIFY_SOURCE=2  
-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o v4l2_compliance-v4l2-compliance.o `test -f 
'v4l2-compliance.cpp' || echo './'`v4l2-compliance.cpp
  In file included from v4l2-compliance.h:42,
   from v4l2-compliance.cpp:38:
  ../../utils/common/cv4l-helpers.h: In member function ‘void 
cv4l_buffer::init(const cv4l_buffer&)’:
  ../../utils/common/cv4l-helpers.h:843:29: warning: ‘void* memcpy(void*, const 
void*, size_t)’ writing to an object of type ‘class cv4l_buffer’ with no 
trivial copy-assignment; use copy-assignment or copy-initialization instead 
[-Wclass-memaccess]
 memcpy(this, , sizeof(b));
   ^
  ../../utils/common/cv4l-helpers.h:817:7: note: ‘class cv4l_buffer’ declared 
here
   class cv4l_buffer : public v4l_buffer {
 ^~~
  g++  -I. -I../..  -I../../utils/common -I../../lib/include -Wall 
-Wpointer-arith -D_GNU_SOURCE -I../../include -Wdate-time -D_FORTIFY_SOURCE=2  
-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o v4l2_compliance-v4l2-test-debug.o `test -f 
'v4l2-test-debug.cpp' || echo './'`v4l2-test-debug.cpp
  In file included from v4l2-compliance.h:42,
   from v4l2-test-debug.cpp:35:
  ../../utils/common/cv4l-helpers.h: In member function ‘void 
cv4l_buffer::init(const cv4l_buffer&)’:
  ../../utils/common/cv4l-helpers.h:843:29: warning: ‘void* memcpy(void*, const 
void*, size_t)’ writing to an object of type ‘class cv4l_buffer’ with no 
trivial copy-assignment; use copy-assignment or copy-initialization instead 
[-Wclass-memaccess]
 memcpy(this, , sizeof(b));
   ^
  ../../utils/common/cv4l-helpers.h:817:7: note: ‘class cv4l_buffer’ declared 
here
   class cv4l_buffer : public v4l_buffer {
 ^~~
  g++  -I. -I../..  -I../../utils/common -I../../lib/include -Wall 
-Wpointer-arith -D_GNU_SOURCE -I../../include -Wdate-time -D_FORTIFY_SOURCE=2  
-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o v4l2_compliance-v4l2-test-input-output.o `test -f 
'v4l2-test-input-output.cpp' || echo './'`v4l2-test-input-output.cpp
  In file included from v4l2-compliance.h:42,
   from v4l2-test-input-output.cpp:32:
  ../../utils/common/cv4l-helpers.h: In member function ‘void 
cv4l_buffer::init(const cv4l_buffer&)’:
  ../../utils/common/cv4l-helpers.h:843:29: warning: ‘void* memcpy(void*, const 
void*, size_t)’ writing to an object of type ‘class cv4l_buffer’ with no 
trivial copy-assignment; use copy-assignment or copy-initialization instead 
[-Wclass-memaccess]
 memcpy(this, , sizeof(b));
   ^
  ../../utils/common/cv4l-helpers.h:817:7: note: ‘class cv4l_buffer’ declared 
here
   class cv4l_buffer : public v4l_buffer {
 ^~~
  g++  -I. -I../..  -I../../utils/common -I../../lib/include -Wall 
-Wpointer-arith -D_GNU_SOURCE -I../../include -Wdate-time -D_FORTIFY_SOURCE=2  
-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o v4l2_compliance-v4l2-test-controls.o `test -f 
'v4l2-test-controls.cpp' || echo './'`v4l2-test-controls.cpp
  In file included from v4l2-compliance.h:42,
   from v4l2-test-controls.cpp:33:
  ../../utils/common/cv4l-helpers.h: In member function ‘void 
cv4l_buffer::init(const cv4l_buffer&)’:
  ../../utils/common/cv4l-helpers.h:843:29: warning: ‘void* memcpy(void*, const 
void*, size_t)’ writing to an object of type ‘class cv4l_buffer’ with no 
trivial copy-assignment; use copy-assignment or copy-initialization instead 
[-Wclass-memaccess]
 memcpy(this, , sizeof(b));
   ^
  ../../utils/common/cv4l-helpers.h:817:7: note: ‘class cv4l_buffer’ declared 
here
   class cv4l_buffer : public v4l_buffer {
 ^~~
  g++  -I. -I../..  -I../../utils/common -I../../lib/include -Wall 
-Wpointer-arith -D_GNU_SOURCE -I../../include -Wdate-time -D_FORTIFY_SOURCE=2  
-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o v4l2_compliance-v4l2-test-io-config.o `test -f 
'v4l2-test-io-config.cpp' || echo './'`v4l2-test-io-config.cpp
  In file included from v4l2-compliance.h:42,

[Touch-packages] [Bug 1823425] Re: libdmapsharing ftbfs in disco

** Changed in: libdmapsharing (Ubuntu)
   Status: New => Fix Committed

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

Title:
  libdmapsharing ftbfs in disco

Status in libdmapsharing package in Ubuntu:
  Fix Committed

Bug description:
  https://launchpadlibrarian.net/417924367/buildlog_ubuntu-disco-
  amd64.libdmapsharing_2.9.39-4_BUILDING.txt.gz

  Making all in tests
  make[3]: Entering directory '/<>/tests'
  /usr/bin/valac --vapidir=../vala --pkg gee-0.8 --pkg gstreamer-1.0 --pkg 
libdmapsharing-3.0 --pkg libsoup-2.4 --pkg gio-2.0 --pkg avahi-gobject  
dacplisten.vala vala-dmap-db.vala vala-dmap-container-db.vala -C
  /usr/bin/valac --vapidir=../vala --pkg gee-0.8 --pkg gtk+-2.0 --pkg 
gstreamer-1.0 --pkg libdmapsharing-3.0 --pkg libsoup-2.4 --pkg gio-2.0 --pkg 
avahi-gobject dpapview.vala vala-dmap-db.vala vala-dpap-record.vala -C
  /usr/bin/valac --vapidir=../vala --pkg gee-0.8 --pkg gstreamer-1.0 --pkg 
libdmapsharing-3.0 --pkg libsoup-2.4 --pkg gio-2.0 --pkg avahi-gobject 
dmapcopy.vala vala-dmap-db.vala vala-dpap-record.vala -C
  /usr/bin/valac --vapidir=../vala --pkg gee-0.8 --pkg gstreamer-1.0 --pkg 
libdmapsharing-3.0 --pkg libsoup-2.4 --pkg gio-2.0 --pkg avahi-gobject 
dmapserve.vala vala-dmap-db.vala vala-dpap-record.vala 
vala-dmap-container-db.vala -C
  vala-dpap-record.vala:120.3-120.42: warning: unhandled error `GLib.FileError'
GLib.FileUtils.get_data (path, out data);

  vala-dmap-db.vala:27.2-27.46: error: Cannot convert from 
`Gee.ArrayList' to `Gee.ArrayList'
private Gee.ArrayList db = new 
Gee.ArrayList ();
^
  vala-dmap-db.vala:30.3-30.8: error: The name `add' does not exist in the 
context of `ValaDMAPDb.db'
db.add (((DMAP.Record) record));
^^
  vala-dmap-db.vala:27.2-27.46: vala-dmap-db.vala:31.10-31.16: error: The name 
`size' does not exist in the context of `ValaDMAPDb.db'
return db.size;
   ^^^
  vala-dmap-db.vala:43.10-43.16: error: The name `size' does not exist in the 
context of `ValaDMAPDb.db'
return db.size;
   ^^^
  vala-dmap-db.vala:48.19-48.25: error: The name `size' does not exist in the 
context of `ValaDMAPDb.db'
for (i = 0; i < db.size; i++) {
^^^
  error: Cannot convert from 
`Gee.ArrayList'vala-dmap-db.vala:58.10-58.15: error: The name 
`get' does not exist in the context of `ValaDMAPDb.db'
return db.get ((int) id - 1);
   ^^
  vala-dmap-container-db.vala:27.2-27.46: error: Cannot convert from 
`Gee.ArrayList' to `Gee.ArrayList'
   to `Gee.ArrayList'
private Gee.ArrayList db = new 
Gee.ArrayList ();
private Gee.ArrayList db = new 
Gee.ArrayList ();
^
  vala-dmap-container-db.vala:30.10-30.16: error: The name `size' does not 
exist in the context of `ValaDMAPContainerDb.db'
return db.size;
   ^^   ^
  ^^^vala-dmap-container-db.vala:35.19-35.25: 
^^
  vala-dmap-db.vala:30.3-30.8: error: The name `add' does not exist in the 
context of `ValaDMAPDb.db'error: The name `size' does not exist in the context 
of `ValaDMAPContainerDb.db'
for (i = 0; i < db.size; i++) {
^^^

db.add (((DMAP.Record) record));
  dmapserve.vala:34.40-34.43:   ^^
  vala-dmap-db.vala:31.10-31.16: error: The name `size' does not exist in the 
context of `ValaDMAPDb.db'
return db.size;
   ^^^
  warning: Argument 2: Cannot pass null to non-null parameter type
  vala-dmap-db.vala:43.10-43.16: error: The nameshare = new 
DPAP.Share ("dmapserve", null, db, container_db, null);
 
  dmapserve.vala:34.64-34.67: warning: Argument 5: Cannot pass null to non-null 
parameter type
share = new DPAP.Share ("dmapserve", null, db, container_db, 
null);
 

  `size' does not exist in the context of 
`ValaDMAPDb.db'dmapserve.vala:57.6-57.32: 
return db.size;
   ^^^
  warning: unhandled error `GLib.Error'
  vala-dmap-db.vala:48.19-48.25: error: The name `size' does not exist in the 
context of `ValaDMAPDb.db'
for (i = 0; i < db.size; i++) {
^^^
var dmapcopy = new DPAPServe ();
^^^vala-dmap-db.vala:58.10-58.15: error: The name `get' does not 
exist in the context of `ValaDMAPDb.db'

[Touch-packages] [Bug 1823423] Re: ibus ftbfs in disco

Thanks Mitsuya, I've sponsored the upload of your fix to disco

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

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

Title:
  ibus ftbfs in disco

Status in ibus package in Ubuntu:
  Fix Committed

Bug description:
  https://launchpadlibrarian.net/417924597/buildlog_ubuntu-disco-
  amd64.ibus_1.5.19-1ubuntu1_BUILDING.txt.gz

  multiple vala/glib errors

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

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

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

2019-04-08 Thread Alex Fedorov

Apparently, same bug for Audacious media player: https://redmine
.audacious-media-player.org/issues/798 .

Also, Freecad users have encountered the similar error and managed to
bypass is by setting LIBGL_DRI3_DISABLE environment variable to true
before running Freecad:
https://bugs.launchpad.net/ubuntu/+source/freecad/+bug/1754084/comments/13

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

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

Title:
  !xcb_xlib_threads_sequence_lost error with GTK2 applications

Status in gtk+2.0 package in Ubuntu:
  Confirmed

Bug description:
  GTK2 applications randomly crash or freeze with same error. See
  attached files.

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

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

[Touch-packages] [Bug 1823721] [NEW] systemctl fstrim.timer freeze computer with an SSD with dual boot system Windows 10/Ubuntu 18.04

2019-04-08 Thread Eliastik

Public bug reported:

The default systemctl fstrim.timer on Ubuntu 18.04 entirely freeze the
computer once a week (usually on Monday midnight) in the case of a dual
boot system installed on a SSD (Windows/Ubuntu) due to high IO overhead.
I also had several freeze at boot due to the same problem.

When the freeze occur I can open a tty terminal and type the command
iotop to see the process which use that amount of IO. It was mount.ntfs-
3g which point to my mount point to my Windows 10 install on my SSD.

When the freeze occur the system is not responsive for about 10-15
minutes.

I solved my issue by disabling the fstrim.timer entirely with this
command:

sudo systemctl disable fstrim.timer

I can reproduce the problem on my installation by launching the fstrim-
timer:

sudo systemctl start fstrim.timer

Imediately after launching fstrim.timer, iotop display this line at top,
with my Windows 10 mount point:

  TID  PRIO  USER DISK READ  DISK WRITE  SWAPIN IO>COMMAND
  893 be/4 root0.00 B/s0.00 B/s  0.00 % 99.10 % mount.ntfs-3g 
/dev/sda1 /media/systeme_windows -o 
rw,noatime,noexec,nosuid,nodev,gid=100,uid=1000,nls=utf8,windows_names,umask=002,user


Systemd 237-3ubuntu10.19
Ubuntu 18.04.2

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

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

Title:
  systemctl fstrim.timer freeze computer with an SSD  with dual boot
  system Windows 10/Ubuntu 18.04

Status in systemd package in Ubuntu:
  New

Bug description:
  The default systemctl fstrim.timer on Ubuntu 18.04 entirely freeze the
  computer once a week (usually on Monday midnight) in the case of a
  dual boot system installed on a SSD (Windows/Ubuntu) due to high IO
  overhead. I also had several freeze at boot due to the same problem.

  When the freeze occur I can open a tty terminal and type the command
  iotop to see the process which use that amount of IO. It was mount
  .ntfs-3g which point to my mount point to my Windows 10 install on my
  SSD.

  When the freeze occur the system is not responsive for about 10-15
  minutes.

  I solved my issue by disabling the fstrim.timer entirely with this
  command:

  sudo systemctl disable fstrim.timer

  I can reproduce the problem on my installation by launching the
  fstrim-timer:

  sudo systemctl start fstrim.timer

  Imediately after launching fstrim.timer, iotop display this line at
  top, with my Windows 10 mount point:

TID  PRIO  USER DISK READ  DISK WRITE  SWAPIN IO>COMMAND
893 be/4 root0.00 B/s0.00 B/s  0.00 % 99.10 % mount.ntfs-3g 
/dev/sda1 /media/systeme_windows -o 
rw,noatime,noexec,nosuid,nodev,gid=100,uid=1000,nls=utf8,windows_names,umask=002,user

  
  Systemd 237-3ubuntu10.19
  Ubuntu 18.04.2

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

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

[Touch-packages] [Bug 1823474] Re: package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2019-04-08 Thread Christian Ehrhardt 

I have seen such errors related to OpenVZ 6 - you can take a look at bug
1814124 and bug 1811580 for that if it applies to you.

If that is true check for the workarounds in those buge for a short term 
resolution, long term you should ask your provider to update your hosting 
environment.
If your case is this one please mark this bug here as a dup of it as well.


If the above does not apply please outline your environment in detail as 
reproducing this locally for me neither triggers in containers nor in VMs.

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

** Tags added: server-triage-discuss

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

Title:
  package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  frequently fails; 
  Devon:~$ systemctl status ssh
  * ssh.service - OpenBSD Secure Shell server
 Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: 
enabled)
 Active: failed (Result: start-limit-hit) since Sa 2019-04-06 17:42:35 
CEST; 5min ago
Process: 15706 ExecStartPre=/usr/sbin/sshd -t (code=exited, status=255)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: openssh-server 1:7.2p2-4ubuntu2.8
  ProcVersionSignature: Ubuntu 4.15.0-46.49~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Sat Apr  6 11:17:53 2019
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2018-12-08 (119 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.5
   apt  1.2.31
  SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 
255: Missing privilege separation directory: /var/run/sshd
  SourcePackage: openssh
  Title: package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1814124] Re: sshd does not start after update on non-Ubuntu kernels where fchownat() is broken

2019-04-08 Thread Christian Ehrhardt 

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

Same discussion and more in bug 1811580 marking as dup to have people
finding this bug all get to the same main bug.

** This bug has been marked a duplicate of bug 1811580
   systemd fails to start sshd at reboot

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

Title:
  sshd does not start after update on non-Ubuntu kernels where
  fchownat() is broken

Status in openssh package in Ubuntu:
  Invalid

Bug description:
  [Triage Notes]

  This issue is caused on Ubuntu derivatives due to problematic symlink
  handling on those systems. See bug 1804847 for details, and comment 10
  below for details and a workaround.

  Proper Ubuntu systems do not appear to be affected.

  [Original Description]

  After processing system update by:
  apt-get clean && apt-get autoclean && apt-get autoremove && apt-get update && 
apt-get upgrade && apt-get dist-upgrade && reboot

  ssh server stops starting at system boot.

  It starts after doing:
  mkdir /var/run/sshd
  chmod 0755 /var/run/sshd
  service ssh start

  It happens on fresh Ubuntu-16.04 installs on every VPS provide I have
  tested so far.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: openssh-server 1:7.2p2-4ubuntu2.6
  Uname: Linux 2.6.32-042stab127.2 x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Thu Jan 31 10:18:56 2019
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
  SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 
255: Missing privilege separation directory: /var/run/sshd
  SourcePackage: openssh
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1794629] Re: CVE-2018-15473 - User enumeration vulnerability

2019-04-08 Thread Vital Koshalew

@Seth Arnold,

Qualys automated vulnerability scanner is not supposed to do any
penetration testing, including vulnerability exploitation attempts as it
is ran unattended so must not create any risks of DoS. Trying to exploit
some vulnerabilities can jeopardize production systems. This way, such
non-intrusive scans are by definition limited to sending completely
legitimate requests, checking the responses and then analyzing them
based on a vulnerability database.

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

Title:
  CVE-2018-15473 - User enumeration vulnerability

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

Bug description:
  https://nvd.nist.gov/vuln/detail/CVE-2018-15473

  OpenSSH through 7.7 is prone to a user enumeration vulnerability due
  to not delaying bailout for an invalid authenticating user until after
  the packet containing the request has been fully parsed, related to
  auth2-gss.c, auth2-hostbased.c, and auth2-pubkey.c.

  Fixed in Debian: https://www.debian.org/security/2018/dsa-4280

  Currently pending triage? https://people.canonical.com/~ubuntu-
  security/cve/2018/CVE-2018-15473.html

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

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

[Touch-packages] [Bug 1823667] Re: SRU: pcre3 ftbfs with cosmic toolchain updates

** Summary changed:

- pcre3 ftbfs with cosmic toolchain updates
+ SRU: pcre3 ftbfs with cosmic toolchain updates

** Description changed:

+ Fix the symbols file error by backporting the disco upload, marking more
+ symbols as optional.
+ 
+ Test case: the package builds, in current 18.10, and with the planned 
toolchain updates in ppa:ubuntu-toolchain-r/ppa.
+ Regression potential: Should be the same as for every no-change rebuild.
+ 
  https://launchpadlibrarian.net/418304485/buildlog_ubuntu-cosmic-
  amd64.pcre3_2%3A8.39-11_BUILDING.txt.gz
  
  dh_makeshlibs -plibpcre3 --add-udeb="libpcre3-udeb" -V 'libpcre3 (>= 1:8.35)' 
-- -c4
  dh_makeshlibs -plibpcrecpp0v5 -V 'libpcrecpp0v5 (>= 7.7)' -- -c4
  dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols 
file: see diff output below
  dpkg-gensymbols: warning: debian/libpcrecpp0v5/DEBIAN/symbols doesn't match 
completely debian/libpcrecpp0v5.symbols
  --- debian/libpcrecpp0v5.symbols (libpcrecpp0v5_2:8.39-11_amd64)
  +++ dpkg-gensymbolsc5z0KV 2019-04-08 00:54:17.137602850 +
  @@ -80,9 +80,9 @@
-   (c++)"pcrecpp::Scanner::SetSkipExpression(char const*)@Base" 7.7
-   (c++)"pcrecpp::Scanner::Skip(char const*)@Base" 7.7
-   (c++)"pcrecpp::Scanner::~Scanner()@Base" 7.7
+   (c++)"pcrecpp::Scanner::SetSkipExpression(char const*)@Base" 7.7
+   (c++)"pcrecpp::Scanner::Skip(char const*)@Base" 7.7
+   (c++)"pcrecpp::Scanner::~Scanner()@Base" 7.7
  -#MISSING: 2:8.39-9# (c++|optional=STL)"std::vector 
>::_M_insert_aux(__gnu_cxx::__normal_iterator > >, 
pcrecpp::StringPiece const&)@Base" 7.7
  +#MISSING: 2:8.39-11# (c++|optional=STL)"std::vector 
>::_M_insert_aux(__gnu_cxx::__normal_iterator > >, 
pcrecpp::StringPiece const&)@Base" 7.7
-   (c++|optional=STL)"void std::__cxx11::basic_string, std::allocator >::_M_construct(char 
const*, char const*, std::forward_iterator_tag)@Base" 2:8.39-10
+   (c++|optional=STL)"void std::__cxx11::basic_string, std::allocator >::_M_construct(char 
const*, char const*, std::forward_iterator_tag)@Base" 2:8.39-10
  -#MISSING: 2:8.39-9# (c++|optional=STL)"void 
std::vector 
>::_M_emplace_back_aux(pcrecpp::StringPiece&&)@Base" 
2:8.39-2
  +#MISSING: 2:8.39-11# (c++|optional=STL)"void 
std::vector 
>::_M_emplace_back_aux(pcrecpp::StringPiece&&)@Base" 
2:8.39-2
-   (c++|optional=STL)"void std::vector >::_M_realloc_insert(__gnu_cxx::__normal_iterator > >, 
pcrecpp::StringPiece const&)@Base" 2:8.39-4
-   (c++|optional=STL)"void std::vector 
>::_M_realloc_insert(__gnu_cxx::__normal_iterator > >, 
pcrecpp::StringPiece&&)@Base" 2:8.39-9
+   (c++|optional=STL)"void std::vector >::_M_realloc_insert(__gnu_cxx::__normal_iterator > >, 
pcrecpp::StringPiece const&)@Base" 2:8.39-4
+   (c++|optional=STL)"void std::vector 
>::_M_realloc_insert(__gnu_cxx::__normal_iterator > >, 
pcrecpp::StringPiece&&)@Base" 2:8.39-9
  - (c++)"void std::vector 
>::emplace_back(pcrecpp::StringPiece&&)@Base" 2:8.39-10
  +#MISSING: 2:8.39-11# (c++)"void std::vector 
>::emplace_back(pcrecpp::StringPiece&&)@Base" 2:8.39-10
  dh_makeshlibs: failing due to earlier errors
  make: *** [debian/rules:116: binary-arch] Error 2
  dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned 
exit status 2
  

  Build finished at 20190408-0054

** Changed in: pcre3 (Ubuntu)
   Status: New => In Progress

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

Title:
  SRU: pcre3 ftbfs with cosmic toolchain updates

Status in pcre3 package in Ubuntu:
  In Progress

Bug description:
  Fix the symbols file error by backporting the disco upload, marking
  more symbols as optional.

  Test case: the package builds, in current 18.10, and with the planned 
toolchain updates in ppa:ubuntu-toolchain-r/ppa.
  Regression potential: Should be the same as for every no-change rebuild.

  https://launchpadlibrarian.net/418304485/buildlog_ubuntu-cosmic-
  amd64.pcre3_2%3A8.39-11_BUILDING.txt.gz

  dh_makeshlibs -plibpcre3 --add-udeb="libpcre3-udeb" -V 'libpcre3 (>= 1:8.35)' 
-- -c4
  dh_makeshlibs -plibpcrecpp0v5 -V 'libpcrecpp0v5 (>= 7.7)' -- -c4
  dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols 
file: see diff output below
  dpkg-gensymbols: warning: debian/libpcrecpp0v5/DEBIAN/symbols doesn't match 
completely debian/libpcrecpp0v5.symbols
  --- debian/libpcrecpp0v5.symbols (libpcrecpp0v5_2:8.39-11_amd64)
  +++ dpkg-gensymbolsc5z0KV 2019-04-08 00:54:17.137602850 +
  @@ -80

[Touch-packages] [Bug 1718373] Re: FTBFS on s390x on ubuntu

now closing, builds in recent releases

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

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

Title:
  FTBFS on s390x on ubuntu

Status in pcre3 package in Ubuntu:
  Fix Released

Bug description:
  FTBFS on s390x on ubuntu

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

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

[Touch-packages] [Bug 1823433] Re: pcre3 ftbfs in disco

now builds in disco

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

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

Title:
  pcre3 ftbfs in disco

Status in pcre3 package in Ubuntu:
  Fix Released

Bug description:
  https://launchpadlibrarian.net/417924474/buildlog_ubuntu-disco-
  amd64.pcre3_2%3A8.39-11_BUILDING.txt.gz

  dh_makeshlibs -plibpcrecpp0v5 -V 'libpcrecpp0v5 (>= 7.7)' -- -c4
  dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols 
file: see diff output below
  dpkg-gensymbols: warning: debian/libpcrecpp0v5/DEBIAN/symbols doesn't match 
completely debian/libpcrecpp0v5.symbols
  --- debian/libpcrecpp0v5.symbols (libpcrecpp0v5_2:8.39-11_amd64)
  +++ dpkg-gensymbolsEKHP_Q 2019-04-06 01:28:56.598135324 +
  @@ -80,9 +80,9 @@
(c++)"pcrecpp::Scanner::SetSkipExpression(char const*)@Base" 7.7
(c++)"pcrecpp::Scanner::Skip(char const*)@Base" 7.7
(c++)"pcrecpp::Scanner::~Scanner()@Base" 7.7
  -#MISSING: 2:8.39-9# (c++|optional=STL)"std::vector 
>::_M_insert_aux(__gnu_cxx::__normal_iterator > >, 
pcrecpp::StringPiece const&)@Base" 7.7
  +#MISSING: 2:8.39-11# (c++|optional=STL)"std::vector 
>::_M_insert_aux(__gnu_cxx::__normal_iterator > >, 
pcrecpp::StringPiece const&)@Base" 7.7
(c++|optional=STL)"void std::__cxx11::basic_string, std::allocator >::_M_construct(char 
const*, char const*, std::forward_iterator_tag)@Base" 2:8.39-10
  -#MISSING: 2:8.39-9# (c++|optional=STL)"void 
std::vector 
>::_M_emplace_back_aux(pcrecpp::StringPiece&&)@Base" 
2:8.39-2
  +#MISSING: 2:8.39-11# (c++|optional=STL)"void 
std::vector 
>::_M_emplace_back_aux(pcrecpp::StringPiece&&)@Base" 
2:8.39-2
(c++|optional=STL)"void std::vector >::_M_realloc_insert(__gnu_cxx::__normal_iterator > >, 
pcrecpp::StringPiece const&)@Base" 2:8.39-4
(c++|optional=STL)"void std::vector 
>::_M_realloc_insert(__gnu_cxx::__normal_iterator > >, 
pcrecpp::StringPiece&&)@Base" 2:8.39-9
  - (c++)"void std::vector 
>::emplace_back(pcrecpp::StringPiece&&)@Base" 2:8.39-10
  +#MISSING: 2:8.39-11# (c++)"void std::vector 
>::emplace_back(pcrecpp::StringPiece&&)@Base" 2:8.39-10
  dh_makeshlibs: failing due to earlier errors
  make: *** [debian/rules:116: binary-arch] Error 2

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

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

[Touch-packages] [Bug 1823550] Re: GtkSourceView wrongly has monospaced font in dropdown (context) menu

** Also affects: ubuntu-themes (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  GtkSourceView wrongly has monospaced font in dropdown (context) menu

Status in GtkSourceView:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Invalid
Status in gtksourceview3 package in Ubuntu:
  Invalid
Status in mate-themes package in Ubuntu:
  New
Status in pluma package in Ubuntu:
  Invalid
Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 17.04 or later installed
  2. Open any application with GtkSourceView component - such as Pluma, Gedit, 
Giggle, Gitg, gnome-builder and maybe others (see complete list with `apt-cache 
rdepends libgtksourceview-3.0-1`)
  3. Click right mouse button on text zone

  Expected result:
  * dropdown menu has normal font as all other interface elements

  Actual result:
  * dropdwon menu wrongly has monospaced font

  Notes:
  * first seen in 17.04, but persists in 17.10, 18.04 LTS, 18.10, 19.04 
releases.
  * seems to be caused by GTK3 library

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: pluma 1.18.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.10
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sun Apr  7 20:13:24 2019
  InstallationDate: Installed on 2018-08-07 (243 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: pluma
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1794629] Re: CVE-2018-15473 - User enumeration vulnerability

2019-04-08 Thread Vital Koshalew

@root (mysky),

You don't need any scripts. Referring to a vendor's documentation
(https://usn.ubuntu.com/3809-1/ in this case) is usually enough.

See also:
https://pci.qualys.com/static/help/merchant/false_positives/submit_false_positive_requests.htm

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

Title:
  CVE-2018-15473 - User enumeration vulnerability

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

Bug description:
  https://nvd.nist.gov/vuln/detail/CVE-2018-15473

  OpenSSH through 7.7 is prone to a user enumeration vulnerability due
  to not delaying bailout for an invalid authenticating user until after
  the packet containing the request has been fully parsed, related to
  auth2-gss.c, auth2-hostbased.c, and auth2-pubkey.c.

  Fixed in Debian: https://www.debian.org/security/2018/dsa-4280

  Currently pending triage? https://people.canonical.com/~ubuntu-
  security/cve/2018/CVE-2018-15473.html

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

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

[Touch-packages] [Bug 1823650] Re: v4l-utils ftbfs in cosmic

2019-04-08 Thread Gregor Jasny

Hello,

maybe the following commit from the stable-1.14 branch fixes it:
https://git.linuxtv.org/v4l-
utils.git/commit/?h=stable-1.14=65b6f255a02de403621e478aac701e3ee56806a4

How could I re-create your setup?

Thanks,
-Gregor

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

Title:
  v4l-utils ftbfs in cosmic

Status in v4l-utils package in Ubuntu:
  New

Bug description:
  https://launchpadlibrarian.net/418304769/buildlog_ubuntu-cosmic-amd64
  .v4l-utils_1.14.2-1_BUILDING.txt.gz

  g++  -I. -I../..  -I../../utils/common -I../../lib/include -Wall 
-Wpointer-arith -D_GNU_SOURCE -I../../include -Wdate-time -D_FORTIFY_SOURCE=2  
-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o v4l2_compliance-v4l2-compliance.o `test -f 
'v4l2-compliance.cpp' || echo './'`v4l2-compliance.cpp
  In file included from v4l2-compliance.h:42,
   from v4l2-compliance.cpp:38:
  ../../utils/common/cv4l-helpers.h: In member function ‘void 
cv4l_buffer::init(const cv4l_buffer&)’:
  ../../utils/common/cv4l-helpers.h:843:29: warning: ‘void* memcpy(void*, const 
void*, size_t)’ writing to an object of type ‘class cv4l_buffer’ with no 
trivial copy-assignment; use copy-assignment or copy-initialization instead 
[-Wclass-memaccess]
 memcpy(this, , sizeof(b));
   ^
  ../../utils/common/cv4l-helpers.h:817:7: note: ‘class cv4l_buffer’ declared 
here
   class cv4l_buffer : public v4l_buffer {
 ^~~
  g++  -I. -I../..  -I../../utils/common -I../../lib/include -Wall 
-Wpointer-arith -D_GNU_SOURCE -I../../include -Wdate-time -D_FORTIFY_SOURCE=2  
-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o v4l2_compliance-v4l2-test-debug.o `test -f 
'v4l2-test-debug.cpp' || echo './'`v4l2-test-debug.cpp
  In file included from v4l2-compliance.h:42,
   from v4l2-test-debug.cpp:35:
  ../../utils/common/cv4l-helpers.h: In member function ‘void 
cv4l_buffer::init(const cv4l_buffer&)’:
  ../../utils/common/cv4l-helpers.h:843:29: warning: ‘void* memcpy(void*, const 
void*, size_t)’ writing to an object of type ‘class cv4l_buffer’ with no 
trivial copy-assignment; use copy-assignment or copy-initialization instead 
[-Wclass-memaccess]
 memcpy(this, , sizeof(b));
   ^
  ../../utils/common/cv4l-helpers.h:817:7: note: ‘class cv4l_buffer’ declared 
here
   class cv4l_buffer : public v4l_buffer {
 ^~~
  g++  -I. -I../..  -I../../utils/common -I../../lib/include -Wall 
-Wpointer-arith -D_GNU_SOURCE -I../../include -Wdate-time -D_FORTIFY_SOURCE=2  
-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o v4l2_compliance-v4l2-test-input-output.o `test -f 
'v4l2-test-input-output.cpp' || echo './'`v4l2-test-input-output.cpp
  In file included from v4l2-compliance.h:42,
   from v4l2-test-input-output.cpp:32:
  ../../utils/common/cv4l-helpers.h: In member function ‘void 
cv4l_buffer::init(const cv4l_buffer&)’:
  ../../utils/common/cv4l-helpers.h:843:29: warning: ‘void* memcpy(void*, const 
void*, size_t)’ writing to an object of type ‘class cv4l_buffer’ with no 
trivial copy-assignment; use copy-assignment or copy-initialization instead 
[-Wclass-memaccess]
 memcpy(this, , sizeof(b));
   ^
  ../../utils/common/cv4l-helpers.h:817:7: note: ‘class cv4l_buffer’ declared 
here
   class cv4l_buffer : public v4l_buffer {
 ^~~
  g++  -I. -I../..  -I../../utils/common -I../../lib/include -Wall 
-Wpointer-arith -D_GNU_SOURCE -I../../include -Wdate-time -D_FORTIFY_SOURCE=2  
-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o v4l2_compliance-v4l2-test-controls.o `test -f 
'v4l2-test-controls.cpp' || echo './'`v4l2-test-controls.cpp
  In file included from v4l2-compliance.h:42,
   from v4l2-test-controls.cpp:33:
  ../../utils/common/cv4l-helpers.h: In member function ‘void 
cv4l_buffer::init(const cv4l_buffer&)’:
  ../../utils/common/cv4l-helpers.h:843:29: warning: ‘void* memcpy(void*, const 
void*, size_t)’ writing to an object of type ‘class cv4l_buffer’ with no 
trivial copy-assignment; use copy-assignment or copy-initialization instead 
[-Wclass-memaccess]
 memcpy(this, , sizeof(b));
   ^
  ../../utils/common/cv4l-helpers.h:817:7: note: ‘class cv4l_buffer’ declared 
here
   class cv4l_buffer : public v4l_buffer {
 ^~~
  g++  -I. -I../..  -I../../utils/common -I../../lib/include -Wall 
-Wpointer-arith -D_GNU_SOURCE -I../../include -Wdate-time -D_FORTIFY_SOURCE=2  
-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o v4l2_compliance-v4l2-test-io-config.o `test -f

[Touch-packages] [Bug 1821863] Re: Need to add Intel CML related pci-id's

2019-04-08 Thread Timo Aaltonen

** Changed in: linux-oem (Ubuntu Bionic)
   Status: New => Fix Committed

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

Title:
  Need to add Intel CML related pci-id's

Status in libdrm package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem package in Ubuntu:
  Fix Committed
Status in mesa package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Fix Released
Status in libdrm source package in Bionic:
  New
Status in linux source package in Bionic:
  Invalid
Status in linux-oem source package in Bionic:
  Fix Committed
Status in mesa source package in Bionic:
  New
Status in xorg-server source package in Bionic:
  New
Status in libdrm source package in Disco:
  Fix Released
Status in linux source package in Disco:
  Fix Committed
Status in linux-oem source package in Disco:
  Fix Committed
Status in mesa source package in Disco:
  Fix Released
Status in xorg-server source package in Disco:
  Fix Released

Bug description:
  [Impact]

  Please make it happen in the coming oem-kernel as there will be a
  flood of Intel Comet Lake (CML) platforms that would need it. Thank
  you.

  The same is needed for the rest of the stack.

  CML is basically another iteration of Skylake/Kabylake/Coffee Lake,
  and doesn't need other changes than pci-id's and support for the PCH
  (similar to Cannon point, already supported by the kernel).

  [Test case]

  Test that i915 graphics works on CML.

  [Regression potential]

  None really, these only add a bunch of new pci-id's across the stack.

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

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

[Touch-packages] [Bug 1823532] Re: Não Entra no google. E as vezes fica com a tela azul

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the
problem.
2. The behavior you expected.
3. The behavior you actually encountered (in as much detail as possible).
Thanks!

** Changed in: evolution-data-server (Ubuntu)
Importance: Undecided => Low

** Changed in: evolution-data-server (Ubuntu)
Status: New => Incomplete

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

Title:
Não Entra no google. E as vezes fica com a tela azul

Status in evolution-data-server package in Ubuntu:
Incomplete

Bug description:
As vezes a tela fica azul ou preta impossibilita acessar as funções e
tela e preta . As não entra no google e nas outras funções, e parece
algo relacionado ao software que impedi e baixar e atualiza .

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: evolution-data-server 3.18.5-1ubuntu1.1
ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
Uname: Linux 4.4.0-23-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
Date: Sun Apr 7 09:39:51 2019
DistributionChannelDescriptor:
# This is a distribution channel descriptor
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-xenial-amd64-20160624-2
ErrorMessage: problemas de dependência - deixando desconfigurado
InstallationDate: Installed on 2019-02-24 (41 days ago)
InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary
20160624-10:47
RelatedPackageVersions:
dpkg 1.18.4ubuntu1.5
apt 1.2.29ubuntu0.1
SourcePackage: evolution-data-server
Title: package evolution-data-server 3.18.5-1ubuntu1.1 failed to
install/upgrade: problemas de dependência - deixando desconfigurado
UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1823532/+subscriptions

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

[Touch-packages] [Bug 1823550] Re: GtkSourceView wrongly has monospaced font in dropdown (context) menu

** Changed in: gtk+3.0 (Ubuntu)
   Status: New => Invalid

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

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

Title:
  GtkSourceView wrongly has monospaced font in dropdown (context) menu

Status in GtkSourceView:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Invalid
Status in gtksourceview3 package in Ubuntu:
  Invalid
Status in mate-themes package in Ubuntu:
  New
Status in pluma package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 17.04 or later installed
  2. Open any application with GtkSourceView component - such as Pluma, Gedit, 
Giggle, Gitg, gnome-builder and maybe others (see complete list with `apt-cache 
rdepends libgtksourceview-3.0-1`)
  3. Click right mouse button on text zone

  Expected result:
  * dropdown menu has normal font as all other interface elements

  Actual result:
  * dropdwon menu wrongly has monospaced font

  Notes:
  * first seen in 17.04, but persists in 17.10, 18.04 LTS, 18.10, 19.04 
releases.
  * seems to be caused by GTK3 library

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: pluma 1.18.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.10
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sun Apr  7 20:13:24 2019
  InstallationDate: Installed on 2018-08-07 (243 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: pluma
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1823667] Re: pcre3 ftbfs with cosmic toolchain updates

fixed in disco, needs the disco upload in cosmic

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

Title:
  pcre3 ftbfs with cosmic toolchain updates

Status in pcre3 package in Ubuntu:
  New

Bug description:
  https://launchpadlibrarian.net/418304485/buildlog_ubuntu-cosmic-
  amd64.pcre3_2%3A8.39-11_BUILDING.txt.gz

  dh_makeshlibs -plibpcre3 --add-udeb="libpcre3-udeb" -V 'libpcre3 (>= 1:8.35)' 
-- -c4
  dh_makeshlibs -plibpcrecpp0v5 -V 'libpcrecpp0v5 (>= 7.7)' -- -c4
  dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols 
file: see diff output below
  dpkg-gensymbols: warning: debian/libpcrecpp0v5/DEBIAN/symbols doesn't match 
completely debian/libpcrecpp0v5.symbols
  --- debian/libpcrecpp0v5.symbols (libpcrecpp0v5_2:8.39-11_amd64)
  +++ dpkg-gensymbolsc5z0KV 2019-04-08 00:54:17.137602850 +
  @@ -80,9 +80,9 @@
(c++)"pcrecpp::Scanner::SetSkipExpression(char const*)@Base" 7.7
(c++)"pcrecpp::Scanner::Skip(char const*)@Base" 7.7
(c++)"pcrecpp::Scanner::~Scanner()@Base" 7.7
  -#MISSING: 2:8.39-9# (c++|optional=STL)"std::vector 
>::_M_insert_aux(__gnu_cxx::__normal_iterator > >, 
pcrecpp::StringPiece const&)@Base" 7.7
  +#MISSING: 2:8.39-11# (c++|optional=STL)"std::vector 
>::_M_insert_aux(__gnu_cxx::__normal_iterator > >, 
pcrecpp::StringPiece const&)@Base" 7.7
(c++|optional=STL)"void std::__cxx11::basic_string, std::allocator >::_M_construct(char 
const*, char const*, std::forward_iterator_tag)@Base" 2:8.39-10
  -#MISSING: 2:8.39-9# (c++|optional=STL)"void 
std::vector 
>::_M_emplace_back_aux(pcrecpp::StringPiece&&)@Base" 
2:8.39-2
  +#MISSING: 2:8.39-11# (c++|optional=STL)"void 
std::vector 
>::_M_emplace_back_aux(pcrecpp::StringPiece&&)@Base" 
2:8.39-2
(c++|optional=STL)"void std::vector >::_M_realloc_insert(__gnu_cxx::__normal_iterator > >, 
pcrecpp::StringPiece const&)@Base" 2:8.39-4
(c++|optional=STL)"void std::vector 
>::_M_realloc_insert(__gnu_cxx::__normal_iterator > >, 
pcrecpp::StringPiece&&)@Base" 2:8.39-9
  - (c++)"void std::vector 
>::emplace_back(pcrecpp::StringPiece&&)@Base" 2:8.39-10
  +#MISSING: 2:8.39-11# (c++)"void std::vector 
>::emplace_back(pcrecpp::StringPiece&&)@Base" 2:8.39-10
  dh_makeshlibs: failing due to earlier errors
  make: *** [debian/rules:116: binary-arch] Error 2
  dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned 
exit status 2
  

  Build finished at 20190408-0054

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

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

[Touch-packages] [Bug 1787956] Re: Network Manager overrides saved password with 2FA temporary code

2019-04-08 Thread one-w

Related upstream bug: https://gitlab.gnome.org/GNOME/NetworkManager-
openvpn/issues/12

** Bug watch added: gitlab.gnome.org/GNOME/NetworkManager-openvpn/issues #12
   https://gitlab.gnome.org/GNOME/NetworkManager-openvpn/issues/12

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

Title:
  Network Manager overrides saved password with 2FA temporary code

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Set up OpenVPN with MFA.

  Connect, and enter MFA code when prompted.

  Disconnect and reconnect

  Expected: Password portion is saved and reused

  Actual: The MFA code is saved in the password field and attempted
  first, then prompted for PW.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18
  Uname: Linux 4.15.0-30-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 20 09:49:23 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-06-07 (74 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/fish
  RfKill:
   
  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.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1823698] Re: dont know

2019-04-08 Thread tim parker

bug could have been received by email on yahoo on another linked
computer

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

Title:
  dont know

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  could be via email ?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
  Uname: Linux 4.15.0-47-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Mon Apr  8 12:14:53 2019
  DistUpgraded: 2018-08-28 23:59:06,593 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 4 Series Chipset Integrated Graphics Controller 
[8086:2e32] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 4 Series Chipset Integrated Graphics 
Controller [1043:836d]
  InstallationDate: Installed on 2012-03-13 (2582 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-47-generic 
root=UUID=b5d5d6d6-6240-4254-9586-c18faee66775 ro splash quiet
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-08-28 (222 days ago)
  dmi.bios.date: 11/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0405
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5G41T-M LX2/GB
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0405:bd11/22/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5G41T-MLX2/GB:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Tue Aug 28 20:10:43 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputMicrosoft Natural® Ergonomic Keyboard 4000 KEYBOARD, id 8
   inputMicrosoft Natural® Ergonomic Keyboard 4000 KEYBOARD, id 9
   inputLogitech USB-PS/2 Optical Mouse MOUSE, id 10
  xserver.errors:
   /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
   /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1432 
   vendor SAM
  xserver.version: 2:1.18.4-0ubuntu0.8

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

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

[Touch-packages] [Bug 1823658] Re: elfutils ftbfs with cosmic toolchain updates (arm64 only)

fixed in the updates pocket

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

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

Title:
  elfutils ftbfs with cosmic toolchain updates (arm64 only)

Status in elfutils package in Ubuntu:
  Invalid

Bug description:
  https://launchpadlibrarian.net/418304775/buildlog_ubuntu-cosmic-
  arm64.elfutils_0.170-0.5_BUILDING.txt.gz

  ==
 elfutils 0.170: tests/test-suite.log
  ==

  # TOTAL: 174
  # PASS:  167
  # SKIP:  5
  # XFAIL: 0
  # FAIL:  2
  # XPASS: 0
  # ERROR: 0

  .. contents:: :depth: 2

  SKIP: run-backtrace-data.sh
  ===

  /<>/tests/backtrace-data: Unwinding not supported for this 
architecture
  data: arch not supported
  SKIP run-backtrace-data.sh (exit status: 77)

  FAIL: run-backtrace-dwarf.sh
  

  0xad77c73craise
  0xad76a8e8abort
  /<>/tests/backtrace-dwarf: dwfl_thread_getframes: (null)
  dwarf: no main
  FAIL run-backtrace-dwarf.sh (exit status: 1)

  SKIP: run-backtrace-native-biarch.sh
  

  biarch testing disabled
  SKIP run-backtrace-native-biarch.sh (exit status: 77)

  SKIP: run-backtrace-native-core.sh
  ==

  No core.17943 file generated
  SKIP run-backtrace-native-core.sh (exit status: 77)

  SKIP: run-backtrace-native-core-biarch.sh
  =

  biarch testing disabled
  SKIP run-backtrace-native-core-biarch.sh (exit status: 77)

  FAIL: run-deleted.sh
  

  PID 18365 - process
  TID 18365:
  #0  0xae0a53e0 __nanosleep
  #1  0xae0a52c0 sleep
  /<>/src/stack: dwfl_thread_getframes tid 18365 at 0xae0a52bf 
in /lib/aarch64-linux-gnu/libc-2.28.so: (null)
  FAIL run-deleted.sh (exit status: 1)

  SKIP: run-lfs-symbols.sh
  

  LFS testing is irrelevent on this system
  SKIP run-lfs-symbols.sh (exit status: 77)

  make: *** [debian/rules:57: build-stamp] Error 1

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

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

[Touch-packages] [Bug 1823587] Re: totem crashed with SIGSEGV in magazine_chain_pop_head() from thread_memory_magazine1_alloc() from g_slice_alloc() from gst_buffer_new() from gst_buffer_copy_region()

** Changed in: gstreamer1.0 (Ubuntu)
   Importance: Undecided => Low

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

Title:
  totem crashed with SIGSEGV in magazine_chain_pop_head() from
  thread_memory_magazine1_alloc() from g_slice_alloc() from
  gst_buffer_new() from gst_buffer_copy_region()

Status in gstreamer1.0 package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gstreamer1.0.  This problem was most recently seen with package version 
3.26.2-1ubuntu3, the problem page at 
https://errors.ubuntu.com/problem/fa349f255c8a6919b90e34d3a1544a8b0bccf588 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1823666] Re: nss ftbfs with cosmic toolchain updates

fixed in the -updates pocket


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

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

Title:
  nss ftbfs with cosmic toolchain updates

Status in nss package in Ubuntu:
  Invalid

Bug description:
  https://launchpadlibrarian.net/418304406/buildlog_ubuntu-cosmic-
  amd64.nss_2%3A3.36.1-1ubuntu1_BUILDING.txt.gz

  make[2]: Entering directory '/<>/nss/coreconf/nsinstall'
  x86_64-linux-gnu-gcc -o OBJS/nsinstall.o -c -g -fPIC   -pipe 
-ffunction-sections -fdata-sections -DHAVE_STRERROR -DLINUX -Dlinux -Wall 
-Werror -DXP_UNIX -DDEBUG -UNDEBUG -DDEBUG_buildd -D_REENTRANT 
-DNSS_NO_INIT_SUPPORT -DUSE_UTIL_DIRECTLY -DNO_NSPR_10_SUPPORT 
-DSSL_DISABLE_DEPRECATED_CIPHER_SUITE_NAMES -I/<>/dist/include 
-I/<>/dist/public/coreconf 
-I/<>/dist/private/coreconf  nsinstall.c
  x86_64-linux-gnu-gcc -o OBJS/pathsub.o -c -g -fPIC   -pipe 
-ffunction-sections -fdata-sections -DHAVE_STRERROR -DLINUX -Dlinux -Wall 
-Werror -DXP_UNIX -DDEBUG -UNDEBUG -DDEBUG_buildd -D_REENTRANT 
-DNSS_NO_INIT_SUPPORT -DUSE_UTIL_DIRECTLY -DNO_NSPR_10_SUPPORT 
-DSSL_DISABLE_DEPRECATED_CIPHER_SUITE_NAMES -I/<>/dist/include 
-I/<>/dist/public/coreconf 
-I/<>/dist/private/coreconf  pathsub.c
  pathsub.c: In function ‘reversepath’:
  pathsub.c:215:6: error: ‘strncpy’ output truncated before terminating nul 
copying 3 bytes from a string of the same length [-Werror=stringop-truncation]
strncpy(cp, "../", 3);
^
  cc1: all warnings being treated as errors
  make[2]: *** [../../coreconf/rules.mk:393: OBJS/pathsub.o] Error 1
  make[2]: Leaving directory '/<>/nss/coreconf/nsinstall'
  make[1]: *** [debian/rules:106: override_dh_auto_build] Error 2
  make[1]: Leaving directory '/<>'
  make: *** [debian/rules:201: build] Error 2

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

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

[Touch-packages] [Bug 1763942] Re: Text selection in dialog windows have low contrast

** No longer affects: gtk+3.0 (Ubuntu)

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

Title:
  Text selection in dialog windows have low contrast

Status in mate-themes package in Ubuntu:
  New
Status in ubuntu-mate-artwork package in Ubuntu:
  New
Status in ubuntu-mate-meta package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce:
  1. Install Ubuntu MATE 18.04 LTS
  2. Launch `mate-terminal`, select *Help*, *About*, select text *A terminal 
emulator for the MATE desktop*. 

  
  Expected results:
  * selected text has good contrast 

  Actual results:
  * selected text has bad contrast as it is not selected.

  
  Note: you can find other examples of low contrast text.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-mate-desktop 1.222
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sat Apr 14 16:02:42 2018
  InstallationDate: Installed on 2018-04-14 (0 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180414)
  SourcePackage: ubuntu-mate-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mate-themes/+bug/1763942/+subscriptions

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

[Touch-packages] [Bug 1823700] [NEW] broken docker-compose version

2019-04-08 Thread abdullah

Public bug reported:

Docker-compose version 1.23.1 is buggy and has many issues. Docker-compose team 
has released a specific release for fixing them. 
 
https://github.com/docker/compose/releases/tag/1.23.2

Description:Ubuntu 18.04.2 LTS
Release:18.04

Kindly update it to 1.23.2 or higher.

Best Regards, 
Abdullah

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


** Tags: upgrade-software-version

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

Title:
  broken docker-compose version

Status in file package in Ubuntu:
  New

Bug description:
  Docker-compose version 1.23.1 is buggy and has many issues. Docker-compose 
team has released a specific release for fixing them. 
   
  https://github.com/docker/compose/releases/tag/1.23.2

  Description:Ubuntu 18.04.2 LTS
  Release:18.04

  Kindly update it to 1.23.2 or higher.

  Best Regards, 
  Abdullah

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

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

[Touch-packages] [Bug 1823698] Re: dont know

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected.
3. The behavior you actually encountered (in as much detail as possible).
Thanks! 

** Changed in: xorg (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  dont know

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  could be via email ?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
  Uname: Linux 4.15.0-47-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Mon Apr  8 12:14:53 2019
  DistUpgraded: 2018-08-28 23:59:06,593 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 4 Series Chipset Integrated Graphics Controller 
[8086:2e32] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 4 Series Chipset Integrated Graphics 
Controller [1043:836d]
  InstallationDate: Installed on 2012-03-13 (2582 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-47-generic 
root=UUID=b5d5d6d6-6240-4254-9586-c18faee66775 ro splash quiet
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-08-28 (222 days ago)
  dmi.bios.date: 11/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0405
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5G41T-M LX2/GB
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0405:bd11/22/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5G41T-MLX2/GB:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Tue Aug 28 20:10:43 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputMicrosoft Natural® Ergonomic Keyboard 4000 KEYBOARD, id 8
   inputMicrosoft Natural® Ergonomic Keyboard 4000 KEYBOARD, id 9
   inputLogitech USB-PS/2 Optical Mouse MOUSE, id 10
  xserver.errors:
   /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
   /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1432 
   vendor SAM
  xserver.version: 2:1.18.4-0ubuntu0.8

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

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

[Touch-packages] [Bug 1823698] [NEW] dont know

2019-04-08 Thread tim parker

Public bug reported:

could be via email ?

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
Uname: Linux 4.15.0-47-generic i686
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Mon Apr  8 12:14:53 2019
DistUpgraded: 2018-08-28 23:59:06,593 DEBUG icon theme changed, re-reading
DistroCodename: bionic
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e32] 
(rev 03) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. 4 Series Chipset Integrated Graphics 
Controller [1043:836d]
InstallationDate: Installed on 2012-03-13 (2582 days ago)
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
MachineType: System manufacturer System Product Name
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-47-generic 
root=UUID=b5d5d6d6-6240-4254-9586-c18faee66775 ro splash quiet
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2018-08-28 (222 days ago)
dmi.bios.date: 11/22/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0405
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5G41T-M LX2/GB
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0405:bd11/22/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5G41T-MLX2/GB:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.95-1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Tue Aug 28 20:10:43 2018
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputMicrosoft Natural® Ergonomic Keyboard 4000 KEYBOARD, id 8
 inputMicrosoft Natural® Ergonomic Keyboard 4000 KEYBOARD, id 9
 inputLogitech USB-PS/2 Optical Mouse MOUSE, id 10
xserver.errors:
 /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
 /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id1432 
 vendor SAM
xserver.version: 2:1.18.4-0ubuntu0.8

** Affects: xorg (Ubuntu)
 Importance: Low
 Status: Incomplete


** Tags: apport-bug bionic i386 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/1823698

Title:
  dont know

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  could be via email ?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
  Uname: Linux 4.15.0-47-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Mon Apr  8 12:14:53 2019
  DistUpgraded: 2018-08-28 23:59:06,593 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 4 Series Chipset Integrated Graphics Controller 
[8086:2e32] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 4 Series Chipset Integrated Graphics 
Controller [1043:836d]
  InstallationDate: Installed on 2012-03-13 (2582 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-47-generic 
root=UUID=b5d5d6d6-6240-4254-9586-c18faee66775 ro splash quiet
  SourcePackage: xorg

[Touch-packages] [Bug 1822416] Re: resolve: do not hit CNAME or DNAME entry in NODATA cache

2019-04-08 Thread Chiang Fong Lee

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

** This bug has been marked a duplicate of bug 1818527
   Stub resolver cache is corrupted

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

Title:
  resolve: do not hit CNAME or DNAME entry in NODATA cache

Status in systemd package in Ubuntu:
  New

Bug description:
  The question: DNS A record lookups fail to resolve due to cached CNAME
  NODATA lookups ...

  https://askubuntu.com/questions/1063462/18-04-server-systemd-resolve-
  returns-cached-cname-nodata-for-a-lookup

  Upstream at Github: Systemd issue 998 - Cached cname NODATA returned
  for A lookup ...

  https://github.com/systemd/systemd/issues/9833

  
  Please patch ...

  
https://github.com/systemd/systemd/commit/3740146a4cbd99883af79e375ee4836206dcea4e

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

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

[Touch-packages] [Bug 1818527] Re: Stub resolver cache is corrupted

2019-04-08 Thread Chiang Fong Lee

This seems to be the same issue previously reported at
https://github.com/systemd/systemd/issues/9833, which was fixed in
https://github.com/systemd/systemd/pull/9836 (commit 3740146) and
released in v240.

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

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

Title:
  Stub resolver cache is corrupted

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  It seems that when systemd-resolve cache an non-existent CNAME record
  for a domain, any attempt to resolve A record for the same domain
  fail.

  systemd version the issue has been seen with
  Installed: 237-3ubuntu10.13
  Used distribution

  Distributor ID: Ubuntu
  Description: Ubuntu 18.04.2 LTS
  Release: 18.04
  Codename: bionic

  Expected behaviour you didn't see

  Return A record for a domain when it exists.

  Unexpected behaviour you saw

  Resolution failed.

  Steps to reproduce the problem

  Whait for 1 minutes (github.com TTL for A record)

  Try to resolv github.com CNAME record dig CNAME github.com

  This will return an empty result.

  Then try to resolve github.com A record dig A github.com.

  This will now return empty result unless you restart systemd-resolved
  or wait for cache expiration.

  At the same time using another DNS will resolve correctly dig A
  github.com @8.8.8.8.

  Exemple :

  Wait for 1 minutes to let cache expire, then run

  dig CNAME github.com
  dig A github.com
  # no result
  dig A github.com @8.8.8.8
  # ;; ANSWER SECTION:
  # github.com. 59  IN  A   192.30.253.113
  # github.com. 59  IN  A   192.30.253.112

  PS: Don't forget to restart systemd-resolve, before trying to post an
  answer.

  This bug was first reported in github
  https://github.com/systemd/systemd/issues/11789 but systemd version in
  ubuntu is too  old.

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

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

[Touch-packages] [Bug 1818527] Re: Stub resolver cache is corrupted

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

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

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

Title:
  Stub resolver cache is corrupted

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  It seems that when systemd-resolve cache an non-existent CNAME record
  for a domain, any attempt to resolve A record for the same domain
  fail.

  systemd version the issue has been seen with
  Installed: 237-3ubuntu10.13
  Used distribution

  Distributor ID: Ubuntu
  Description: Ubuntu 18.04.2 LTS
  Release: 18.04
  Codename: bionic

  Expected behaviour you didn't see

  Return A record for a domain when it exists.

  Unexpected behaviour you saw

  Resolution failed.

  Steps to reproduce the problem

  Whait for 1 minutes (github.com TTL for A record)

  Try to resolv github.com CNAME record dig CNAME github.com

  This will return an empty result.

  Then try to resolve github.com A record dig A github.com.

  This will now return empty result unless you restart systemd-resolved
  or wait for cache expiration.

  At the same time using another DNS will resolve correctly dig A
  github.com @8.8.8.8.

  Exemple :

  Wait for 1 minutes to let cache expire, then run

  dig CNAME github.com
  dig A github.com
  # no result
  dig A github.com @8.8.8.8
  # ;; ANSWER SECTION:
  # github.com. 59  IN  A   192.30.253.113
  # github.com. 59  IN  A   192.30.253.112

  PS: Don't forget to restart systemd-resolve, before trying to post an
  answer.

  This bug was first reported in github
  https://github.com/systemd/systemd/issues/11789 but systemd version in
  ubuntu is too  old.

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

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

[Touch-packages] [Bug 1763942] Re: Text selection in dialog windows have low contrast

It is theming issue:

* affected themes - Ambiant-MATE, Ambiant-MATE-Dark, Radiant-MATE;
* not affected themes - BlackMATE, BlueMenta, Blue-Submarine, GreenLaguna, 
Green-Submarine, High Contrast, High Contrast Inverse, Menta, TraditionalGreen, 
TraditionalOk.

So all default `mate-themes` themes should be changed to have normal
text selection rectangle. See TraditionalOk as good example in
attachment.

** Attachment added: "TraditionalOk theme is not affected"
   
https://bugs.launchpad.net/ubuntu/+source/mate-themes/+bug/1763942/+attachment/5254049/+files/TraditionalOk-selection.png

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

Title:
  Text selection in dialog windows have low contrast

Status in gtk+3.0 package in Ubuntu:
  New
Status in mate-themes package in Ubuntu:
  New
Status in ubuntu-mate-artwork package in Ubuntu:
  New
Status in ubuntu-mate-meta package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce:
  1. Install Ubuntu MATE 18.04 LTS
  2. Launch `mate-terminal`, select *Help*, *About*, select text *A terminal 
emulator for the MATE desktop*. 

  
  Expected results:
  * selected text has good contrast 

  Actual results:
  * selected text has bad contrast as it is not selected.

  
  Note: you can find other examples of low contrast text.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-mate-desktop 1.222
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sat Apr 14 16:02:42 2018
  InstallationDate: Installed on 2018-04-14 (0 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180414)
  SourcePackage: ubuntu-mate-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1783283] Re: setvtrgb.service incorrectly ordered [with patchy]

2019-04-08 Thread Harald Sitter

Was there a question in there?

I did also see this on installed kubuntu systems, it's just far harder
to reproduce there because of the racy nature of the issue. In fact, the
only reason I know about the issue is because the colors are just so far
off that they tripped up our openqa tests and flaked every so often.

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

Title:
  setvtrgb.service incorrectly ordered [with patchy]

Status in console-setup package in Ubuntu:
  Incomplete

Bug description:
  setvtrgb is not correctly ordered when used with plymouth. It has an 
After=plymouth-quit-wait.service, but that may not be applicable when 
plymouth-quit.service is queued instead. This ultimately results in semi-random 
setvtrgb results as calling setvtrgb too soon will do nothing if the VTs aren't 
up/still getting fiddled with with by plymouth. So, depending on the unit tree 
the VT may have the correct custom color, or the default kernel color.
  Since this is entirely dependent on the units being started, and their 
effective order, this is super hard to reproduce reliably. The most reliable 
way I have is an ISO which has Calamares instead of Ubiquity and SDDM instead 
of GDM, which 100% of the time ends up having a unit order where setvtrgb is 
called way too soon (even before getty.target, although I am not sure that 
matters as far as the VT colors are concerned).

  The solution seems excitingly simple though. Adding an After=plymouth-
  quit.service rule correctly orders the unit at least in my test case.
  Since After is only an order hint this should be entirely regression
  free.

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

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

[Touch-packages] [Bug 1573982] Re: LVM boot problem - volumes not activated after upgrade to Xenial

2019-04-08 Thread alienn

Well. Today I installed a fresh 18.04 server and just ran into this issue. 
My disk setup is as following:
/dev/sda1 - bios
/dev/sda2 - /boot
/dev/sdb (LVM)
  - vg-0/Usr
  - vg-0/Home
  - vg-0/Root
  - vg-0/Swap
/dev/sdc (LVM
  - vg-1/Var

Upon reboot I get an error within initramfs that the root was not found. 
Executing vgchange -ay activates the volumes and I can continue with ctrl-d .
Why is this not fixed? And why is the last state "invalid"?

- Nicki

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

Title:
  LVM boot problem - volumes not activated after upgrade to Xenial

Status in curtin:
  Incomplete
Status in MAAS:
  Invalid
Status in lvm2 package in Ubuntu:
  Confirmed

Bug description:
  Soon after upgrade to Xenial (from 15.10) the boot process got broken.
  I'm using LVM for /root swap and other partitions.

  ===
  The current behaviour is:

  When I boot short after the Grub login screen I'm getting log messages
  like:

  ---
  Scanning for Btrfs filesystems
  resume: Could not state the resume device file: '/dev/mapper/VolGroup'
  Please type in the full path...
  ---

  Then I press ENTER, for a few minutes some errors about floppy device
  access are raised (for some reason it tries to scan fd0 when floppy
  drive is empty). And then:

  ---
  Gave up waiting for root device. Common problems: ...
  ...
  ALERT! UUID=xxx-xxx does not exist.
  Dropping to a shell.
  ---

  From the BusyBox shell I managed to recover the boot by issuing "lvm
  vgchange -ay", then exit and then boot continues fine (all LVM file
  systems are successfully mounted).

  ===
  One workaround so far is creating 
/etc/initramfs-tools/scripts/local-top/lvm2-manual script doing "lvm vgchange 
-ay". But I'm looking for cleaner solution.

  Boot used to work fine with 15.10. Actually the first boot after
  upgrading to Xenial actually worked OK too, I'm not sure what might
  changed meanwhile (I've been fixing some packages installation since
  mysql server upgrade has failed).

  ===
  # lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

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

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

[Touch-packages] [Bug 1763942] Re: Text selection in dialog windows have low contrast