date:20171107

** Changed in: ubuntu-meta (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

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

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

Bug description:
  [Impact]

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

  [Test Case]

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

  [Regression Potential]

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

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

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

[Touch-packages] [Bug 1716069] Re: systemd breaks apparmor (<2.10.95-1). in turn mysql-server wont install

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

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

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

Title:
  systemd breaks apparmor (<2.10.95-1). in turn mysql-server wont
  install

Status in apparmor package in Ubuntu:
  Expired

Bug description:
  mysql-server cant be installed, because systemd
  (233-8ubuntu1~ubuntu16.04.1) requires a newer version of apparmor than
  the installed version 2.10.95-0ubuntu2.7 this in tune breaks various
  packages depending on mysql-server, like gnu-cash or others.

  Possible solutions:
  - provide a newer apparmor package for ubuntu 16.04.1
  - provide a mysql-server package not depending on apparmor
  - provide a systemd package working with apparmor 2.10.95-0ubuntu2.7

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

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

[Touch-packages] [Bug 768613] Re: apport does not work on turkish locale

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

** This bug has been marked a duplicate of bug 1030483
   apport-collect crash when sending log file and using a non-English locale

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

Title:
  apport does not work on turkish locale

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: apport

  ubuntu-bug apport
  ERROR: /etc/apport/crashdb.conf is damaged: No default database

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: apport 1.20.1-0ubuntu5
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic i686
  NonfreeKernelModules: wl
  ApportLog:
   
  Architecture: i386
  Date: Fri Apr 22 00:19:43 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110104)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=tr_TR:tr_TR.UTF-8:tr:en_GB:en
   PATH=(custom, user)
   LANG=tr_TR.UTF-8
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: Upgraded to natty on 2011-03-08 (44 days ago)

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

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

[Touch-packages] [Bug 1030483] Re: apport-collect crash when sending log file and using a non-English locale ("TypeError: 'unicode' does not have the buffer interface")

** Summary changed:

- apport-collect crash when sending log file and using a non-English locale
+ apport-collect crash when sending log file and using a non-English locale 
("TypeError: 'unicode' does not have the buffer interface")

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

Title:
  apport-collect crash when sending log file and using a non-English
  locale ("TypeError: 'unicode' does not have the buffer interface")

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  In the process of updating #1030151 I was hit by a bug in apport-collect. 
When doing 
  apport-collect 1030151
  in a root console the apport-collect would crash with following trace back : 

  Traceback (most recent call last):
File "/usr/share/apport/apport-gtk", line 587, in 
  app.run_argv()
File "/usr/lib/python2.7/dist-packages/apport/ui.py", line 634, in run_argv
  return self.run_update_report()
File "/usr/lib/python2.7/dist-packages/apport/ui.py", line 554, in 
run_update_report
  attachment_comment='apport information')
File "/usr/lib/python2.7/dist-packages/apport/crashdb_impl/launchpad.py", 
line 356, in update
  report.write_mime(mime, skip_keys=skip_keys)
File "/usr/lib/python2.7/dist-packages/problem_report.py", line 505, in 
write_mime
  attach_value = CompressedValue(v, k).gzipvalue
File "/usr/lib/python2.7/dist-packages/problem_report.py", line 44, in 
__init__
  self.set_value(value)
File "/usr/lib/python2.7/dist-packages/problem_report.py", line 50, in 
set_value
  gzip.GzipFile(self.name, mode='wb', fileobj=out).write(value)
File "/usr/lib/python2.7/gzip.py", line 131, in __init__
  self._write_gzip_header()
File "/usr/lib/python2.7/gzip.py", line 176, in _write_gzip_header
  self.fileobj.write(fname + '\000')
  TypeError: 'unicode' does not have the buffer interface

  Calling apport-collect with LC_ALL=C or LANG=C as suggest by Edward
  Donovan didn't solve the issue.

  I used this workaround : in 
/usr/lib/python2.7/dist-packages/problem_report.py I replaced line  50 :
  gzip.GzipFile(self.name, mode='wb', fileobj=out).write(value)
  by :
  gzip.GzipFile(self.name.encode('UTF-8'), mode='wb', 
fileobj=out).write(value.encode('UTF-8'))

  It's a quick and dirty hack but maybe it will help the developpers to
  trully solve the issue.

  Cheers !

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: apport 2.4-0ubuntu6
  ProcVersionSignature: Ubuntu 3.5.0-6.6-generic 3.5.0
  Uname: Linux 3.5.0-6-generic x86_64
  ApportLog:
   
  ApportVersion: 2.4-0ubuntu6
  Architecture: amd64
  CrashReports:
   644:0:110:0:2012-07-29 12:14:17.260971307 +0200:2012-07-29 
12:14:17.260971307 +0200:/var/crash/_sbin_plymouthd.0.upload
   600:105:110:0:2012-07-29 12:14:25.388971230 +0200:2012-07-29 
12:14:25.388971230 +0200:/var/crash/_sbin_plymouthd.0.uploaded
   640:0:110:1232461:2012-07-29 12:08:44.732974000 +0200:2012-07-29 
12:14:18.284971294 +0200:/var/crash/_sbin_plymouthd.0.crash
  Date: Sun Jul 29 12:53:17 2012
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120627)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1730841] Re: /usr/share/apport/apport-gtk:ValueError:/usr/share/apport/apport-gtk@597:run_argv:run_crashes:get_timestamp:getlocale:_parse_localename

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

** This bug has been marked a duplicate of bug 1677172
   apport-gtk crashed with ValueError in _parse_localename(): unknown locale: 
lzh_TW

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

Title:
  /usr/share/apport/apport-gtk:ValueError:/usr/share/apport/apport-
  gtk@597:run_argv:run_crashes:get_timestamp:getlocale:_parse_localename

Status in apport package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.20.3-0ubuntu8.3, the problem page at 
https://errors.ubuntu.com/problem/39159170a2e2c3917e96a46300ae2e12b7ef57c2 
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/apport/+bug/1730841/+subscriptions

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

[Touch-packages] [Bug 1677172] Re: apport-gtk crashed with ValueError in _parse_localename(): unknown locale: lzh_TW

Also tracking here:
https://errors.ubuntu.com/problem/39159170a2e2c3917e96a46300ae2e12b7ef57c2

** Information type changed from Private to Public

** Description changed:

+ https://errors.ubuntu.com/problem/39159170a2e2c3917e96a46300ae2e12b7ef57c2
+ 
+ ---
+ 
  on restart up after an update
  
  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: apport-gtk 2.20.4-0ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: LXDE
  Date: Wed Mar 29 13:43:24 2017
  ExecutablePath: /usr/share/apport/apport-gtk
  InstallationDate: Installed on 2017-02-24 (32 days ago)
  InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
  InterpreterPath: /usr/bin/python3.5
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk
  PythonArgs: ['/usr/share/apport/apport-gtk']
  SourcePackage: apport
  Title: apport-gtk crashed with ValueError in _parse_localename(): unknown 
locale: lzh_TW
  UpgradeStatus: Upgraded to zesty on 2017-02-24 (32 days ago)
  UserGroups: adm audio cdrom dialout dip fax floppy lpadmin netdev 
nopasswdlogin plugdev sambashare scanner sudo tape video

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

Title:
  apport-gtk crashed with ValueError in _parse_localename(): unknown
  locale: lzh_TW

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/39159170a2e2c3917e96a46300ae2e12b7ef57c2

  ---

  on restart up after an update

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: apport-gtk 2.20.4-0ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: LXDE
  Date: Wed Mar 29 13:43:24 2017
  ExecutablePath: /usr/share/apport/apport-gtk
  InstallationDate: Installed on 2017-02-24 (32 days ago)
  InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
  InterpreterPath: /usr/bin/python3.5
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk
  PythonArgs: ['/usr/share/apport/apport-gtk']
  SourcePackage: apport
  Title: apport-gtk crashed with ValueError in _parse_localename(): unknown 
locale: lzh_TW
  UpgradeStatus: Upgraded to zesty on 2017-02-24 (32 days ago)
  UserGroups: adm audio cdrom dialout dip fax floppy lpadmin netdev 
nopasswdlogin plugdev sambashare scanner sudo tape video

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

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

[Touch-packages] [Bug 1730841] [NEW] /usr/share/apport/apport-gtk:ValueError:/usr/share/apport/apport-gtk@597:run_argv:run_crashes:get_timestamp:getlocale:_parse_localename

2017-11-07 Thread errors.ubuntu.com bug bridge

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

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.20.3-0ubuntu8.3, the problem page at 
https://errors.ubuntu.com/problem/39159170a2e2c3917e96a46300ae2e12b7ef57c2 
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/.

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


** Tags: xenial yakkety

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

Title:
  /usr/share/apport/apport-gtk:ValueError:/usr/share/apport/apport-
  gtk@597:run_argv:run_crashes:get_timestamp:getlocale:_parse_localename

Status in apport package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.20.3-0ubuntu8.3, the problem page at 
https://errors.ubuntu.com/problem/39159170a2e2c3917e96a46300ae2e12b7ef57c2 
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/apport/+bug/1730841/+subscriptions

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

[Touch-packages] [Bug 1726093] Re: ubuntu-desktop: Install gir1.2-gmenu-3.0 by default

Hello Jeremy, or anyone else affected,

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

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

** Also affects: ubuntu-meta (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-meta (Ubuntu Artful)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-artful

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

Title:
  ubuntu-desktop: Install gir1.2-gmenu-3.0 by default

Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-meta source package in Artful:
  Fix Committed

Bug description:
  Impact
  ==
  Ubuntu doesn't install particular files ( gir1.2-gmenu-3.0 ) that are needed 
by several popular GNOME Shell extensions.

  Test Case
  =
  Install the update to Ubuntu 17.10.
  Open the Ubuntu Software app.
  Search for Arc Menu
  Install it.
  There should be an A menu in the top left of the screen.

  Other Info
  ==
  Debian-based distros are somewhat unique in that they split gir files into 
separate packages. This is normally not a problem since .deb packages should 
simply depend on the packages they need. It is a bit of a problem for GNOME 
Shell extensions distributed through extensions.gnome.org since they can't 
depend on system packages except as a comment in the extension description that 
may or may be read even if it is mentioned.

  Specifically, there are several extensions that add a traditional
  applications menu to GNOME Shell. These usually need gir1.2-gmenu-3.0.

  This wasn't noticed much before because both Debian GNOME and Ubuntu
  GNOME installed the gnome-shell-extensions package by default which
  depends on gir1.2-gmenu-3.0.

  Now though, it just feels to users like Ubuntu is broken. I've read
  comments that think that Ubuntu is intentionally trying to make it
  difficult to use these app menu extensions.

  Approved at the Ubuntu Desktop meeting (discussion continues until 15:09)
  https://irclogs.ubuntu.com/2017/10/24/%23ubuntu-desktop.html#t14:44

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

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

[Touch-packages] [Bug 1730639] Re: ubuntu-bug does not recognize lzh_TW locale

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1677172, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of private bug 1677172

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

Title:
  ubuntu-bug does not recognize lzh_TW locale

Status in apport package in Ubuntu:
  New

Bug description:
  While trying to upload the .crash file for bug 1730554, using command:

  $ ubuntu-bug /var/crash/_usr_bin_gnome-shell.1000.crash

  The tool crashes with unknown locale error:
  ERROR: hook /usr/share/apport/general-hooks/generic.py crashed:
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 198, in 
_run_hook
  symb['add_info'](report, ui)
File "/usr/share/apport/general-hooks/generic.py", line 48, in add_info
  if gtk_like and apport.hookutils.in_session_of_problem(report):
File "/usr/lib/python3/dist-packages/apport/hookutils.py", line 882, in 
in_session_of_problem
  orig_ctime = locale.getlocale(locale.LC_TIME)
File "/usr/lib/python3.5/locale.py", line 577, in getlocale
  return _parse_localename(localename)
File "/usr/lib/python3.5/locale.py", line 486, in _parse_localename
  raise ValueError('unknown locale: %s' % localename)
  ValueError: unknown locale: lzh_TW

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: apport 2.20.4-0ubuntu4.5
  ProcVersionSignature: Ubuntu 4.10.0-38.42-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  ApportLog:
   ERROR: apport (pid 28299) Tue Nov  7 11:12:04 2017: called for pid 2068, 
signal 11, core limit 0
   ERROR: apport (pid 28299) Tue Nov  7 11:12:04 2017: executable: 
/usr/bin/gnome-shell (command line "/usr/bin/gnome-shell")
   ERROR: apport (pid 28299) Tue Nov  7 11:12:05 2017: debug: session gdbus 
call: (true,)
   
   ERROR: apport (pid 28299) Tue Nov  7 11:13:15 2017: wrote report 
/var/crash/_usr_bin_gnome-shell.1000.crash
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CrashReports:
   600:111:119:0:2017-11-07 18:35:26.974509633 +0800:2017-11-07 
18:33:17.310366228 +0800:/var/crash/_usr_bin_gnome-shell.1000.uploaded
   640:1000:119:42648617:2017-11-07 18:35:08.738488435 +0800:2017-11-07 
18:35:13.822493362 +0800:/var/crash/_usr_bin_gnome-shell.1000.crash
   640:1000:119:58131:2017-11-07 18:36:03.870557135 +0800:2017-11-07 
18:36:03.870557135 +0800:/var/crash/_usr_share_apport_apport-gtk.1000.crash
   644:1000:119:0:2017-11-07 18:35:24.294506287 +0800:2017-11-07 
18:35:24.294506287 +0800:/var/crash/_usr_bin_gnome-shell.1000.upload
  CurrentDesktop: GNOME
  Date: Tue Nov  7 18:36:00 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-07-12 (117 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

Hello Dimitri, or anyone else affected,

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

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

** Changed in: ubuntu-meta (Ubuntu Artful)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-artful

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

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

Status in ubuntu-meta package in Ubuntu:
  Fix Committed
Status in ubuntu-meta source package in Xenial:
  Fix Committed
Status in ubuntu-meta source package in Zesty:
  Fix Committed
Status in ubuntu-meta source package in Artful:
  Fix Committed
Status in ubuntu-meta source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

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

  [Test Case]

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

  [Regression Potential]

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

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

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

[Touch-packages] [Bug 1730639] Re: ubuntu-bug does not recognize lzh_TW locale

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

As a workaround please try:

  env LANG=C ubuntu-bug /var/crash/_usr_bin_gnome-shell.1000.crash

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

Title:
  ubuntu-bug does not recognize lzh_TW locale

Status in apport package in Ubuntu:
  New

Bug description:
  While trying to upload the .crash file for bug 1730554, using command:

  $ ubuntu-bug /var/crash/_usr_bin_gnome-shell.1000.crash

  The tool crashes with unknown locale error:
  ERROR: hook /usr/share/apport/general-hooks/generic.py crashed:
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 198, in 
_run_hook
  symb['add_info'](report, ui)
File "/usr/share/apport/general-hooks/generic.py", line 48, in add_info
  if gtk_like and apport.hookutils.in_session_of_problem(report):
File "/usr/lib/python3/dist-packages/apport/hookutils.py", line 882, in 
in_session_of_problem
  orig_ctime = locale.getlocale(locale.LC_TIME)
File "/usr/lib/python3.5/locale.py", line 577, in getlocale
  return _parse_localename(localename)
File "/usr/lib/python3.5/locale.py", line 486, in _parse_localename
  raise ValueError('unknown locale: %s' % localename)
  ValueError: unknown locale: lzh_TW

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: apport 2.20.4-0ubuntu4.5
  ProcVersionSignature: Ubuntu 4.10.0-38.42-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  ApportLog:
   ERROR: apport (pid 28299) Tue Nov  7 11:12:04 2017: called for pid 2068, 
signal 11, core limit 0
   ERROR: apport (pid 28299) Tue Nov  7 11:12:04 2017: executable: 
/usr/bin/gnome-shell (command line "/usr/bin/gnome-shell")
   ERROR: apport (pid 28299) Tue Nov  7 11:12:05 2017: debug: session gdbus 
call: (true,)
   
   ERROR: apport (pid 28299) Tue Nov  7 11:13:15 2017: wrote report 
/var/crash/_usr_bin_gnome-shell.1000.crash
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CrashReports:
   600:111:119:0:2017-11-07 18:35:26.974509633 +0800:2017-11-07 
18:33:17.310366228 +0800:/var/crash/_usr_bin_gnome-shell.1000.uploaded
   640:1000:119:42648617:2017-11-07 18:35:08.738488435 +0800:2017-11-07 
18:35:13.822493362 +0800:/var/crash/_usr_bin_gnome-shell.1000.crash
   640:1000:119:58131:2017-11-07 18:36:03.870557135 +0800:2017-11-07 
18:36:03.870557135 +0800:/var/crash/_usr_share_apport_apport-gtk.1000.crash
   644:1000:119:0:2017-11-07 18:35:24.294506287 +0800:2017-11-07 
18:35:24.294506287 +0800:/var/crash/_usr_bin_gnome-shell.1000.upload
  CurrentDesktop: GNOME
  Date: Tue Nov  7 18:36:00 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-07-12 (117 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

Hello Dimitri, or anyone else affected,

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

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

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

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

Status in ubuntu-meta package in Ubuntu:
  Fix Committed
Status in ubuntu-meta source package in Xenial:
  Fix Committed
Status in ubuntu-meta source package in Zesty:
  Fix Committed
Status in ubuntu-meta source package in Artful:
  Fix Committed
Status in ubuntu-meta source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

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

  [Test Case]

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

  [Regression Potential]

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

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

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

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

Hello Dimitri, or anyone else affected,

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

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

** Changed in: ubuntu-meta (Ubuntu Xenial)
   Status: In Progress => Fix Committed

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

** Changed in: ubuntu-meta (Ubuntu Zesty)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-zesty

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

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

Status in ubuntu-meta package in Ubuntu:
  Fix Committed
Status in ubuntu-meta source package in Xenial:
  Fix Committed
Status in ubuntu-meta source package in Zesty:
  Fix Committed
Status in ubuntu-meta source package in Artful:
  Fix Committed
Status in ubuntu-meta source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

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

  [Test Case]

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

  [Regression Potential]

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

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

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

[Touch-packages] [Bug 1682102] Re: libseccomp should support GA and HWE kernels

I built this package in the ubuntu-security-proposed PPA so it can be
released to both -updates and -security (which seems like probably a
sane thing to do) once it's passed the SRU process.

** Changed in: libseccomp (Ubuntu Xenial)
   Status: Confirmed => Fix Committed

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

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

Title:
  libseccomp should support GA and HWE kernels

Status in libseccomp package in Ubuntu:
  Invalid
Status in libseccomp source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

  out of date libseccomp w.r.t. custom and hwe kernels provides sub-par 
userspace protection, which is otherwise available on the running kernel and 
hardware combination.
  This results in subpar security of systems running new architectures (s390x & 
ppc64el) and newer hwe/custom kernels.

  * Version 2.3.1 - April 20, 2016
  - Fixed a problem with 32-bit x86 socket syscalls on some systems
  - Fixed problems with ipc syscalls on 32-bit x86
  - Fixed problems with socket and ipc syscalls on s390 and s390x

  * Version 2.3.0 - February 29, 2016
  - Added support for the s390 and s390x architectures
  - Added support for the ppc, ppc64, and ppc64le architectures
  - Update the internal syscall tables to match the Linux 4.5-rcX releases
  - Filter generation for both multiplexed and direct socket syscalls on x86
  - Support for the musl libc implementation
  - Additions to the API to enable runtime version checking of the library
  - Enable the use of seccomp() instead of prctl() on supported systems
  - Added additional tests to the regression test suite

  There is no ABI/API break

  There are no packaging changes, apart from dropping patches included
  in this upstream release and updating new symbols.

  Doing wholesome update is safer and carries less risk, than
  individually cherrypicking effectively all of the above.

  This is a backport to an LTS release under the banner of safe
  introduction of new features and new hardware support.

  It is expected that container technologies will take advantage of the
  newly available libseccomp.

  This may need to be uploaded as a security update.

  Currently, s390x support in xenial libssecomp is incomplete. And there
  are v4.5+ syscall tables missing as used by hwe kernels and some
  custom kernels.

  [Testcase]
  Validate that all main contianer technologies are operational and do not 
regress, e.g.:
   - lxc
   - lxd
   - docker
   - snapd

  [Regression Potential]
  Userspace components may detect at runtime newly available libseccomp, and 
thus restrict user-space processes more than previously done. This may lead to 
a change of restrictions applied on the user sapce processes, and result in 
previously unexpected denials / errors returned.

  
  [Proposed Update available in bileto PPA]
  https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/2981

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

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

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

Hello Dimitri, or anyone else affected,

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

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

** Changed in: libseccomp (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  libseccomp should support GA and HWE kernels

Status in libseccomp package in Ubuntu:
  Invalid
Status in libseccomp source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

  out of date libseccomp w.r.t. custom and hwe kernels provides sub-par 
userspace protection, which is otherwise available on the running kernel and 
hardware combination.
  This results in subpar security of systems running new architectures (s390x & 
ppc64el) and newer hwe/custom kernels.

  * Version 2.3.1 - April 20, 2016
  - Fixed a problem with 32-bit x86 socket syscalls on some systems
  - Fixed problems with ipc syscalls on 32-bit x86
  - Fixed problems with socket and ipc syscalls on s390 and s390x

  * Version 2.3.0 - February 29, 2016
  - Added support for the s390 and s390x architectures
  - Added support for the ppc, ppc64, and ppc64le architectures
  - Update the internal syscall tables to match the Linux 4.5-rcX releases
  - Filter generation for both multiplexed and direct socket syscalls on x86
  - Support for the musl libc implementation
  - Additions to the API to enable runtime version checking of the library
  - Enable the use of seccomp() instead of prctl() on supported systems
  - Added additional tests to the regression test suite

  There is no ABI/API break

  There are no packaging changes, apart from dropping patches included
  in this upstream release and updating new symbols.

  Doing wholesome update is safer and carries less risk, than
  individually cherrypicking effectively all of the above.

  This is a backport to an LTS release under the banner of safe
  introduction of new features and new hardware support.

  It is expected that container technologies will take advantage of the
  newly available libseccomp.

  This may need to be uploaded as a security update.

  Currently, s390x support in xenial libssecomp is incomplete. And there
  are v4.5+ syscall tables missing as used by hwe kernels and some
  custom kernels.

  [Testcase]
  Validate that all main contianer technologies are operational and do not 
regress, e.g.:
   - lxc
   - lxd
   - docker
   - snapd

  [Regression Potential]
  Userspace components may detect at runtime newly available libseccomp, and 
thus restrict user-space processes more than previously done. This may lead to 
a change of restrictions applied on the user sapce processes, and result in 
previously unexpected denials / errors returned.

  
  [Proposed Update available in bileto PPA]
  https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/2981

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

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

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

2017-11-07 Thread Steve Langasek

What does systemd-resolve --status show in this scenario?

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

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

Status in systemd package in Ubuntu:
  New

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

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

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

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

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

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

[Touch-packages] [Bug 1729389] Re: Bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react

** Also affects: bluez (Fedora) via
   https://bugzilla.redhat.com/show_bug.cgi?id=1500407
   Importance: Unknown
   Status: Unknown

** Package changed: bluez (Fedora) => linux (Fedora)

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

** No longer affects: linux (Fedora)

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

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

Title:
  Bluetooth mouse and keyboard connects, works for a few seconds, then
  doesn't react

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After upgrading from Ubuntu Gnome 17.04 to Ubuntu 17.10, bluetooth
  mouse and keyboard connects, works for a few seconds, then doesn't
  react.

  Bluetooth package version: 5.46-0ubuntu3 500

  Please tell me which log-files to upload.

  Thanks
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2016-06-11 (509 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 006: ID 04b4:5210 Cypress Semiconductor Corp. 
   Bus 001 Device 005: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 13d3:5664 IMC Networks 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80MK
  Package: bluez 5.46-0ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=ed8fbe48-3db5-4a77-ab34-f35fd1a481cc ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-23 (11 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/01/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C6CN37WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: VIUU4
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 900-13ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrC6CN37WW:bd03/01/2016:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80MK
  dmi.product.version: Lenovo YOGA 900-13ISK
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: A4:34:D9:9A:CD:FF  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY 
RX bytes:71005 acl:1028 sco:0 events:2920 errors:0
TX bytes:601922 acl:36 sco:0 commands:2468 errors:0

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

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

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

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

** Changed in: resolvconf (Ubuntu Trusty)
 Assignee: (unassigned) => Scott Moser (smoser)

** Changed in: resolvconf (Ubuntu Xenial)
 Assignee: (unassigned) => Scott Moser (smoser)

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

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

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

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

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

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

  [Test Case]
  There are two tests for this.

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

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

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

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

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

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

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

  [Other Info]

  === End SRU Template ===

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

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

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

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

  Which correctly includes the DNS server. However:

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

  If restart the interfacE:

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

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

[Touch-packages] [Bug 1729558] Re: [regression] In Java apps like Netbeans, dark menu bars don't look good for disabled elements

2017-11-07 Thread md_5

No upstream bug yet unfortunately (OpenJDK bugtracker is restricted access as 
I'm sure you know).
I made a mailing list thread a few days ago here 
http://mail.openjdk.java.net/pipermail/swing-dev/2017-November/007904.html 
although haven't had any feedback aside from the patch not being attached!

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

Title:
  [regression] In Java apps like Netbeans, dark menu bars don't look
  good for disabled elements

Status in Ubuntu theme:
  Invalid
Status in openjdk-8 package in Ubuntu:
  Confirmed
Status in openjdk-9 package in Ubuntu:
  New
Status in ubuntu-themes package in Ubuntu:
  Invalid

Bug description:
  This fix, #961679, specifically Ambiance/gtk-2.0/gtkrc:346
  (http://bazaar.launchpad.net/~ubuntu-art-pkg/ubuntu-
  themes/trunk/revision/583), makes disabled elements in menus look
  terrible.

  Unfortunately I'm not aware of an easy way to get screenshots of open
  menus, so hopefully these attached phone pictures of Netbeans are
  enough to illustrate the issue.

  As you can see it is hard to tell the difference between what is
  disabled and what isn't, and the disabled items look fuzzy (easier to
  observe on monitor).

  I really don't see the issue with lighter menus, but if they must stay
  dark then the readability / contrast of disabled items needs to be
  fixed.

  Thanks

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

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

[Touch-packages] [Bug 1729558] Re: [regression] In Java apps like Netbeans, dark menu bars don't look good for disabled elements

Great, thanks. Do you have a link to the upstream bug?

** Changed in: openjdk-9 (Ubuntu)
   Importance: Undecided => Low

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

Title:
  [regression] In Java apps like Netbeans, dark menu bars don't look
  good for disabled elements

Status in Ubuntu theme:
  Invalid
Status in openjdk-8 package in Ubuntu:
  Confirmed
Status in openjdk-9 package in Ubuntu:
  New
Status in ubuntu-themes package in Ubuntu:
  Invalid

Bug description:
  This fix, #961679, specifically Ambiance/gtk-2.0/gtkrc:346
  (http://bazaar.launchpad.net/~ubuntu-art-pkg/ubuntu-
  themes/trunk/revision/583), makes disabled elements in menus look
  terrible.

  Unfortunately I'm not aware of an easy way to get screenshots of open
  menus, so hopefully these attached phone pictures of Netbeans are
  enough to illustrate the issue.

  As you can see it is hard to tell the difference between what is
  disabled and what isn't, and the disabled items look fuzzy (easier to
  observe on monitor).

  I really don't see the issue with lighter menus, but if they must stay
  dark then the readability / contrast of disabled items needs to be
  fixed.

  Thanks

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

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

[Touch-packages] [Bug 1729558] Re: [regression] In Java apps like Netbeans, dark menu bars don't look good for disabled elements

2017-11-07 Thread md_5

Patch I submitted upstream is attached, not through yet though.

** Patch added: "disabled.diff"
   
https://bugs.launchpad.net/ubuntu/+source/openjdk-8/+bug/1729558/+attachment/5005613/+files/disabled.diff

** Also affects: openjdk-9 (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/1729558

Title:
  [regression] In Java apps like Netbeans, dark menu bars don't look
  good for disabled elements

Status in Ubuntu theme:
  Invalid
Status in openjdk-8 package in Ubuntu:
  Confirmed
Status in openjdk-9 package in Ubuntu:
  New
Status in ubuntu-themes package in Ubuntu:
  Invalid

Bug description:
  This fix, #961679, specifically Ambiance/gtk-2.0/gtkrc:346
  (http://bazaar.launchpad.net/~ubuntu-art-pkg/ubuntu-
  themes/trunk/revision/583), makes disabled elements in menus look
  terrible.

  Unfortunately I'm not aware of an easy way to get screenshots of open
  menus, so hopefully these attached phone pictures of Netbeans are
  enough to illustrate the issue.

  As you can see it is hard to tell the difference between what is
  disabled and what isn't, and the disabled items look fuzzy (easier to
  observe on monitor).

  I really don't see the issue with lighter menus, but if they must stay
  dark then the readability / contrast of disabled items needs to be
  fixed.

  Thanks

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

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

[Touch-packages] [Bug 1730793] [NEW] Translations not imported from upstream

2017-11-07 Thread Ask Hjorth Larsen

Public bug reported:

The listing of Ubuntu source package translations (for Danish) reveals
that the last import of translations for util-linux happened in 2011:

https://translations.launchpad.net/ubuntu/artful/+lang/da/+index?batch=300=300=300

The Ubuntu source package version is 2.30, which appears to be from 2017
(on my Ubuntu 16.04 it is 2.27 which is also relatively new).  Either
way it should have imported the translations from 2017.  Indeed util-
linux has been translated very well in Danish for quite a few years:

https://translationproject.org/domain/util-linux.html

More precisely, 4000 translations are available and they have not been
imported for (apparently) 6 years, leaving Danish at the level of 600
strings.

I suspect this is not really an issue with the util-linux source
package, but rather with the whole Ubuntu/Launchpad translations
workflow.  I can see that several packages have similar problems, and
that is probably just the tip of the iceberg.  Unfortunately I have no
clue how to approach that - at least I cannot file a bug report against
The Whole Thing.  So if someone could speak to someone who could speak
to someone who can actually get this to work, it would also be extremely
good.

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

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

Title:
  Translations not imported from upstream

Status in util-linux package in Ubuntu:
  New

Bug description:
  The listing of Ubuntu source package translations (for Danish) reveals
  that the last import of translations for util-linux happened in 2011:

  
https://translations.launchpad.net/ubuntu/artful/+lang/da/+index?batch=300=300=300

  The Ubuntu source package version is 2.30, which appears to be from
  2017 (on my Ubuntu 16.04 it is 2.27 which is also relatively new).
  Either way it should have imported the translations from 2017.  Indeed
  util-linux has been translated very well in Danish for quite a few
  years:

  https://translationproject.org/domain/util-linux.html

  More precisely, 4000 translations are available and they have not been
  imported for (apparently) 6 years, leaving Danish at the level of 600
  strings.

  I suspect this is not really an issue with the util-linux source
  package, but rather with the whole Ubuntu/Launchpad translations
  workflow.  I can see that several packages have similar problems, and
  that is probably just the tip of the iceberg.  Unfortunately I have no
  clue how to approach that - at least I cannot file a bug report
  against The Whole Thing.  So if someone could speak to someone who
  could speak to someone who can actually get this to work, it would
  also be extremely good.

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

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

[Touch-packages] [Bug 1729389] Re: Bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react

2017-11-07 Thread PJSingh5000

See if the following provides a workaround...

$ sudo gedit /etc/modprobe.d/iwlwifi.conf

# Add to the end:
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
options iwlwifi bt_coex_active=0
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

# Restart

This was suggsted on the following RedHat bug report:
https://bugzilla.redhat.com/show_bug.cgi?id=1500407


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

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

Title:
  Bluetooth mouse and keyboard connects, works for a few seconds, then
  doesn't react

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  After upgrading from Ubuntu Gnome 17.04 to Ubuntu 17.10, bluetooth
  mouse and keyboard connects, works for a few seconds, then doesn't
  react.

  Bluetooth package version: 5.46-0ubuntu3 500

  Please tell me which log-files to upload.

  Thanks
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2016-06-11 (509 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 006: ID 04b4:5210 Cypress Semiconductor Corp. 
   Bus 001 Device 005: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 13d3:5664 IMC Networks 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80MK
  Package: bluez 5.46-0ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=ed8fbe48-3db5-4a77-ab34-f35fd1a481cc ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-23 (11 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/01/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C6CN37WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: VIUU4
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 900-13ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrC6CN37WW:bd03/01/2016:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80MK
  dmi.product.version: Lenovo YOGA 900-13ISK
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: A4:34:D9:9A:CD:FF  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY 
RX bytes:71005 acl:1028 sco:0 events:2920 errors:0
TX bytes:601922 acl:36 sco:0 commands:2468 errors:0

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

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

[Touch-packages] [Bug 1722528] Re: find buffer-overflow with -printf '%T+'

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

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

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

Title:
   find buffer-overflow with -printf '%T+'

Status in findutils:
  Unknown
Status in findutils package in Ubuntu:
  Confirmed
Status in findutils package in Debian:
  Unknown

Bug description:
  This has already been reported upstream. Just reporting it here
  because I observed it in artful.

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

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

[Touch-packages] [Bug 1730696] Re: * buffer overflow detected *: find terminated

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

** This bug has been marked a duplicate of bug 1722528
find buffer-overflow with -printf '%T+'

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

Title:
  *** buffer overflow detected ***: find terminated

Status in findutils package in Ubuntu:
  Confirmed
Status in findutils package in Debian:
  Fix Released

Bug description:
  When running find with -printf "%T+ %p\n"

  The -printf "%T+ %p\n" worked in previous versions. This is a new bug
  in 17.10.

  ```
  > find .  -printf "%A+ %p\n"
  *** buffer overflow detected ***: find terminated
  Aborted (core dumped)
  ```

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

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

[Touch-packages] [Bug 1730767] [NEW] /lib/systemd/systemd-journald:6:journal_file_move_to_object:journal_file_append_object:journal_file_append_data:journal_file_append_entry:write_to_journal

2017-11-07 Thread errors.ubuntu.com bug bridge

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
systemd.  This problem was most recently seen with package version 
234-2ubuntu12.1, the problem page at 
https://errors.ubuntu.com/problem/0bdfb1861952322eb09e5e0b4c6d66020a08ac7c 
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/.

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


** Tags: artful kylin-15.04 vivid wily xenial yakkety zesty

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

Title:
  /lib/systemd/systemd-
  
journald:6:journal_file_move_to_object:journal_file_append_object:journal_file_append_data:journal_file_append_entry:write_to_journal

Status in systemd package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
systemd.  This problem was most recently seen with package version 
234-2ubuntu12.1, the problem page at 
https://errors.ubuntu.com/problem/0bdfb1861952322eb09e5e0b4c6d66020a08ac7c 
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/systemd/+bug/1730767/+subscriptions

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

[Touch-packages] [Bug 1641284] Re: libatk-adaptor breaks down the LibreOffice TexMaths extension

2017-11-07 Thread Bug Watch Updater

** Changed in: at-spi2-atk (Debian)
   Status: Unknown => New

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

Title:
  libatk-adaptor breaks down the LibreOffice TexMaths extension

Status in at-spi2-atk package in Ubuntu:
  Confirmed
Status in at-spi2-atk package in Debian:
  New

Bug description:
  Package: libatk-adaptor 2.18.1-2ubuntu1
  System: Ubuntu 16.04.1 LTS (Xenial Xerus)

  If the package libatk-adaptor is installed on Ubuntu (as a depency of
  gnome-orca for example), it breaks down the LibreOffice TexMaths
  extension. TexMaths is a popular extension used to enter / edit LaTeX
  equations on LibreOffice (see http://roland65.free.fr/texmaths).

  Step to reproduce the bug:

  1. It is assumed that LibreOffice 5.1.4 (with at least the Writer and
  Draw components) is installed on Ubuntu. It is also assumed that
  libatk-adaptor is installed.

  2. Install texlive:
  sudo apt-get install texlive

  3. Download and install the TexMaths extension (version 0.42) from
  there: https://sourceforge.net/projects/texmaths/files/0.42/

  4. Create a new empty Writer document, then click on the Pi icon (this
  is the TexMaths icon) and in the window that opens, type: 'x(t)+y(t)'
  (without the quotes), then click on the LaTeX button. This generates
  an SVG image of the 'x(t)+y(t)' equation.

  5. Select the SVG image of the equation by left clicking on it. Then
  click on the Pi icon. Now, instead of editing the equation, an error
  message is displayed: "The selected object is not a TexMaths
  equation... Please unselect it and call the macro again...".

  6. Now, right click on the SVG image and select the 'Description' menu
  voice. In the window that opens, the description is empty and does not
  contain the equation text, as it should.

  7. Now purge (and not just remove) the libatk-adaptor package:

  sudo apt-get purge libatk-adaptor

  then logout and login and repeat the steps 4, 5, and 6: everything is
  OK and the equation can be edited as usual.

  Another way to remove the bug instead of purging libatk-adaptor is to
  rename the file: /etc/X11/Xsession.d/90atk-adaptor to
  /etc/X11/Xsession.d/90atk-adaptor.orig . Then logout and login.

  Note there is another bug #1584795 that relates libatk-adaptor and
  LibreOffice, see there https://bugs.launchpad.net/ubuntu/+source/at-
  spi2-atk/+bug/1584795

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/at-spi2-atk/+bug/1641284/+subscriptions

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

[Touch-packages] [Bug 1730696] Re: * buffer overflow detected *: find terminated

2017-11-07 Thread Bug Watch Updater

** Changed in: findutils (Debian)
   Status: Unknown => Fix Released

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

Title:
  *** buffer overflow detected ***: find terminated

Status in findutils package in Ubuntu:
  Confirmed
Status in findutils package in Debian:
  Fix Released

Bug description:
  When running find with -printf "%T+ %p\n"

  The -printf "%T+ %p\n" worked in previous versions. This is a new bug
  in 17.10.

  ```
  > find .  -printf "%A+ %p\n"
  *** buffer overflow detected ***: find terminated
  Aborted (core dumped)
  ```

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

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

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

Somewhat interestingly, I'm not sure why I can't just reproduce this by:

$ sudo bash -c 'oname=$(hostname); 
  trap "hostname $oname" EXIT; 
  hostname my-bogus-hostname; 
  hostname;
  time sudo /bin/true;' ; hostname

but it doesnt reproduce this way.

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

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

Status in systemd package in Ubuntu:
  New

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

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

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

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

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

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

[Touch-packages] [Bug 1730759] Re: package sysv-rc 2.88dsf-59.3ubuntu2 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1

2017-11-07 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package sysv-rc 2.88dsf-59.3ubuntu2 failed to install/upgrade: el
  subproceso instalado el script post-installation devolvió el código de
  salida de error 1

Status in sysvinit package in Ubuntu:
  New

Bug description:
  package sysv-rc 2.88dsf-59.3ubuntu2 failed to install/upgrade: el
  subproceso instalado el script post-installation devolvió el código de
  salida de error 1

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: sysv-rc 2.88dsf-59.3ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-93.140-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-93-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.25
  Architecture: amd64
  Date: Tue Nov  7 18:48:38 2017
  DuplicateSignature: package:sysv-rc:2.88dsf-59.3ubuntu2:el subproceso 
instalado el script post-installation devolvió el código de salida de error 1
  ErrorMessage: el subproceso instalado el script post-installation devolvió el 
código de salida de error 1
  InstallationDate: Installed on 2013-04-26 (1656 days ago)
  InstallationMedia: Ubuntu-Server 12.04 LTS "Precise Pangolin" - Beta amd64 
(20120418)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.0.1ubuntu2.17
  SourcePackage: sysvinit
  Title: package sysv-rc 2.88dsf-59.3ubuntu2 failed to install/upgrade: el 
subproceso instalado el script post-installation devolvió el código de salida 
de error 1
  UpgradeStatus: Upgraded to xenial on 2017-11-07 (0 days ago)

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

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

[Touch-packages] [Bug 1166529] Re: Creative Recon3d & Sound Blaster Z (CA0132), No Sound At All; Broken Beyond All Repair

2017-11-07 Thread Michael Murphy

ALSA does not exist on it's own within a package. It's a part of the
Linux kernel (because Linux is a macrokernel).

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

Title:
  Creative Recon3d & Sound Blaster Z (CA0132), No Sound At All; Broken
  Beyond All Repair

Status in ALSA driver:
  Unknown
Status in Linux:
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in alsa-driver package in Debian:
  New

Bug description:
  [WORKAROUND] Run the following command:

  echo "options snd-hda-intel position_fix=1" | sudo tee -a
  /etc/modprobe.d/alsa-base.conf

  [EDIT]
  Workaround doesn't work anymore for me at least. I assume it only has a small 
possibility of working due to a firmware bug.

  [ORIGINAL REPORT]
  No sound, no jacks; It is detected by Linux however.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5
  Uname: Linux 3.8.0-16-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: amd64
  Date: Mon Apr  8 18:56:44 2013
  InstallationDate: Installed on 2013-04-07 (1 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402.1)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Creative failed
  Symptom_Card: HDA Creative - HDA Creative
  Symptom_Type: No sound at all
  Title: [To be filled by O.E.M., Creative CA0132, Green Line Out, Rear] No 
sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/12/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1102
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: SABERTOOTH 990FX
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1102:bd03/12/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FX:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

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

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

[Touch-packages] [Bug 1730759] [NEW] package sysv-rc 2.88dsf-59.3ubuntu2 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1

2017-11-07 Thread jar

Public bug reported:

package sysv-rc 2.88dsf-59.3ubuntu2 failed to install/upgrade: el
subproceso instalado el script post-installation devolvió el código de
salida de error 1

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: sysv-rc 2.88dsf-59.3ubuntu2
ProcVersionSignature: Ubuntu 3.13.0-93.140-generic 3.13.11-ckt39
Uname: Linux 3.13.0-93-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.25
Architecture: amd64
Date: Tue Nov  7 18:48:38 2017
DuplicateSignature: package:sysv-rc:2.88dsf-59.3ubuntu2:el subproceso instalado 
el script post-installation devolvió el código de salida de error 1
ErrorMessage: el subproceso instalado el script post-installation devolvió el 
código de salida de error 1
InstallationDate: Installed on 2013-04-26 (1656 days ago)
InstallationMedia: Ubuntu-Server 12.04 LTS "Precise Pangolin" - Beta amd64 
(20120418)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.0.1ubuntu2.17
SourcePackage: sysvinit
Title: package sysv-rc 2.88dsf-59.3ubuntu2 failed to install/upgrade: el 
subproceso instalado el script post-installation devolvió el código de salida 
de error 1
UpgradeStatus: Upgraded to xenial on 2017-11-07 (0 days ago)

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


** Tags: amd64 apport-package third-party-packages xenial

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

Title:
  package sysv-rc 2.88dsf-59.3ubuntu2 failed to install/upgrade: el
  subproceso instalado el script post-installation devolvió el código de
  salida de error 1

Status in sysvinit package in Ubuntu:
  New

Bug description:
  package sysv-rc 2.88dsf-59.3ubuntu2 failed to install/upgrade: el
  subproceso instalado el script post-installation devolvió el código de
  salida de error 1

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: sysv-rc 2.88dsf-59.3ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-93.140-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-93-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.25
  Architecture: amd64
  Date: Tue Nov  7 18:48:38 2017
  DuplicateSignature: package:sysv-rc:2.88dsf-59.3ubuntu2:el subproceso 
instalado el script post-installation devolvió el código de salida de error 1
  ErrorMessage: el subproceso instalado el script post-installation devolvió el 
código de salida de error 1
  InstallationDate: Installed on 2013-04-26 (1656 days ago)
  InstallationMedia: Ubuntu-Server 12.04 LTS "Precise Pangolin" - Beta amd64 
(20120418)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.0.1ubuntu2.17
  SourcePackage: sysvinit
  Title: package sysv-rc 2.88dsf-59.3ubuntu2 failed to install/upgrade: el 
subproceso instalado el script post-installation devolvió el código de salida 
de error 1
  UpgradeStatus: Upgraded to xenial on 2017-11-07 (0 days ago)

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

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

[Touch-packages] [Bug 1166529] Re: Creative Recon3d & Sound Blaster Z (CA0132), No Sound At All; Broken Beyond All Repair

2017-11-07 Thread Zaszuś

Launchpad says alsa package was updated for the last time on 2013-10-20.
Is it true that Linux/Ubuntu does not have any sound development for 4
years??

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

Title:
  Creative Recon3d & Sound Blaster Z (CA0132), No Sound At All; Broken
  Beyond All Repair

Status in ALSA driver:
  Unknown
Status in Linux:
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in alsa-driver package in Debian:
  New

Bug description:
  [WORKAROUND] Run the following command:

  echo "options snd-hda-intel position_fix=1" | sudo tee -a
  /etc/modprobe.d/alsa-base.conf

  [EDIT]
  Workaround doesn't work anymore for me at least. I assume it only has a small 
possibility of working due to a firmware bug.

  [ORIGINAL REPORT]
  No sound, no jacks; It is detected by Linux however.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5
  Uname: Linux 3.8.0-16-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: amd64
  Date: Mon Apr  8 18:56:44 2013
  InstallationDate: Installed on 2013-04-07 (1 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402.1)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Creative failed
  Symptom_Card: HDA Creative - HDA Creative
  Symptom_Type: No sound at all
  Title: [To be filled by O.E.M., Creative CA0132, Green Line Out, Rear] No 
sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/12/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1102
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: SABERTOOTH 990FX
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1102:bd03/12/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FX:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

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

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

[Touch-packages] [Bug 1522675] Re: Warning messages about unsandboxed downloads

2017-11-07 Thread Norbert

Got this bug again on fresh installation of kUbuntu 16.04 LTS during
installation of kubuntu-restricted-extras (especially fonts).

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

Title:
  Warning messages about unsandboxed downloads

Status in apt package in Ubuntu:
  Fix Released
Status in aptitude package in Ubuntu:
  Fix Released
Status in synaptic package in Ubuntu:
  Triaged
Status in update-notifier package in Ubuntu:
  Fix Released
Status in apt package in Debian:
  Fix Released
Status in aptitude package in Debian:
  Fix Released
Status in synaptic package in Debian:
  New

Bug description:
  Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but
  now get that error when installing/upgrading some packages:

  Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ...
  Processing triggers for libc-bin (2.21-0ubuntu5) ...
  W: Can't drop privileges for downloading as file 
'/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - 
pkgAcquire::Run (13: Permission denied)

  From nautilus, i'm seeing a /root/ folder locked (x on its icon) and
  the folder is empty (no /.synaptic/ sub-folder or file), so the above
  error.

  oem@u64:~$ ls -l .synaptic
  total 4
  -rw-rw-r-- 1 oem oem   0 Aug 25 11:19 options
  -rw-rw-r-- 1 oem oem 236 Aug 25 11:19 synaptic.conf

  oem@u64:~$ ls -l /var/lib/apt/lists/
  
  -rw-r- 1 root root0 Sep 20 06:36 lock
  drwx-- 2 _apt root16384 Sep 24 15:25 partial
  ..

  oem@u64:~$ sudo ls -l /var/lib/update-notifier/package-data-downloads/
  .
  drwxr-xr-x 2 _apt root 4096 Sep 22 23:33 partial

  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: synaptic 0.82+build1
  ProcVersionSignature: Ubuntu 4.3.0-1.10-generic 4.3.0
  Uname: Linux 4.3.0-1-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.2-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Dec  4 05:23:25 2015
  SourcePackage: synaptic
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1586528] Re: Avahi-daemon withdraws address record

2017-11-07 Thread SamTzu

As niedzielski wrote on 2017-07-19:

It's clearly a IPv6 issue. Temp solution is to disable IPv6 until they
can fix NetworkManager. Most of us don't need it anyway.


Add the following /etc/sysctl.conf:

  net.ipv6.conf.all.disable_ipv6 = 1
  net.ipv6.conf.default.disable_ipv6 = 1
  net.ipv6.conf.lo.disable_ipv6 = 1


Sam

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

Title:
  Avahi-daemon withdraws address record

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

Bug description:
  For some reason, if I leave my Ubuntu VM up for a prolonged period of
  time the machine will lose connection to the network.  ip addr shows
  that the nic port no longer has an address and an examination of the
  syslog shows this:

  May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Withdrawing address record 
for 10.0.2.15 on enp0s3.
  May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Leaving mDNS multicast 
group on interface enp0s3.IPv4 with address 10.0.2.15.
  May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Interface enp0s3.IPv4 no 
longer relevant for mDNS.

  
  for no known reason.

  The only reliable way to get the network to come back (that I have
  found) is a full reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2
  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
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri May 27 15:11:34 2016
  InstallationDate: Installed on 2015-10-22 (218 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: avahi
  UpgradeStatus: Upgraded to xenial on 2016-03-30 (58 days ago)

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

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

[Touch-packages] [Bug 1727696] Re: System does not shut down without Ctrl+Alt+F7

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

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

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

Title:
  System does not shut down without Ctrl+Alt+F7

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  This is a fresh 17.10 installation, for some reason defaulting to Xorg
  instead of wayland (no choice given in the login screen).

  Anyway, shutting down from X session doesn't work. Screen stays blank
  black, cursor blinking in top left corner. Seems like it's stuck there
  forever (haven't had patience to wait long enough).

  Found a workaround: in the black screen cursor blinking state above,
  hit Ctrl+Alt+F7. One second or so after that, the system shuts down
  cleanly every time.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  BootLog: /dev/sda1: clean, 153154/2842624 files, 1254197/11368960 blocks
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 26 14:27:05 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. N56VZ [1043:2103]
   NVIDIA Corporation GK107M [GeForce GT 650M] [10de:0fd1] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. N56VZ [1043:2103]
  InstallationDate: Installed on 2017-10-26 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: ASUSTeK COMPUTER INC. N56VZ
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=be8c6652-102f-4bc2-9739-4c7954b40a80 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/22/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N56VZ.217
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N56VZ
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN56VZ.217:bd05/22/2013:svnASUSTeKCOMPUTERINC.:pnN56VZ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN56VZ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: N
  dmi.product.name: N56VZ
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1730696] Re: * buffer overflow detected *: find terminated

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

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

Title:
  *** buffer overflow detected ***: find terminated

Status in findutils package in Ubuntu:
  Confirmed
Status in findutils package in Debian:
  Unknown

Bug description:
  When running find with -printf "%T+ %p\n"

  The -printf "%T+ %p\n" worked in previous versions. This is a new bug
  in 17.10.

  ```
  > find .  -printf "%A+ %p\n"
  *** buffer overflow detected ***: find terminated
  Aborted (core dumped)
  ```

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

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

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

This is more easily recreated with lxc.

Given a host with systemd-resolv:

$ lxc launch ubuntu-daily:xenial x1
$ sleep 10 # let it boot
$ lxc exec x1 -- grep '^[^#]' /etc/resolv.conf
nameserver 10.75.205.1
search lxd

$ lxc exec x1 -- hostname bogus-host
$ lxc exec x1 -- bash -c 'time sudo /bin/true'
sudo: unable to resolve host bogus-host: Connection timed out

real0m20.042s
user0m0.005s
sys 0m0.014s

$ lxc exec x1 -- bash -c 'time host bogus-host 10.75.205.1'
Using domain server:
Name: 10.75.205.1
Address: 10.75.205.1#53
Aliases: 

Host bogus-host not found: 2(SERVFAIL)

real0m0.780s
user0m0.011s
sys 0m0.015s

$ lxc exec x1 -- bash -c 'time hostname --fqdn'
hostname: Temporary failure in name resolution

real0m10.009s
user0m0.002s
sys 0m0.000s

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

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

Status in systemd package in Ubuntu:
  New

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

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

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

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

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

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

[Touch-packages] [Bug 1576583] Re: vim paste option bracks expandtab option

2017-11-07 Thread Will Gray

This is not a bug, but the defined behavior of the 'paste' setting.

> When the 'paste' option is switched on (also when it was already on):
> - 'expandtab' is reset

** Changed in: vim (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  vim paste option bracks expandtab option

Status in vim package in Ubuntu:
  Invalid

Bug description:
  i am using ubuntu xenial.

  when I use vim options at the end of a file like the following:

  # vim: syntax=yaml ts=2 sw=2 et sr softtabstop=2 autoindent paste

  it should convert an entered tab into spaces (pressing tab should
  result into 2 spaces). in the past it actually did. currently it does
  not anymore. the problem here seems to be the last option "paste". if
  i leave out the paste options the expandtab (et) option works again.
  the paste option should not have any effect on the expandtab option
  though.

  
  steps to reproduce:

  - create a file with "# vim: syntax=yaml ts=2 sw=2 et sr softtabstop=2 
autoindent paste" at the end of the file. 
  - save it
  - reopen it with vim
  - in insert mode: press tab key
  - the tab should have been converted into 2 spaces (but it doesn't)
  - remove the paste option  "# vim: syntax=yaml ts=2 sw=2 et sr softtabstop=2 
autoindent"
  - save it
  - reopen it with vim
  - in insert mode: press tab key again
  - now the tab is converted into 2 spaces

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

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

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

I've uploaded the same change that is in xenial but slightly adjusted for 
trusty.
I'm attaching an updated recreate script that works for both xenial and trusty.
(trusty needs to install the cloud-initramfs-dyn-netconf package to mimic the 
MAAS ephemeral environment).


** Attachment added: "lp-1711760-test.sh:  works for xenial or trusty"
   
https://bugs.launchpad.net/maas/+bug/1711760/+attachment/5005575/+files/lp-1711760-test.sh

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

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

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

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

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

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

  [Test Case]
  There are two tests for this.

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

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

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

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

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

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

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

  [Other Info]

  === End SRU Template ===

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

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

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

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

  Which correctly includes the DNS server. However:

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

  If restart the interfacE:

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

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

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

** Merge proposal linked:

https://code.launchpad.net/~smoser/ubuntu/+source/resolvconf/+git/resolvconf/+merge/37

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

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

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

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

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

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

[Test Case]
There are two tests for this.

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

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

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

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

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

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

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

[Other Info]

=== End SRU Template ===

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

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

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

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

Which correctly includes the DNS server. However:

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

If restart the interfacE:

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

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

ubuntu@manual:~$ cat /etc/resolv.conf
# Dynamic resolv.conf(5)

[Touch-packages] [Bug 1730696] Re: * buffer overflow detected *: find terminated

I can confirm the bug:

There is a blatant stack overflow in the ubuntu 17.10 sources 
(findutils-4.6.0+git+20170729):
file "find/print.c", function "static char* format_date", line 614 and following

char fmt[6];
/* a few lines later */
strcpy(fmt, "%Y-%m-%d+%T");

that is string is longer than 5 characters
that call should be strncpy anyway

the non-crashing versions (previous ubuntu, also official GNU sources
4.6.0) instead have

strcpy (fmt, "%F+%T");

which does fit exactly into a six byte buffer

The obvious fix is to increase the size of fmt to hold the longer string

there is a comment in the new sources, explaining the motivation

  /* Avoid %F, some Unix versions lack it.  For example:
 HP Tru64 UNIX V5.1B (Rev. 2650); Wed Feb 17 22:59:59 CST 2016
 Also, some older HP-UX versions expand %F as the full month (like %B).
 Reported by Steven M. Schweda  */


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

** Bug watch added: GNU Savannah Bug Tracker #51841
   http://savannah.gnu.org/bugs/?51841

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

Title:
  *** buffer overflow detected ***: find terminated

Status in findutils package in Ubuntu:
  Confirmed

Bug description:
  When running find with -printf "%T+ %p\n"

  The -printf "%T+ %p\n" worked in previous versions. This is a new bug
  in 17.10.

  ```
  > find .  -printf "%A+ %p\n"
  *** buffer overflow detected ***: find terminated
  Aborted (core dumped)
  ```

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

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

[Touch-packages] [Bug 1730696] Re: * buffer overflow detected *: find terminated

I just checked the GNU git sources
(https://git.savannah.gnu.org/git/findutils.git)

the bug was fixed upstream

commit febde26dd0e66dda5d4060fa29b85443ddc6a865
Author: Bernhard Voelker 
Date:   Mon Aug 28 23:15:12 2017 +0200

find: avoid buffer-overflow with -printf '%T+'

* find/print.c (format_date): Increase size of local variable
FMT to match the longest possible content.

Fixes https://bugs.debian.org/873032 reported upstream by
Andreas Metzler in https://savannah.gnu.org/bugs/?51841;
fix proposed by Kamil Dudka.

Bug introduced in commit v4.6.0-111-g95816b2, so no released version
ever saw this; therefore not adding a NEWS entry.

commit 95816b29d46fb6b64754d4a66e7d918b3f134a1f
Author: James Youngman 
Date:   Sun Jul 23 22:19:42 2017 +0100

find: avoid strftime's non-portable %F specifier.

* find/print.c (format_date): Avoid passing %F to strftime since
some implementation lack it.  Pass the synonymous %Y-%m-%d
instead.  This fixes a bug manifesting on HP Tru64 UNIX V5.1B.
Reported by Steven M. Schweda .

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

Title:
  *** buffer overflow detected ***: find terminated

Status in findutils package in Ubuntu:
  Confirmed

Bug description:
  When running find with -printf "%T+ %p\n"

  The -printf "%T+ %p\n" worked in previous versions. This is a new bug
  in 17.10.

  ```
  > find .  -printf "%A+ %p\n"
  *** buffer overflow detected ***: find terminated
  Aborted (core dumped)
  ```

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

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

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

sooo, turns out this is caused by debian/patches/vulkan-mir.patch, which
needs to be either dropped or updated to cover radv too

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

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

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

Title:
  vulkan-smoketest segfaults steam vulkan games segfault

Status in mesa package in Ubuntu:
  Triaged

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

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

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

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

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

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

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

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

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

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

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

Here is some information collected when I tried to debug.

 Using resolved on host =
## guest
$ 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
nameserver 10.0.2.3
search mydomain.com bar.com

ubuntu@rooturl-trusty$ time sudo /bin/true
sudo: unable to resolve host rooturl-trusty

$ time sudo /bin/true
real0m10.021s
user0m0.007s
sys 0m0.004s

## host 
$ grep "^[^#]" /etc/resolv.conf
nameserver 127.0.0.53
search mydomain.net lan

$ sudo tcpdump -i any udp port 53
14:51:58.038103 IP localhost.55365 > localhost.domain: 36012+ A? 
rooturl-trusty.mydomain.com. (45)
14:51:58.038180 IP localhost.55365 > localhost.domain: 49842+ ? 
rooturl-trusty.mydomain.com. (45)
14:51:58.038569 IP localhost.domain > localhost.55365: 36012 NXDomain 0/0/0 (45)
14:51:58.038718 IP localhost.36879 > localhost.domain: 52853+ PTR? 
3.2.0.10.in-addr.arpa. (39)
14:51:58.038848 IP localhost.domain > localhost.55365: 49842 NXDomain 0/0/0 (45)
14:51:58.039125 IP localhost.54202 > localhost.domain: 32902+ A? 
rooturl-trusty.bar.com. (40)
14:51:58.039154 IP localhost.54202 > localhost.domain: 58975+ ? 
rooturl-trusty.bar.com. (40)
14:51:58.039189 IP milhouse.45718 > OpenWrt.xx.net.domain: 196+ PTR? 
3.2.0.10.in-addr.arpa. (39)
14:51:58.039436 IP localhost.domain > localhost.54202: 32902 0/0/0 (40)
14:51:58.039606 IP localhost.domain > localhost.54202: 58975 0/0/0 (40)
14:51:58.039828 IP localhost.39909 > localhost.domain: 14117+ A? 
rooturl-trusty. (32)
14:51:58.039856 IP localhost.39909 > localhost.domain: 64237+ ? 
rooturl-trusty. (32)
14:51:58.041042 IP OpenWrt.xx.net.domain > milhouse.45718: 196 NXDomain* 
0/0/0 (39)
14:51:58.137739 IP localhost.domain > localhost.36879: 52853 0/0/0 (39)
14:51:58.138622 IP localhost.37396 > localhost.domain: 9267+ PTR? 
15.2.0.10.in-addr.arpa. (40)
14:51:58.139344 IP milhouse.44398 > OpenWrt.xx.net.domain: 32522+ PTR? 
15.2.0.10.in-addr.arpa. (40)
14:51:58.141103 IP OpenWrt.xx.net.domain > milhouse.44398: 32522 NXDomain* 
0/0/0 (40)
14:51:58.386028 IP localhost.domain > localhost.37396: 9267 0/0/0 (40)
14:51:58.633518 IP localhost.domain > localhost.39909: 14117 ServFail 0/0/0 (32)
14:52:03.043476 IP localhost.39909 > localhost.domain: 14117+ A? 
rooturl-trusty. (32)
14:52:03.043544 IP localhost.39909 > localhost.domain: 64237+ ? 
rooturl-trusty. (32)
14:52:03.634060 IP localhost.domain > localhost.39909: 14117 ServFail 0/0/0 (32)


## in the guest at the time of the above, doing a tcpdump shows
# tcpdump -i any udp port 53
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on any, link-type LINUX_SLL (Linux cooked), capture size 262144 bytes
19:51:58.039452 IP 10.0.2.15.35832 > 10.0.2.3.domain: 49842+ ? 
rooturl-trusty.mydomain.com. (45)
19:51:58.040165 IP 10.0.2.15.36362 > 10.0.2.3.domain: 52853+ PTR? 
3.2.0.10.in-addr.arpa. (39)
19:51:58.040220 IP 10.0.2.3.domain > 10.0.2.15.35832: 36012 NXDomain 0/0/0 (45)
19:51:58.040469 IP 10.0.2.3.domain > 10.0.2.15.35832: 49842 NXDomain 0/0/0 (45)
19:51:58.040594 IP 10.0.2.15.55332 > 10.0.2.3.domain: 32902+ A? 
rooturl-trusty.bar.com. (40)
19:51:58.040607 IP 10.0.2.15.55332 > 10.0.2.3.domain: 58975+ ? 
rooturl-trusty.bar.com. (40)
19:51:58.041062 IP 10.0.2.3.domain > 10.0.2.15.55332: 32902 0/0/0 (40)
19:51:58.635241 IP 10.0.2.3.domain > 10.0.2.15.47518: 14117 ServFail 0/0/0 (32)
19:52:03.044813 IP 10.0.2.15.47518 > 10.0.2.3.domain: 14117+ A? rooturl-trusty. 
(32)
19:52:03.044835 IP 10.0.2.15.47518 > 10.0.2.3.domain: 64237+ ? 
rooturl-trusty. (32)
19:52:03.636299 IP 10.0.2.3.domain > 10.0.2.15.47518: 14117 ServFail 0/0/0 (32)


== Using no local dns on host ==
## guest
$ 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
nameserver 10.0.2.3
search mydomain.com bar.com

ubuntu@rooturl-trusty$ time sudo /bin/true
sudo: unable to resolve host rooturl-trusty

$ time sudo /bin/true
real0m0.157s
user0m0.012s
sys 0m0.003s


## host 
$ grep "^[^#]" /etc/resolv.conf
nameserver 8.8.8.8
search mydomain.net lan

$ sudo tcpdump -i any udp port 53
13:55:38.185879 IP milhouse.50417 > google-public-dns-a.google.com.domain: 
19445+ A? rooturl-trusty.mydomain.com. (45)
13:55:38.185909 IP milhouse.50417 > google-public-dns-a.google.com.domain: 
63478+ ? rooturl-trusty.mydomain.com. (45)
13:55:38.228029 IP google-public-dns-a.google.com.domain > milhouse.50417: 
19445 NXDomain 0/1/0 (96)
13:55:38.234909 IP google-public-dns-a.google.com.domain > milhouse.50417: 
63478 NXDomain 0/1/0 (96)
13:55:38.235643 IP milhouse.33309 > google-public-dns-a.google.com.domain: 
22952+ A? rooturl-trusty.bar.com. (40)
13:55:38.235686 IP milhouse.33309 > google-public-dns-a.google.com.domain: 
35430+ ? rooturl-trusty.bar.com. (40)

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

Public bug reported:

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


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

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

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

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

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

Status in systemd package in Ubuntu:
  New

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

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

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

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

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

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

[Touch-packages] [Bug 1641284] Re: libatk-adaptor breaks down the LibreOffice TexMaths extension

2017-11-07 Thread Paul Gevers

I forwarded the bug to Debian.

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

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

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

Title:
  libatk-adaptor breaks down the LibreOffice TexMaths extension

Status in at-spi2-atk package in Ubuntu:
  Confirmed
Status in at-spi2-atk package in Debian:
  Unknown

Bug description:
  Package: libatk-adaptor 2.18.1-2ubuntu1
  System: Ubuntu 16.04.1 LTS (Xenial Xerus)

  If the package libatk-adaptor is installed on Ubuntu (as a depency of
  gnome-orca for example), it breaks down the LibreOffice TexMaths
  extension. TexMaths is a popular extension used to enter / edit LaTeX
  equations on LibreOffice (see http://roland65.free.fr/texmaths).

  Step to reproduce the bug:

  1. It is assumed that LibreOffice 5.1.4 (with at least the Writer and
  Draw components) is installed on Ubuntu. It is also assumed that
  libatk-adaptor is installed.

  2. Install texlive:
  sudo apt-get install texlive

  3. Download and install the TexMaths extension (version 0.42) from
  there: https://sourceforge.net/projects/texmaths/files/0.42/

  4. Create a new empty Writer document, then click on the Pi icon (this
  is the TexMaths icon) and in the window that opens, type: 'x(t)+y(t)'
  (without the quotes), then click on the LaTeX button. This generates
  an SVG image of the 'x(t)+y(t)' equation.

  5. Select the SVG image of the equation by left clicking on it. Then
  click on the Pi icon. Now, instead of editing the equation, an error
  message is displayed: "The selected object is not a TexMaths
  equation... Please unselect it and call the macro again...".

  6. Now, right click on the SVG image and select the 'Description' menu
  voice. In the window that opens, the description is empty and does not
  contain the equation text, as it should.

  7. Now purge (and not just remove) the libatk-adaptor package:

  sudo apt-get purge libatk-adaptor

  then logout and login and repeat the steps 4, 5, and 6: everything is
  OK and the equation can be edited as usual.

  Another way to remove the bug instead of purging libatk-adaptor is to
  rename the file: /etc/X11/Xsession.d/90atk-adaptor to
  /etc/X11/Xsession.d/90atk-adaptor.orig . Then logout and login.

  Note there is another bug #1584795 that relates libatk-adaptor and
  LibreOffice, see there https://bugs.launchpad.net/ubuntu/+source/at-
  spi2-atk/+bug/1584795

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/at-spi2-atk/+bug/1641284/+subscriptions

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

[Touch-packages] [Bug 1730736] [NEW] ubuntu-bug claims systemd is not an official package

Public bug reported:

I have just used 'env -i' to avoid the gtk dialog.
The same occurs when using gtk.

I can't file a bug against systemd because it complains:
   This is not an official Ubuntu package. Please remove any third party 
package and try again.

Other packages work (i tried 'cloud-initramfs-rooturl' for one).
(also note, i used 'ubuntu-bug' to file *this* bug, so  not all packages are 
borked).


$ apt-cache policy systemd
systemd:
  Installed: 234-2ubuntu12.1
  Candidate: 234-2ubuntu12.1
  Version table:
 *** 234-2ubuntu12.1 100
100 /var/lib/dpkg/status
 234-2ubuntu12 500
500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

$ dpkg-query --show systemd
systemd 234-2ubuntu12.1


$ env -i HOME=$HOME ubuntu-bug systemd

*** Collecting problem information

The collected information can be sent to the developers to improve the
application. This might take a few minutes.
.ERROR: hook /usr/share/apport/package-hooks/systemd.py crashed:
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/apport/report.py", line 198, in _run_hook
symb['add_info'](report, ui)
TypeError: add_info() takes 1 positional argument but 2 were given

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/apport/report.py", line 203, in _run_hook
symb['add_info'](report)
  File "/usr/share/apport/package-hooks/systemd.py", line 11, in add_info
apport.hookutils.attach_hardware(report)
  File "/usr/lib/python3/dist-packages/apport/hookutils.py", line 265, in 
attach_hardware
attach_dmi(report)
  File "/usr/lib/python3/dist-packages/apport/hookutils.py", line 221, in 
attach_dmi
value = fd.read().strip()
  File "/usr/lib/python3.6/encodings/ascii.py", line 26, in decode
return codecs.ascii_decode(input, self.errors)[0]
UnicodeDecodeError: 'ascii' codec can't decode byte 0xff in position 0: ordinal 
not in range(128)

*** Problem in systemd

The problem cannot be reported:

This is not an official Ubuntu package. Please remove any third party
package and try again.

Press any key to continue...
No pending crash reports. Try --help for more information.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: apport 2.20.7-0ubuntu3.1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportLog:

ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CrashReports: 640:1000:116:17662:2017-10-31 09:46:03.727057218 -0400:2017-10-31 
09:46:04.727057218 -0400:/var/crash/_usr_bin_tox.1000.crash
CurrentDesktop: ubuntu:GNOME
Date: Tue Nov  7 14:22:04 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-07-23 (838 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: apport
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic third-party-packages wayland-session

** Description changed:

  I have just used 'env -i' to avoid the gtk dialog.
  The same occurs when using gtk.
  
  I can't file a bug against systemd because it complains:
-This is not an official Ubuntu package. Please remove any third party 
package and try again.
+    This is not an official Ubuntu package. Please remove any third party 
package and try again.
  
  Other packages work (i tried 'cloud-initramfs-rooturl' for one).
+ (also note, i used 'ubuntu-bug' to file *this* bug, so  not all packages are 
borked).
+ 
+ 
+ $ apt-cache policy systemd
+ systemd:
+   Installed: 234-2ubuntu12.1
+   Candidate: 234-2ubuntu12.1
+   Version table:
+  *** 234-2ubuntu12.1 100
+ 100 /var/lib/dpkg/status
+  234-2ubuntu12 500
+ 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
+ 
+ $ dpkg-query --show systemd
+ systemd   234-2ubuntu12.1
+ 
+ 
  
  $ env -i HOME=$HOME ubuntu-bug systemd
  
  *** Collecting problem information
  
  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.
  .ERROR: hook /usr/share/apport/package-hooks/systemd.py crashed:
  Traceback (most recent call last):
-   File "/usr/lib/python3/dist-packages/apport/report.py", line 198, in 
_run_hook
- symb['add_info'](report, ui)
+   File "/usr/lib/python3/dist-packages/apport/report.py", line 198, in 
_run_hook
+ symb['add_info'](report, ui)
  TypeError: add_info() takes 1 positional argument but 2 were given
  
  During handling of the above exception, another exception occurred:
  
  Traceback (most recent call last):
-   File "/usr/lib/python3/dist-packages/apport/report.py", line 203, in 
_run_hook
- symb['add_info'](report)

[Touch-packages] [Bug 1650634] Re: when installing systemd, it creates /run/nologin preventing all users from logging in.

2017-11-07 Thread Mikhail N

Thank you, today my Ubuntu 16.04 booted into the maintenance mode and systemctl 
--failed showed only nfs-resolvd.service. I made
# systemctl restart ssh
then I got:
"System is booting up. See pam_nologin(8)"
Authentication failed.

# rm -fv /run/nologin
solved the issue.

I ran 
# apt install --reinstall systemd
and /run/nologin did not appear again.

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

Title:
  when installing systemd, it creates /run/nologin preventing all users
  from logging in.

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

Bug description:
  How to replicate:

  sudo apt-get install systemd

  wait for 5 minutes

  check to see if /run/nologin appears. If it does the bug is present.
  See https://ubuntuforums.org/showthread.php?t=2327330

  I ran this command via ansible on all of my servers. Then I could no
  longer log into any of them. Pretty big bug in my opinion. Please fix.

  -Tim

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: systemd 204-5ubuntu20.20
  ProcVersionSignature: Ubuntu 3.13.0-105.152-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-105-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Fri Dec 16 12:03:55 2016
  InstallationDate: Installed on 2014-04-21 (970 days ago)
  InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.1)
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1728421] Re: Update gtk+3.0 to 3.22.25

I have been using gtk 3.22.25-0ubuntu0.1 for several days on Ubuntu
17.10 and haven't noticed any regressions. The Adwaita, Ambiance and
HighContrast themes look as expected.

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

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

Title:
  Update gtk+3.0 to 3.22.25

Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Artful:
  Fix Committed

Bug description:
  Impact
  ==
  There is a new gtk3 release, 3.22.25.

  Highlights
  --
  * Allows dropping these cherry-picked patches:
    - 0001-Adwaita-Fix-typo-.backgrounf-.background.patch
    - 0002-theme-Fix-Adwaita-headerbars.patch
   - 0003-display-x11-Unset-tiled-state-if-_GTK_EDGE_CONSTRAIN.patch
  * Fixes crash with GNOME Online Accounts (LP: #1720400)
  * Fixes menu forwarding over SSH (LP: #1700319)
  * Fixes log spam about cursor when running gnome-terminal on Wayland (LP: 
#1681910)
  * Support KDE SSD (server-side decorations) handling on Wayland
  * Restores middle-click to do the opposite of primary (usually left-) click 
in scrollbars, GTKRange
  * Some theme fixes for the gtk3 High Contrast theme
  * Allow more key buttons in the GNOME Settings > Keyboard panel to be 
translatable
  * A fix to not show duplicate printers in some cases
  * Improves the GNOME 3.26 tiling feature for GNOME Terminal

  For more changes since 3.22.24, see
  https://git.gnome.org/browse/gtk+/log?h=gtk-3-22
  https://git.gnome.org/browse/gtk+/tree/NEWS?h=gtk-3-22

  Test Case
  =
  Install the update. Run a variety of apps in the default Ubuntu install with 
the Ambiance theme.

  Also check that the Adwaita and High Contrast themes still look ok. You can 
change the theme with the GNOME Tweaks app (gnome-tweak-tool). For the window 
buttons to look as designed, you should change the icon theme to Adwaita when 
you set the theme to Adwaita or High Contrast. Afterwards, you can reset your 
theme back to the defaults with
  gsettings reset org.gnome.desktop.interface gtk-theme
  gsettings reset org.gnome.desktop.interface icon-theme

  Regression Potential
  
  Quite a few changes, but mostly it's bug fixes.

  Earlier gtk3 releases had some regressions (that's why we had those
  cherry-picked patches), but that was mostly related to the late GNOME
  3.26 tiling feature that was rushed in. This release does not have any
  major new features like that.

  Unfortunately, very few people run gtk3 from git master so regressions
  often aren't seen until distros start shipping the gtk3 update.

  The GNOME stack has an SRU Micro-release exception
  https://wiki.ubuntu.com/StableReleaseUpdates#GNOME

  We haven't done micro-release SRUs for gtk3.22 yet. This might be a
  good trial run to see how well it works before 18.04 LTS. Fedora does
  keep their gtk3 up to date throughout the life of their releases.

  Other Info
  ==
  This update also drops a few old patches that weren't listed in 
debian/patches/series. Sorry about the noise but this makes it a bit cleaner in 
the future.

  0001-Update-the-GDK-Mir-backend-to-fix-a-few-problems.patch
  0001-Improve-external-drives-detection.patch
  0002-fix-other-locations-with-glib-249.patch
  0003-use-null-for-generic-marshallers.patch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1728421/+subscriptions

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

[Touch-packages] [Bug 1719043] Re: Gnome web urlbar very slow to show typed input

I verify that the address bar works correctly now after upgrading Ubuntu
17.10 to mutter 3.26.2-0ubuntu0.1.

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

** Changed in: mutter (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 gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1719043

Title:
  Gnome web urlbar very slow to show typed input

Status in GTK+:
  Confirmed
Status in epiphany-browser package in Ubuntu:
  Triaged
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Artful:
  Fix Released
Status in mutter source package in Artful:
  Fix Committed
Status in gtk+3.0 package in Debian:
  Fix Released

Bug description:
  Impact
  ==
  It is very difficult to use the address bar in Epiphany on GNOME on Wayland 
because after a few characters, the address bar field stops redrawing. (This 
apparently was triggered by mutter 3.26?)

  Test Case
  =
  sudo apt install epiphany-browser
  Open the Web app
  Type a URL into the address bar. Type a lng URL.
  You should see all the characters you type into the address bar.

  Regression Potential
  ===
  To fix this issue, an optimization commit applied earlier in 3.26 development 
was reverted. This fix is part of mutter 3.26.2 (LP: #1730097).

  Other Info
  ==
  The first SRU gtk+3.0 3.22.24-0ubuntu2 caused a regression seen in totem and 
so was reverted in both gtk upstream and in the next SRU 3.22.25-0ubuntu0.1

  Instead, this is being fixed in mutter.

  Original Bug Report
  ===
  First two characters typed in urlbar show immediately, other characters take 
up to 30 seconds to appear, or url will appear in full once enter key is 
pressed.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: epiphany-browser 3.26.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 22 18:42:19 2017
  InstallationDate: Installed on 2017-09-22 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: epiphany-browser
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1720400] Re: /usr/bin/gnome-control-center:11:update_buffers:image_get_buffers:intel_update_image_buffers:intel_update_renderbuffers:intel_prepare_render

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

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

Title:
  /usr/bin/gnome-control-
  
center:11:update_buffers:image_get_buffers:intel_update_image_buffers:intel_update_renderbuffers:intel_prepare_render

Status in GTK+:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  In Progress
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Artful:
  Fix Committed

Bug description:
  Impact
  ==
  On artful every time gnome-control-center (goa panel) is used to add a google 
account, gnome-control-center crashes. This is one of the most reported crashes 
after the release.

  Test Case
  =
  - Open gnome-control-center
  - Go to online-account panel
  - Add a Google online account.
  - gnome-control-center should not crash while adding a google online account.

  Regression Potential
  ===
  This is a minimal patch applied upstream:
  https://git.gnome.org/browse/gtk+/commit/?h=gtk-3-22=1c3aff510

  Check if closing a gtk window/dialog creates no artifacts both on xorg
  and on wayland.

  Original Bug Report
  ===
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-control-center.  This problem was most recently seen with package version 
1:3.26.0-0ubuntu3, the problem page at 
https://errors.ubuntu.com/problem/f738a467f5d04cbf9ac6cf7554a28bd064e4091a 
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/gtk/+bug/1720400/+subscriptions

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

[Touch-packages] [Bug 1251178] Re: qdbus and qdbusviewer crash with "No such file or directory"

2017-11-07 Thread David Baumann

Same problem on Ubuntu 17.10, I think it's a bug.

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

Title:
  qdbus and qdbusviewer crash with "No such file or directory"

Status in qt4-x11 package in Ubuntu:
  Confirmed
Status in qtchooser package in Ubuntu:
  Confirmed

Bug description:
  Release: Ubuntu 13.10 (32-bit)

  Package versions:
  qtdbus 4:4.8.4+dfsg-0ubuntu18
  qtchooser 26-3ubuntu2

  Expected behavior:

  The `qdbus` program runs, as does the related program `qdbusviewer`.

  Actual behavior:

  If I run the `qdbus` program, it always crashes:

  user@host:~$ qdbus --help
  qdbus: could not exec '/usr/lib/i386-linux-gnu/qt5/bin/qdbus': No such file 
or directory

  The `qdbus` executable is actually:

  user@host:~$ ls --full-time $(which qdbus)
  lrwxrwxrwx 1 root root 9 2013-08-07 14:48:40.0 + /usr/bin/qdbus 
-> qtchooser

  Note that `/usr/lib/i386-linux-gnu/qt4/bin/qdbus` exists and seems to
  work if I invoke it directly.

  There's a `qdbus-qt5` package in the universe repository. It was not
  pulled in as a dependency, but manually installing it fixes the issue.
  Therefore it's either a packaging error or a bug in qtchooser.

  A similar thing happens if I run `qdbusviewer`:

  user@host:~$ qdbusviewer
  qdbusviewer: could not exec '/usr/lib/i386-linux-gnu/qt5/bin/qdbusviewer': No 
such file or directory

  except that installing `qdbus-qt5` doesn't fix the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: qdbus 4:4.8.4+dfsg-0ubuntu18
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic i686
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: i386
  Date: Thu Nov 14 09:34:24 2013
  MarkForUpload: True
  SourcePackage: qt4-x11
  UpgradeStatus: Upgraded to saucy on 2013-10-23 (22 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/1251178/+subscriptions

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

[Touch-packages] [Bug 1730723] [NEW] firefox crashes/locks up

2017-11-07 Thread Frederick Mann

Public bug reported:

This happens when I click on the Firefox icon.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-38-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Tue Nov  7 13:20:00 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 NVIDIA Corporation C61 [GeForce 6150SE nForce 430] [10de:03d0] (rev a2) 
(prog-if 00 [VGA controller])
   Subsystem: Elitegroup Computer Systems C61 [GeForce 6150SE nForce 430] 
[1019:2609]
InstallationDate: Installed on 2017-11-05 (2 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
Lsusb:
 Bus 001 Device 003: ID 148f:3071 Ralink Technology, Corp. RT3071 Wireless 
Adapter
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 002: ID 045e:00d1 Microsoft Corp. Optical Mouse with Tilt Wheel
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: PCCHIPS A15G
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-38-generic 
root=UUID=8c847f1e-0587-4040-ae7a-cf58a16b7a71 ro
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/24/2008
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG
dmi.board.name: A15G
dmi.board.vendor: PCCHIPS
dmi.board.version: 2.0
dmi.chassis.asset.tag: Unknow
dmi.chassis.type: 3
dmi.chassis.vendor: PCCHIPS
dmi.chassis.version: Unknow
dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd09/24/2008:svnPCCHIPS:pnA15G:pvr2.0:rvnPCCHIPS:rnA15G:rvr2.0:cvnPCCHIPS:ct3:cvrUnknow:
dmi.product.name: A15G
dmi.product.version: 2.0
dmi.sys.vendor: PCCHIPS
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Tue Nov  7 13:04:28 2017
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputMicrosoft Microsoft Optical Mouse with Tilt Wheel MOUSE, id 8
 inputAT Translated Set 2 keyboard KEYBOARD, id 9
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.3-1ubuntu1~16.04.4
xserver.video_driver: nouveau

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial

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

Title:
  firefox crashes/locks up

Status in xorg package in Ubuntu:
  New

Bug description:
  This happens when I click on the Firefox icon.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue Nov  7 13:20:00 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation C61 [GeForce 6150SE nForce 430] [10de:03d0] (rev a2) 
(prog-if 00 [VGA controller])
 Subsystem: Elitegroup Computer Systems C61 [GeForce 6150SE nForce 430] 
[1019:2609]
  InstallationDate: Installed on 2017-11-05 (2 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 001 Device 003: ID 148f:3071 Ralink Technology, Corp. RT3071 Wireless 
Adapter
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 045e:00d1 Microsoft Corp. Optical Mouse with Tilt 
Wheel
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation

[Touch-packages] [Bug 1681910] Re: gnome-terminal constantly logs "Unable to load blank_cursor from the cursor theme" under gnome/wayland

I can no longer duplicate this bug with 3.22.25-0ubuntu0.1 on Ubuntu
17.10.

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

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

Title:
  gnome-terminal constantly logs "Unable to load blank_cursor from the
  cursor theme" under gnome/wayland

Status in GTK+:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Artful:
  Fix Committed

Bug description:
  Impact
  ==
  The systemd journal gets full of useless messages about "Unable to load 
blank_cursor from the cursor theme" when using GNOME Terminal in Wayland on 
Ubuntu 17.10. Ubuntu 17.10 uses Wayland by default when the hardware supports 
it.

  Test Case
  =
  1.Install the gtk3 updates to Ubuntu 17.10.
  2. Log out then log into "Ubuntu" or "GNOME" on a computer that supports 
Wayland.
  3. Open the default terminal app.
  4. Verify that you are running Wayland by running this command. If there is 
output, you are running Wayland.

   env | grep -i wayland

  5. Run this command to check for the useless messages from gnome-
  terminal:

  journalctl -f

  Regression Potential
  ===
  This fix is part of the gtk3 3.22.25 update (LP: #1728421) and seems unlikely 
to cause problems.

  https://git.gnome.org/browse/gtk+/commit/?h=gtk-3-22=fc741adbb

  Original Bug Report
  ===
  Under GNOME/Wayland, regardless of cursor theme (I'm using 'DMZ-White', but 
confirmed with 'Adwaita'), whenever the terminal obtains focus and the user 
starts entering input, gnome-terminal will generate two log entries:

  Apr 11 13:39:22 localhost gnome-terminal-[28979]: Unable to load blank_cursor 
from the cursor theme
  Apr 11 13:39:22 localhost gnome-terminal-[28979]: Unable to load blank_cursor 
from the cursor theme

  This seems to be:
  https://bugzilla.redhat.com/show_bug.cgi?id=1417490

  and related to:
  https://bugzilla.gnome.org/show_bug.cgi?id=775217

  (though in Ubuntu 17.04 the log doesn't contain 'gdkcursor-
  wayland.c:170' like in the gnome bug.

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

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

[Touch-packages] [Bug 1690485] Re: openssh-server SIGSYS with 'UsePrivilegeSeparation sandbox'

2017-11-07 Thread Kevin Kenny

Not trying to pester, but bumping this in case you didn't see that I
posted the requested file.

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

Title:
  openssh-server SIGSYS with 'UsePrivilegeSeparation sandbox'

Status in openssh package in Ubuntu:
  New

Bug description:
  The 'sshd' process gets 'authentication failure' and refuses to allow
  any login.

  dmesg indicates that the problem is SIGSYS on a call to 'socket'
  (syscall #41, signal #31).

  On a hunch, I decided to test whether the problem is related to
  'seccomp' and changed /etc/ssh/sshd_config from the default

  # UsePrivilegeSeparation sandbox

  to the former standard value

  UsePrivilegeSeparation yes

  and logins started to work again.

  Obviously, I'd like to have the additional protection that sandboxing
  would give me.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: openssh-server 1:7.4p1-10
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri May 12 21:06:20 2017
  InstallationDate: Installed on 2017-04-08 (35 days ago)
  InstallationMedia:
   
  SourcePackage: openssh
  UpgradeStatus: Upgraded to zesty on 2017-04-24 (19 days ago)

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

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

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

** Also affects: resolvconf (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

** Changed in: resolvconf (Ubuntu Trusty)
   Importance: Undecided => Medium

** Changed in: resolvconf (Ubuntu Trusty)
   Importance: Medium => High

** Description changed:

  === Begin SRU Template ===
  [Impact]
  Without this fix applied, dns settings provided to the dhcp response
  in the initramfs are not reflected in the "real root".
  
  Thus dns resolution does not work. Of most interest was the MAAS use
- case of the 'root=http://<>/squashfs' use case.  MAAS 2.3 uses this for
- the installation environment and also the rescue environment.
+ case of the 'root=http://<>/squashfs' use case.
+ 
+ MAAS 2.3 uses this for the installation environment and also the rescue
+ environment.  In most cases the 14.04 specific fix will only apply
+ to installation as 16.04 is most likely to be used in rescue mode.
  
  [Test Case]
  There are two tests for this.
  
  a.) local/non-MAAS test
  Download the test case attached.
  Run it and follow the instructions.
  Login to the guest (ubuntu:password), and inspect /etc/resolv.conf
  without the fix there would be no data in /etc/resolv.conf.  With the
  fix you should see 'nameserver 10.0.2.2' and 'search mydomain.com bar.com'
  
  b.) MAAS test.
  For the full maas test, you need to build a image stream for maas
  with the fix included in the squashfs image and then import that
  stream to maas and use the rescue environment and verify dns.
  This process is beyond the scope of the SRU template, but is
  described partially in
    
http://bazaar.launchpad.net/~maas-images-maintainers/maas-images/maas-ephemerals/view/head:/README
  
  [Regression Potential]
  Regression potential should be very low.  There are gates in the code
  to make sure that this code is inactive other than when it is explicitly
  enabled.
  
  net-interface-handler will exit without doing anything unless:
  a.) there exist files /run/net-$INTERFACE.conf or /run/net6-$INTERFACE.conf
  and these files have non-empty values for a variable mentioned above.
  (These files are written by the initramfs code when 'ip=' is seen).
  
  b.) this is not a container.
+   trusty uses 'running-in-container' to determine this.
+   xenial uses 'systemd-detect-virt'
  
  c.) there is no OPENISCSI_MARKER file (/run/initramfs/open-iscsi.interface)
  if open-iscsi has written this file due to open-iscsi root, then it
  will handle this functionality. resolvconf will get out of the way.
  
  d.) /proc/cmdline contains cloud-config-url=* or 'rc-initrd-dns'
  This lowers the scope of changes in runtime to cases with where either the
  new flag is seen or cloud-config-url is passed. The MAAS use case will
  contain this flag.
  
  [Other Info]
  
  === End SRU Template ===
  
  Using MAAS 2.3, during commissioning (and likely in the rest of the
  ephemeral environment) we have noticed that resolv.conf is not set with
  the DNS server.
  
  That said, during the commissioning process, MAAS does not send any
  metadata to cloud-init to configure the network, rather, we expect the
  image to boot from the network via DHCP. So, cloud-init writes:
  
  ubuntu@manual:~$ cat /etc/network/interfaces.d/50-cloud-init.cfg
  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  auto lo
  iface lo inet loopback
  
  # control-manual ens3
  iface ens3 inet dhcp
  broadcast 192.168.122.255
  dns-nameservers 192.168.122.2
  gateway 192.168.122.1
  netmask 255.255.255.0
  
  Which correctly includes the DNS server. However:
  
  ubuntu@manual:~$ ping google.com
  ping: unknown host google.com
  
  If restart the interfacE:
  
  ubuntu@manual:~$ sudo ifdown ens3 && sudo ifup ens3
  ifdown: interface ens3 not configured
  Internet Systems Consortium DHCP Client 4.3.3
  Copyright 2004-2015 Internet Systems Consortium.
  All rights reserved.
  For info, please visit https://www.isc.org/software/dhcp/
  
  Listening on LPF/ens3/52:54:00:ea:57:31
  Sending on   LPF/ens3/52:54:00:ea:57:31
  Sending on   Socket/fallback
  DHCPDISCOVER on ens3 to 255.255.255.255 port 67 interval 3 (xid=0x14eb0354)
  DHCPDISCOVER on ens3 to 255.255.255.255 port 67 interval 4 (xid=0x14eb0354)
  DHCPREQUEST of 192.168.122.195 on ens3 to 255.255.255.255 port 67 
(xid=0x5403eb14)
  DHCPOFFER of 192.168.122.195 from 192.168.122.2
  DHCPACK of 192.168.122.195 from 192.168.122.2
  Restarting ntp (via systemctl): ntp.service.
  bound to 192.168.122.195 -- renewal in 290 seconds.
  
  ubuntu@manual:~$ cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT

[Touch-packages] [Bug 1673717] Re: rsyslog GnuTLS error -50

2017-11-07 Thread Brian Murray

** Changed in: rsyslog (Ubuntu)
 Assignee: (unassigned) => Brian Murray (brian-murray)

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

Title:
  rsyslog GnuTLS error -50

Status in rsyslog package in Ubuntu:
  Triaged
Status in rsyslog package in Debian:
  New

Bug description:
  Exactly the same as this:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832995

  Error:

  > rsyslogd-2078: unexpected GnuTLS error -50 in nsd_gtls.c:530: The 
  > request is invalid.  [v8.16.0 try http://www.rsyslog.com/e/2078 ]

  Provided patch in https://github.com/rsyslog/rsyslog/issues/732 works.

  Please apply patch or upgrade rsyslog.

  Ubuntu 16.04 AMD64
  Rsyslog 8.16.0-1ubuntu3

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

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

[Touch-packages] [Bug 1730716] [NEW] package libperl5.26 5.26.0-8ubuntu1 failed to install/upgrade: tentative de remplacement de « /usr/share/doc/libperl5.26/changelog.Debian.gz », qui est différent d

2017-11-07 Thread Strahm

Public bug reported:

New install
Thanks

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: libperl5.26 5.26.0-8ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
Date: Tue Nov  7 18:36:32 2017
ErrorMessage: tentative de remplacement de « 
/usr/share/doc/libperl5.26/changelog.Debian.gz », qui est différent d'autres 
instances du paquet libperl5.26:i386
InstallationDate: Installed on 2017-11-07 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5
SourcePackage: perl
Title: package libperl5.26 5.26.0-8ubuntu1 failed to install/upgrade: tentative 
de remplacement de « /usr/share/doc/libperl5.26/changelog.Debian.gz », qui est 
différent d'autres instances du paquet libperl5.26:i386
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package artful

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

Title:
  package libperl5.26 5.26.0-8ubuntu1 failed to install/upgrade:
  tentative de remplacement de «
  /usr/share/doc/libperl5.26/changelog.Debian.gz », qui est différent
  d'autres instances du paquet libperl5.26:i386

Status in perl package in Ubuntu:
  New

Bug description:
  New install
  Thanks

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libperl5.26 5.26.0-8ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  Date: Tue Nov  7 18:36:32 2017
  ErrorMessage: tentative de remplacement de « 
/usr/share/doc/libperl5.26/changelog.Debian.gz », qui est différent d'autres 
instances du paquet libperl5.26:i386
  InstallationDate: Installed on 2017-11-07 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5
  SourcePackage: perl
  Title: package libperl5.26 5.26.0-8ubuntu1 failed to install/upgrade: 
tentative de remplacement de « /usr/share/doc/libperl5.26/changelog.Debian.gz 
», qui est différent d'autres instances du paquet libperl5.26:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1730696] Re: * buffer overflow detected *: find terminated

2017-11-07 Thread C de-Avillez

correcting package. /usr/bin/find belong to the findutils package.

** Package changed: coreutils (Ubuntu) => findutils (Ubuntu)

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

Title:
  *** buffer overflow detected ***: find terminated

Status in findutils package in Ubuntu:
  Confirmed

Bug description:
  When running find with -printf "%T+ %p\n"

  The -printf "%T+ %p\n" worked in previous versions. This is a new bug
  in 17.10.

  ```
  > find .  -printf "%A+ %p\n"
  *** buffer overflow detected ***: find terminated
  Aborted (core dumped)
  ```

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

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

[Touch-packages] [Bug 1730696] Re: * buffer overflow detected *: find terminated

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

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

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

Title:
  *** buffer overflow detected ***: find terminated

Status in coreutils package in Ubuntu:
  Confirmed

Bug description:
  When running find with -printf "%T+ %p\n"

  The -printf "%T+ %p\n" worked in previous versions. This is a new bug
  in 17.10.

  ```
  > find .  -printf "%A+ %p\n"
  *** buffer overflow detected ***: find terminated
  Aborted (core dumped)
  ```

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

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

[Touch-packages] [Bug 1713313] Re: Unable to launch pkexec'ed applications on Wayland session

2017-11-07 Thread Dave Steele

https://bugs.launchpad.net/ubuntu/+source/sirikali/+bug/1713313/comments/24

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

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

Title:
  Unable to launch pkexec'ed applications on Wayland session

Status in Back In Time:
  Fix Released
Status in Boot-Info:
  Fix Committed
Status in Boot-Repair:
  Fix Committed
Status in GNOME Terminal:
  New
Status in OS-Uninstaller:
  Fix Committed
Status in apport package in Ubuntu:
  New
Status in apt-offline package in Ubuntu:
  New
Status in backintime package in Ubuntu:
  Confirmed
Status in budgie-welcome package in Ubuntu:
  Invalid
Status in caja-admin package in Ubuntu:
  New
Status in cinnamon package in Ubuntu:
  Invalid
Status in ettercap package in Ubuntu:
  Confirmed
Status in gdebi package in Ubuntu:
  Confirmed
Status in gnunet-gtk package in Ubuntu:
  Confirmed
Status in gparted package in Ubuntu:
  Invalid
Status in gui-ufw package in Ubuntu:
  Confirmed
Status in guidedog package in Ubuntu:
  New
Status in hplip package in Ubuntu:
  Confirmed
Status in italc package in Ubuntu:
  New
Status in laptop-mode-tools package in Ubuntu:
  New
Status in lightdm-gtk-greeter-settings package in Ubuntu:
  Confirmed
Status in nautilus-admin package in Ubuntu:
  New
Status in needrestart-session package in Ubuntu:
  Confirmed
Status in nemo package in Ubuntu:
  Confirmed
Status in policykit-1 package in Ubuntu:
  Invalid
Status in scanmem package in Ubuntu:
  New
Status in scap-workbench package in Ubuntu:
  Confirmed
Status in sirikali package in Ubuntu:
  Fix Released
Status in synaptic package in Ubuntu:
  Confirmed
Status in thunar package in Ubuntu:
  New
Status in tuned package in Ubuntu:
  New
Status in ubuntustudio-controls package in Ubuntu:
  New
Status in ubuntustudio-default-settings package in Ubuntu:
  Invalid
Status in update-notifier package in Ubuntu:
  New
Status in xdiagnose package in Ubuntu:
  Confirmed
Status in xubuntu-default-settings package in Ubuntu:
  Invalid
Status in zulucrypt package in Ubuntu:
  Fix Released

Bug description:
  *
  Main upstream discussion & fixes example to deal with wayland:
  https://bugzilla.gnome.org/show_bug.cgi?id=776437
  *

  


  Steps to reproduce:
  1. Install Ubuntu 17.10
  2. Install backintime-qt4 or gparted application from above list (full may be 
acquired from 
https://codesearch.debian.net/search?q=pkexec+filetype%3Adesktop+path%3A*%2Fapplications%2F*=1=4
 )
  3a. Try to launch backintime-qt4 from shortcut "Back In Time (root)" (located 
in /usr/share/applications/backintime-qt4-root.desktop, it uses pkexec
  ($ cat /usr/share/applications/backintime-qt4-root.desktop | grep Exec
  Exec=pkexec backintime-qt4)
  3b. Try to launch Gparted from shortcut "GParted" (located in 
/usr/share/applications/gparted.desktop, it uses gparted-pkexec)
  4a.1. Back In Time does not start from GUI.
  4a.2. Back In Time shows error message in console:
  4b. gparted-pkexec does not start, reports error
  $ gparted-pkexec
  Created symlink /run/systemd/system/-.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-1000.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-121.mount → /dev/null.
  Created symlink /run/systemd/system/tmp.mount → /dev/null.
  No protocol specified

  (gpartedbin:12831): Gtk-WARNING **: cannot open display: :0
  Removed /run/systemd/system/-.mount.
  Removed /run/systemd/system/run-user-1000.mount.
  Removed /run/systemd/system/run-user-121.mount.
  Removed /run/systemd/system/tmp.mount.

  $ pkexec backintime-qt4

  Back In Time
  Version: 1.1.12

  Back In Time comes with ABSOLUTELY NO WARRANTY.
  This is free software, and you are welcome to redistribute it
  under certain conditions; type `backintime --license' for details.

  No protocol specified
  app.py: cannot connect to X server :0

  Expected results:
  * backintime-qt4 may be run as root

  Actual results:
  * unable to run backintime-qt4 as root

  Workaround:
  * setting "xhost +si:localuser:root" helps.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: backintime-qt4 1.1.12-2
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic i686
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Sun Aug 27 14:23:14 2017
  InstallationDate: Installed on 2017-08-26 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170826)
  PackageArchitecture: all
  SourcePackage: backintime
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:

[Touch-packages] [Bug 1730696] [NEW] * buffer overflow detected *: find terminated

2017-11-07 Thread Jay R. Wren

Public bug reported:

When running find with -printf "%T+ %p\n"

The -printf "%T+ %p\n" worked in previous versions. This is a new bug in
17.10.

```
> find .  -printf "%A+ %p\n"
*** buffer overflow detected ***: find terminated
Aborted (core dumped)
```

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

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

Title:
  *** buffer overflow detected ***: find terminated

Status in coreutils package in Ubuntu:
  New

Bug description:
  When running find with -printf "%T+ %p\n"

  The -printf "%T+ %p\n" worked in previous versions. This is a new bug
  in 17.10.

  ```
  > find .  -printf "%A+ %p\n"
  *** buffer overflow detected ***: find terminated
  Aborted (core dumped)
  ```

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

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

[Touch-packages] [Bug 349469] Re: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable

2017-11-07 Thread Steve Langasek

** Changed in: aptdaemon (Ubuntu)
   Status: Fix Released => Incomplete

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

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

Title:
  debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by
  another process: Resource temporarily unavailable

Status in Aptdaemon:
  Fix Released
Status in Debconf:
  New
Status in aptdaemon package in Ubuntu:
  Incomplete
Status in debconf package in Ubuntu:
  Triaged

Bug description:
  Upgrading packages that use debconf sometimes fail with the following
  error:

  debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by
  another process: Resource temporarily unavailable

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

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

[Touch-packages] [Bug 1719043] Re: Gnome web urlbar very slow to show typed input

2017-11-07 Thread Łukasz Zemczak

Hello Andrew, or anyone else affected,

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

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

** Changed in: mutter (Ubuntu Artful)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-artful

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

Title:
  Gnome web urlbar very slow to show typed input

Status in GTK+:
  Confirmed
Status in epiphany-browser package in Ubuntu:
  Triaged
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Committed
Status in gtk+3.0 source package in Artful:
  Fix Released
Status in mutter source package in Artful:
  Fix Committed
Status in gtk+3.0 package in Debian:
  Fix Released

Bug description:
  Impact
  ==
  It is very difficult to use the address bar in Epiphany on GNOME on Wayland 
because after a few characters, the address bar field stops redrawing. (This 
apparently was triggered by mutter 3.26?)

  Test Case
  =
  sudo apt install epiphany-browser
  Open the Web app
  Type a URL into the address bar. Type a lng URL.
  You should see all the characters you type into the address bar.

  Regression Potential
  ===
  To fix this issue, an optimization commit applied earlier in 3.26 development 
was reverted. This fix is part of mutter 3.26.2 (LP: #1730097).

  Other Info
  ==
  The first SRU gtk+3.0 3.22.24-0ubuntu2 caused a regression seen in totem and 
so was reverted in both gtk upstream and in the next SRU 3.22.25-0ubuntu0.1

  Instead, this is being fixed in mutter.

  Original Bug Report
  ===
  First two characters typed in urlbar show immediately, other characters take 
up to 30 seconds to appear, or url will appear in full once enter key is 
pressed.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: epiphany-browser 3.26.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 22 18:42:19 2017
  InstallationDate: Installed on 2017-09-22 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: epiphany-browser
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

2017-11-07 Thread Till Kamppeter

Fixed in CUPS 2.2.6 which is the version used in Bionic.

For a SRU this should be the patch to backport:

https://github.com/apple/cups/commit/c536b6c583abd9ea1b750f15e887b313ed7ad951


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

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

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

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

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

Status in cups package in Ubuntu:
  Fix Released
Status in cups source package in Artful:
  Triaged

Bug description:
  LP ignores the settings defined in ~/cups/lpoptions in artful

  Steps to reproduce:

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

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

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

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

2017-11-07 Thread Andres Rodriguez

** Changed in: maas
   Status: Fix Committed => Fix Released

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

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

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

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

  Thus dns resolution does not work. Of most interest was the MAAS use
  case of the 'root=http://<>/squashfs' use case.  MAAS 2.3 uses this for
  the installation environment and also the rescue environment.

  [Test Case]
  There are two tests for this.

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

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

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

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

  b.) this is not a container.

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

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

  [Other Info]

  === End SRU Template ===

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

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

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

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

  Which correctly includes the DNS server. However:

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

  If restart the interfacE:

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

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

  ubuntu@manual:~$ 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
  nameserver 192.168.122.2
  search maas

  ubuntu@manual:~$ ping google.com
  PING google.com (216.58.192.46) 56(84) bytes of data.
  64 bytes from mia07s46-in-f14.1e100.net (216.58.192.46): icmp_seq=1

[Touch-packages] [Bug 1730625] Re: Dragging and dropping files into MPV doesn't work in Wayland sessions

2017-11-07 Thread Sebastien Bacher

Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue you are reporting is an upstream one and it
would be nice if somebody having it could send the bug to the developers
of the software by following the instructions at
https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please
tell us the number of the upstream bug (or the link), so we can add a
bugwatch that will inform us about its status. Thanks in advance.

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

Title:
  Dragging and dropping files into MPV doesn't work in Wayland sessions

Status in gnome-shell package in Ubuntu:
  New
Status in mpv package in Ubuntu:
  New
Status in wayland package in Ubuntu:
  New

Bug description:
  Dragging and dropping files into MPV doesn't work in Wayland sessions.
  Only Xorg sessions.

  I have no idea right now if this is an MPV, Wayland protocol or Gnome
  Shell issue.

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

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

[Touch-packages] [Bug 349469] Re: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable

2017-11-07 Thread mahdi

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

** Changed in: aptdaemon (Ubuntu)
 Assignee: (unassigned) => mahdi (mnusrat)

** Changed in: aptdaemon
   Status: Confirmed => Fix Released

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

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

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

Title:
  debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by
  another process: Resource temporarily unavailable

Status in Aptdaemon:
  Fix Released
Status in Debconf:
  New
Status in aptdaemon package in Ubuntu:
  Fix Released
Status in debconf package in Ubuntu:
  Fix Released

Bug description:
  Upgrading packages that use debconf sometimes fail with the following
  error:

  debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by
  another process: Resource temporarily unavailable

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

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

[Touch-packages] [Bug 696435] Re: wait-for-root fails to detect nbd root

2017-11-07 Thread Dimitri John Ledkov

https://launchpad.net/ubuntu/+source/linux/4.4.0-100.123


** Changed in: systemd (Ubuntu Xenial)
   Status: Incomplete => 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/696435

Title:
  wait-for-root fails to detect nbd root

Status in linux package in Ubuntu:
  Fix Released
Status in nbd package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed
Status in systemd source package in Xenial:
  Confirmed

Bug description:
  [Impact]
  Kernel does not generate any events when ndb-client connects /dev/nbd0 
devices, therefore it is impossible to monitor/react to the state of /dev/nbd0.

  [Fix]
  Generate change uevent when size of /dev/nbd0 changes

  [Testcase]
  * Start udevadm monitor
  * modprobe nbd
  * use ndb-client to connect something to /dev/nbd0
  * observe that there are change udev events generated on /dev/nbd0 itself

  [Regression Potential]
  There is no change to existing uevents, or their ordering.
  There is now an addition change event which will cause systemd to mark ndb 
devices as ready and trigger appropriate actions

  [Original Bug Report]

  When using an nbd root, wait-for-root blocks for 30 seconds before
  booting continues successfully.

  Using Ubuntu Natty, related packages versions:
  nbd-client 1:2.9.16-6ubuntu1
  initramfs-tools 0.98.1ubuntu9

  The wait-for-root call from /usr/share/initramfs-tools/scripts/local:
   while [ -z "${FSTYPE}" ]; do
    FSTYPE=$(wait-for-root "${ROOT}" ${ROOTDELAY:-30})

    # Run failure hooks, hoping one of them can fix up the system
    # and we can restart the wait loop.  If they all fail, abort
    # and move on to the panic handler and shell.
    if [ -z "${FSTYPE}" ] && ! try_failure_hooks; then
     break
    fi
   done

  I replaced wait-for-root with a sh script that did `set >&2`, here are the 
relevant environment variables at the time wait-for-root was called:
  ROOT='/dev/nbd0'
  ROOTDELAY=''
  ROOTFLAGS=''
  ROOTFSTYPE=''
  nbdroot='192.168.0.1,2011'

  It's probably worth noting that "nbd0: unknown partition table" was
  displayed asynchronously 1-2 seconds after wait-for-root was invoked
  and while it was still waiting. But I tried adding a "sleep 5" as the
  last line of local-top/nbd, so that the nbd message was displayed a
  lot before wait-for-root was called, and it didn't make a difference.
  So I don't think a race condition is involved in this problem.

  Temporarily I'm passing rootdelay=1 in the kernel command line to work
  around the problem.

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

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

[Touch-packages] [Bug 1730498] Re: apt man page doesn't mention a lot of it's options

2017-11-07 Thread selivan

The man page has references to apt-get(8), apt-cache(8), user is
supposed to look for options there. IMHO that's not very obvious.

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

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

Title:
  apt man page doesn't mention a lot of it's options

Status in apt package in Ubuntu:
  Invalid

Bug description:
  Options like --allow-downgrades, --install-recommends and a lot more
  are not listed in man page at all. Only way to guess this options is
  from auto-completion.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.24
  ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12
  Uname: Linux 4.11.0-14-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Nov  6 23:30:45 2017
  InstallationDate: Installed on 2017-07-29 (100 days ago)
  InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

** Description changed:

  [Impact]
  
- A new upstream bugfix release is available.
+ A new upstream bugfix release is available. Release note diff compared
+ to 17.2.2:
  
- FILL
+ "Mesa 17.2.3 is now available.
+ 
+ In this release we have:
+ 
+ The Vulkan drivers ANV and RADV have multiple small fixes.
+ 
+ The EGL code has improved handling of the new wl_dmabuf codepath.
+ 
+ SWR no longer crashes when checking environment variables.
+ 
+ Other gallium drivers have also seen updates - freedreno, nouveau and
+ radeonsi. The gallivm module, used by llvmpipe et al. has gained little
+ endian PPC64 fixes.
+ 
+ The VA and VDPAU state-trackers have seems improvements handling
+ interlaced videos.
+ 
+ We're using python3 compatible constructs which gives us SCons 3.0
+ support."
+ 
+ "Mesa 17.2.4 is now available.
+ 
+ In this release we have:
+ 
+ In Mesa Core we have included a change to prevent KOTOR from breaking
+ when in combination with the ATI fragment shader extension. 
+ Additionally, NIR has also received a correction.
+ 
+ Mesa's state tracker has gotten a patch to avoid leaks in certain
+ situations like when resizing a window.
+ 
+ Intel drivers have received several fixes.  The compiler has gotten a
+ couple, while anv also received one.  i965 got a patch to avoid VA-
+ API, Beignet and other contexts in the system to break when in
+ combination with previous versions of Mesa 17.2.x.
+ 
+ AMD's compiler has received a couple of fixes while radv has also
+ received another couple, including one to avoid a hang due to an
+ overflow on huge textures.
+ 
+ Broadcom's vc4 has corrected a problem when compiling with Android's
+ clang.
+ 
+ clover has also seen fixed a problem compiling after a specific clang
+ revision.
+ 
+ Vulkan's WSI has gotten plugged a memory leak for X11."
+ 
  
  [Test case]
  
+ Test typical use cases on the most common hw/driver combinations:
+ intel/i965
+ nvidia/nouveau
+ radeon/radeonsi
+ 
  [Regression potential]
+ 
+ These releases are tested against compliance, bugfix releases in
+ particular have minimal risk of regressing anything major at least.

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

Title:
  New bugfix release 17.2.4

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

Bug description:
  [Impact]

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

  "Mesa 17.2.3 is now available.

  In this release we have:

  The Vulkan drivers ANV and RADV have multiple small fixes.

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

  SWR no longer crashes when checking environment variables.

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

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

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

  "Mesa 17.2.4 is now available.

  In this release we have:

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

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

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

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

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

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

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

  
  [Test case]

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

  [Regression potential]

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

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

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

[Touch-packages] [Bug 1729012] Re: "gio open /tmp/whatever.mp3" only opens the file (with totem) every other time it is called

2017-11-07 Thread Sebastien Bacher

Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue you are reporting is an upstream one and it
would be nice if somebody having it could send the bug to the developers
of the software by following the instructions at
https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please
tell us the number of the upstream bug (or the link), so we can add a
bugwatch that will inform us about its status. Thanks in advance.

** Changed in: glib2.0 (Ubuntu)
   Importance: Undecided => Low

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

Title:
  "gio open /tmp/whatever.mp3" only opens the file (with totem) every
  other time it is called

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  I run "gio open /tmp/whatever.mp3". It silently does nothing, i.e.,
  the mp3 does not play, and yet exits with status 0. I run exactly the
  same command again. It opens totem to play the mp3. This seems to be
  repeatable: when I run the command repeatedly, it alternatives between
  doing nothing and playing the mp3.

  I've attached two files showing the output of strace when the command
  succeeds and fails. I can't figure out what the heck is going on.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libglib2.0-bin 2.54.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 31 10:32:44 2017
  InstallationDate: Installed on 2017-05-19 (164 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: glib2.0
  UpgradeStatus: Upgraded to artful on 2017-10-20 (10 days ago)

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

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

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

** Summary changed:

- New bugfix release 17.2.3
+ New bugfix release 17.2.4

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

Title:
  New bugfix release 17.2.4

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

Bug description:
  [Impact]

  A new upstream bugfix release is available.

  FILL

  [Test case]

  [Regression potential]

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

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

[Touch-packages] [Bug 1730657] [NEW] systemd don't find userservice- and usertimer-files

2017-11-07 Thread medontlikemusic

Public bug reported:

After an upgrade from Ubuntu 17.04 to 17.10 i have to run “systemctl
--user daemon-reload” after every reboot before the files under
~/.config/systemd/user were recognized by systemd:

xxx@xxx:~$ systemctl --user list-timers --all
0 timers listed.
xxx@xxx:~$ systemctl --user daemon-reload 
xxx@xxx:~$ systemctl --user list-timers --all
NEXT LEFT LAST PASSED UNIT  ACTIVATES
n/a  n/a  n/a  n/amake-borgbackup.timer make-borgbackup.service
n/a  n/a  n/a  n/asyncthing.timer   syncthing.service

2 timers listed.
xxx@xxx:~$ dpkg -l systemd
Gewünscht=Unbekannt/Installieren/R=Entfernen/P=Vollständig Löschen/Halten
| Status=Nicht/Installiert/Config/U=Entpackt/halb konFiguriert/
 Halb installiert/Trigger erWartet/Trigger anhängig
|/ Fehler?=(kein)/R=Neuinstallation notwendig (Status, Fehler: GROSS=schlecht)
||/ Name   Version Architektur  Beschreibung
+++-==-===--=
ii  systemd234-2ubuntu12.1 amd64system and service manager

This user-account has an ecryptfs-encrypted home btw.

Before the upgrade everything works fine.

** 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/1730657

Title:
  systemd don't find userservice- and usertimer-files

Status in systemd package in Ubuntu:
  New

Bug description:
  After an upgrade from Ubuntu 17.04 to 17.10 i have to run “systemctl
  --user daemon-reload” after every reboot before the files under
  ~/.config/systemd/user were recognized by systemd:

  xxx@xxx:~$ systemctl --user list-timers --all
  0 timers listed.
  xxx@xxx:~$ systemctl --user daemon-reload 
  xxx@xxx:~$ systemctl --user list-timers --all
  NEXT LEFT LAST PASSED UNIT  ACTIVATES
  n/a  n/a  n/a  n/amake-borgbackup.timer make-borgbackup.service
  n/a  n/a  n/a  n/asyncthing.timer   syncthing.service

  2 timers listed.
  xxx@xxx:~$ dpkg -l systemd
  Gewünscht=Unbekannt/Installieren/R=Entfernen/P=Vollständig Löschen/Halten
  | Status=Nicht/Installiert/Config/U=Entpackt/halb konFiguriert/
   Halb installiert/Trigger erWartet/Trigger anhängig
  |/ Fehler?=(kein)/R=Neuinstallation notwendig (Status, Fehler: GROSS=schlecht)
  ||/ Name   Version Architektur  Beschreibung
  
+++-==-===--=
  ii  systemd234-2ubuntu12.1 amd64system and service manager

  This user-account has an ecryptfs-encrypted home btw.

  Before the upgrade everything works fine.

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

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

[Touch-packages] [Bug 1726017] Re: dnsmasq prematurely returns REFUSED, breaking resolver

2017-11-07 Thread ChristianEhrhardt

dns1: 192.168.122.225
dns1: 192.168.122.226
xenial: 192.168.122.222

Setting up as described in c #8

As before things depend on the order, so asking the second mostly fails
while for the first it works mostly. One can use a loop like:

i=0; until dig test.paelzertest1.lan @127.0.0.1 | grep REFUSED; do echo
$((i++)); done

For the name served by 225 this is mostly at ~40 but for 226 more like ~0-6.
Anyway they all fail without the fix at some point.

After installing the fix from proposed I was able to do thousands of requests 
without any issue.
The SERVFAIL case works as well.

** 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 dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1726017

Title:
  dnsmasq prematurely returns REFUSED, breaking resolver

Status in dnsmasq package in Ubuntu:
  Fix Released
Status in dnsmasq source package in Xenial:
  Fix Committed
Status in dnsmasq source package in Zesty:
  Fix Committed

Bug description:
  [Impact]

   * DNS name resolution fails in certain network configurations, where
     different DNS servers are responsible for different domains and one or
     more servers reply REFUSED to queries that regard other domains than
     their own. Without the patch, dnsmasq returns a negative reply to
     if only one such negative answer is received from a forwarder, even
     if other forwarders return valid responses.

     This breaks
     the resolver and practically all internet connectivity, including web
     browsing, email, and receiving updates.

   * This should be backported to stable to fix internet connectivity
     for users.

   * The patch fixes the problem by querying all servers and only returning
     a negative reply to the requestor only if *all* forwarders return negative
     responses.

  [Test Case]

   * It should be possible to test this in a virtual network. One DNS server
     should be responsible for queries to the outside world, and the other one
     could be a DHCP/DNS instance (perhaps dnsmasq, also) that handles internal
     IP addresses and names. It's important that at least one of these servers
     return REFUSED to queries that don't belong into its realm (assuming the
     domain name is "my.net", the server for "my.net" would reply REFUSED to
     "ubuntu.com" and every other domain. I am not sure if this is normally the
     case, all I can say is that my Linux-based ASUS router does it.

     Connect an Ubuntu VM to this network.

     To aggravate the problem, the DHCP server would put the internal DNS
     server first in the nameservers field. If that's the case, the problem
     would also occur if the client used "strict-order" in dnsmasq.conf.

  [Regression Potential]

   * I don't see any. Would there be networks where admins rely upon getting
     NXDOMAIN back if just one server fails for a DNS query? I don't know.

   * [racb] As the behaviour in the area of REFUSED and SERVFAIL is
  being changed, it's probably worth checking during SRU verification
  that dnsmasq correctly passes back successful, REFUSED, SERVFAIL,
  zero-answer and 1+ answer responses in the simple, single upstream DNS
  server case. If there is a regression introduced by these patches, it
  is likely to be in the area of handling SERVFAIL, REFUSED and
  successful replies.

  [Other Info]

  Original bug description follows.

  Seen with dnsmasq 2.75-1ubuntu0.16.04.3, after Trusty->Xenial update.

  In my local network, I have two DNS servers; 192.168.1.1 is the local
  DHCP/DNS server configured to reply to queries inside the local
  network, and 192.168.1.4 is the forwarder in my DSL Router,
  responsible to answer queries about the outside world. THe DHCP server
  returns these in the order 192.168.1.4,192.168.1.1. The internal
  server replies REFUSED to queries about external domains.

  This configuration has worked well with Ubuntu 14.04 and other Linux
  Distros (using Fedora and OpenSUSE internally here), as well as
  various other OSes.

  It does not work with Ubuntu 16.04. NetworkManager's dnsmasq instance
  pushes the REFUSED reply from 192.168.1.1 to applications and ignores
  the successful reply from 2.168.1.4. This causes all DNS queries to
  external servers to fail.

  I believe this is fixed in dnsmasq 2.76 and related to

  http://lists.thekelleys.org.uk/pipermail/dnsmasq-
  discuss/2016q1/010263.html

  
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=68f6312d4bae30b78daafcd6f51dc441b8685b1e
  http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=object;h=4ace25c5d6

  According to these sources, the bug was introduced with
  
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=object;h=51967f9807665dae403f1497b827165c5fa1084b

  In my local setup at least, I can work around the problem by using the
  "strict-order" option to

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

No, just install -ati and provide xorg log and glxinfo dump, otherwise
I've no way to point anything wrong.

Besides, AMD reuses pci id's on several marketing names. For instance
the database on libdrm shows "682B, 87, AMD Radeon (TM) R9 M360". And
the output has nothing to do with performance, it should still work just
the same regardless of what some string somewhere says.

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

Title:
  AMD r7 250 wrong detection

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

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

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

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

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

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

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

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

[Touch-packages] [Bug 1728069] Re: glmark2-es2-wayland hangs

2017-11-07 Thread Alan Griffiths

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

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

Title:
  glmark2-es2-wayland hangs

Status in Mir:
  Triaged
Status in mir package in Ubuntu:
  Fix Committed

Bug description:
  I've seen this in the following benchmarks:

  effects2d hangs (showing cube)
  function  hangs (showing pattern)
  texture   hangs (showing cube)

  It is most easy to reproduce with "texture"

  I've also saw it on "shading" after using --run-forever and leaving it
  for over ten minutes.

  While the test isn't important in itself, this does suggests we may be
  hitting a racy scenario.

  
  Note:

  I've also seen other glmark benchmarks fail in ways that are probably
  unrelated to Mir wayland support:

  ideas   => "Failed to link program" => "Set up failed"
  terrain => "Failed to link program" => segfault

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

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

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

2017-11-07 Thread Dimitri John Ledkov

Public bug reported:

[Impact]

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

[Test Case]

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

[Regression Potential]

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

** Affects: ubuntu-meta (Ubuntu)
 Importance: Undecided
 Status: Fix Committed

** Affects: ubuntu-meta (Ubuntu Xenial)
 Importance: Undecided
 Status: In Progress

** Affects: ubuntu-meta (Ubuntu Zesty)
 Importance: Undecided
 Status: In Progress

** Affects: ubuntu-meta (Ubuntu Artful)
 Importance: Undecided
 Status: In Progress

** Affects: ubuntu-meta (Ubuntu Bionic)
 Importance: Undecided
 Status: Fix Committed

** Also affects: ubuntu-meta (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-meta (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-meta (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-meta (Ubuntu Zesty)
   Importance: Undecided
   Status: New

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

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

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

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

** Changed in: ubuntu-meta (Ubuntu Bionic)
   Status: Confirmed => Fix Committed

** Changed in: ubuntu-meta (Ubuntu Artful)
   Status: Confirmed => In Progress

** Changed in: ubuntu-meta (Ubuntu Zesty)
   Status: Confirmed => In Progress

** Changed in: ubuntu-meta (Ubuntu Xenial)
   Status: Confirmed => In Progress

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

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

Status in ubuntu-meta package in Ubuntu:
  Fix Committed
Status in ubuntu-meta source package in Xenial:
  In Progress
Status in ubuntu-meta source package in Zesty:
  In Progress
Status in ubuntu-meta source package in Artful:
  In Progress
Status in ubuntu-meta source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

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

  [Test Case]

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

  [Regression Potential]

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

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

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

[Touch-packages] [Bug 1728581] Re: "mir_demo_server --help" does not show help text

2017-11-07 Thread Alan Griffiths

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

** Changed in: mir (Ubuntu)
 Assignee: (unassigned) => Alan Griffiths (alan-griffiths)

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

Title:
  "mir_demo_server --help" does not show help text

Status in Mir:
  In Progress
Status in mir package in Ubuntu:
  Fix Committed

Bug description:
  $ mir_demo_server --help

  Expect: help text output to console
  Actual: platforms are listed and program exits

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

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

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

2017-11-07 Thread Maxime Chambonnet

>From the logs linked, what I saw :

Greeter log :
*
** (unity-settings-daemon:1364): WARNING **: Unable to register client: 
GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such method 
'RegisterClient'
[+1,13s] DEBUG: background.vala:121: Render of background 
/usr/share/backgrounds/warty-final-ubuntu.png complete

(nm-applet:1309): GLib-GObject-WARNING **: invalid unclassed pointer in
cast to 'GtkWidget'

(nm-applet:1309): Gtk-CRITICAL **: gtk_widget_show: assertion 'GTK_IS_WIDGET 
(widget)' failed
*

Journal errors :
*
nov. 06 18:33:32 username-X301A1 lightdm[1202]: PAM unable to 
dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object 
file: No such file or directory
nov. 06 18:33:32 username-X301A1 lightdm[1202]: PAM adding faulty module: 
pam_kwallet.so
nov. 06 18:33:32 username-X301A1 lightdm[1202]: PAM unable to 
dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared 
object file: No such file or directory
nov. 06 18:33:32 username-X301A1 lightdm[1202]: PAM adding faulty module: 
pam_kwallet5.so
*

LightDM log :
*
[+0.09s] CRITICAL: session_get_login1_session_id: assertion 'session != NULL' 
failed
*

--> Is it possible to reinstall GTK if that's what's faulty?

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

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

Status in xorg package in Ubuntu:
  New

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

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

  Best regards!

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

[Touch-packages] [Bug 1730639] [NEW] ubuntu-bug does not recognize lzh_TW locale

2017-11-07 Thread Po-Hsu Lin

Public bug reported:

While trying to upload the .crash file for bug 1730554, using command:

$ ubuntu-bug /var/crash/_usr_bin_gnome-shell.1000.crash

The tool crashes with unknown locale error:
ERROR: hook /usr/share/apport/general-hooks/generic.py crashed:
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/apport/report.py", line 198, in _run_hook
symb['add_info'](report, ui)
  File "/usr/share/apport/general-hooks/generic.py", line 48, in add_info
if gtk_like and apport.hookutils.in_session_of_problem(report):
  File "/usr/lib/python3/dist-packages/apport/hookutils.py", line 882, in 
in_session_of_problem
orig_ctime = locale.getlocale(locale.LC_TIME)
  File "/usr/lib/python3.5/locale.py", line 577, in getlocale
return _parse_localename(localename)
  File "/usr/lib/python3.5/locale.py", line 486, in _parse_localename
raise ValueError('unknown locale: %s' % localename)
ValueError: unknown locale: lzh_TW

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: apport 2.20.4-0ubuntu4.5
ProcVersionSignature: Ubuntu 4.10.0-38.42-generic 4.10.17
Uname: Linux 4.10.0-38-generic x86_64
ApportLog:
 ERROR: apport (pid 28299) Tue Nov  7 11:12:04 2017: called for pid 2068, 
signal 11, core limit 0
 ERROR: apport (pid 28299) Tue Nov  7 11:12:04 2017: executable: 
/usr/bin/gnome-shell (command line "/usr/bin/gnome-shell")
 ERROR: apport (pid 28299) Tue Nov  7 11:12:05 2017: debug: session gdbus call: 
(true,)
 
 ERROR: apport (pid 28299) Tue Nov  7 11:13:15 2017: wrote report 
/var/crash/_usr_bin_gnome-shell.1000.crash
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
CrashReports:
 600:111:119:0:2017-11-07 18:35:26.974509633 +0800:2017-11-07 
18:33:17.310366228 +0800:/var/crash/_usr_bin_gnome-shell.1000.uploaded
 640:1000:119:42648617:2017-11-07 18:35:08.738488435 +0800:2017-11-07 
18:35:13.822493362 +0800:/var/crash/_usr_bin_gnome-shell.1000.crash
 640:1000:119:58131:2017-11-07 18:36:03.870557135 +0800:2017-11-07 
18:36:03.870557135 +0800:/var/crash/_usr_share_apport_apport-gtk.1000.crash
 644:1000:119:0:2017-11-07 18:35:24.294506287 +0800:2017-11-07 
18:35:24.294506287 +0800:/var/crash/_usr_bin_gnome-shell.1000.upload
CurrentDesktop: GNOME
Date: Tue Nov  7 18:36:00 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-07-12 (117 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug zesty

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

Title:
  ubuntu-bug does not recognize lzh_TW locale

Status in apport package in Ubuntu:
  New

Bug description:
  While trying to upload the .crash file for bug 1730554, using command:

  $ ubuntu-bug /var/crash/_usr_bin_gnome-shell.1000.crash

  The tool crashes with unknown locale error:
  ERROR: hook /usr/share/apport/general-hooks/generic.py crashed:
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 198, in 
_run_hook
  symb['add_info'](report, ui)
File "/usr/share/apport/general-hooks/generic.py", line 48, in add_info
  if gtk_like and apport.hookutils.in_session_of_problem(report):
File "/usr/lib/python3/dist-packages/apport/hookutils.py", line 882, in 
in_session_of_problem
  orig_ctime = locale.getlocale(locale.LC_TIME)
File "/usr/lib/python3.5/locale.py", line 577, in getlocale
  return _parse_localename(localename)
File "/usr/lib/python3.5/locale.py", line 486, in _parse_localename
  raise ValueError('unknown locale: %s' % localename)
  ValueError: unknown locale: lzh_TW

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: apport 2.20.4-0ubuntu4.5
  ProcVersionSignature: Ubuntu 4.10.0-38.42-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  ApportLog:
   ERROR: apport (pid 28299) Tue Nov  7 11:12:04 2017: called for pid 2068, 
signal 11, core limit 0
   ERROR: apport (pid 28299) Tue Nov  7 11:12:04 2017: executable: 
/usr/bin/gnome-shell (command line "/usr/bin/gnome-shell")
   ERROR: apport (pid 28299) Tue Nov  7 11:12:05 2017: debug: session gdbus 
call: (true,)
   
   ERROR: apport (pid 28299) Tue Nov  7 11:13:15 2017: wrote report 
/var/crash/_usr_bin_gnome-shell.1000.crash
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CrashReports:
   600:111:119:0:2017-11-07 18:35:26.974509633 +0800:2017-11-07 
18:33:17.310366228 +0800:/var/crash/_usr_bin_gnome-shell.1000.uploaded
   640:1000:119:42648617:2017-11-07 18:35:08.738488435 +0800:2017-11-07 
18:35:13.822493362 +0800:/var/crash/_usr_bin_gnome-shell.1000.crash
   640:1000:119:58131:2017-11-07 18:36:03.870557135 +0800:2017-11-07 
18:36:03.870557135

[Touch-packages] [Bug 1730636] [NEW] package liblzma5:i386 5.1.1alpha+20120614-2ubuntu2 failed to install/upgrade: problemas de dependência - deixando desconfigurado

2017-11-07 Thread Andri Alcântara

Public bug reported:

again again

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: liblzma5:i386 5.1.1alpha+20120614-2ubuntu2
ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-38-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Tue Nov  7 08:17:51 2017
Dependencies:
 gcc-6-base 6.0.1-0ubuntu1
 libc6 2.23-0ubuntu9
 libgcc1 1:6.0.1-0ubuntu1
 multiarch-support 2.23-0ubuntu9
ErrorMessage: problemas de dependência - deixando desconfigurado
InstallationDate: Installed on 2017-03-20 (231 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
PackageArchitecture: i386
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: xz-utils
Title: package liblzma5:i386 5.1.1alpha+20120614-2ubuntu2 failed to 
install/upgrade: problemas de dependência - deixando desconfigurado
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: xz-utils (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 xenial

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

Title:
  package liblzma5:i386 5.1.1alpha+20120614-2ubuntu2 failed to
  install/upgrade: problemas de dependência - deixando desconfigurado

Status in xz-utils package in Ubuntu:
  New

Bug description:
  again again

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: liblzma5:i386 5.1.1alpha+20120614-2ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Tue Nov  7 08:17:51 2017
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu9
   libgcc1 1:6.0.1-0ubuntu1
   multiarch-support 2.23-0ubuntu9
  ErrorMessage: problemas de dependência - deixando desconfigurado
  InstallationDate: Installed on 2017-03-20 (231 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: xz-utils
  Title: package liblzma5:i386 5.1.1alpha+20120614-2ubuntu2 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/xz-utils/+bug/1730636/+subscriptions

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

[Touch-packages] [Bug 1730630] [NEW] package linux-image-4.10.0-38-generic 4.10.0-38.42 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2

2017-11-07 Thread James Blandford

Public bug reported:

Updating Ubuntu Gnome 16.04 to 17.04 gives me a serious package error
about "unable to install linux-firmware, linux-image, etc."

Possibly has broke my installation, not sure.

lsb_release -rd returns "Ubuntu 17.04" so I think the upgrade worked but
as this is my work computer I will restart when I have some time just in
case it has broken the install

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: linux-image-4.10.0-38-generic 4.10.0-38.42
ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
Uname: Linux 4.4.0-98-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  james  2185 F pulseaudio
Date: Tue Nov  7 10:04:45 2017
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
HibernationDevice: RESUME=UUID=ad5d2d03-d7f8-4ea6-8607-d6dbaeaa24df
InstallationDate: Installed on 2017-09-11 (56 days ago)
InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
MachineType: LENOVO 20FMS1VA09
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-98-generic 
root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu2.2
SourcePackage: initramfs-tools
Title: package linux-image-4.10.0-38-generic 4.10.0-38.42 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/11/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: R06ET39W (1.13 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20FMS1VA09
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40705 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrR06ET39W(1.13):bd07/11/2016:svnLENOVO:pn20FMS1VA09:pvrThinkPadT460:rvnLENOVO:rn20FMS1VA09:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.name: 20FMS1VA09
dmi.product.version: ThinkPad T460
dmi.sys.vendor: LENOVO

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package zesty

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

Title:
  package linux-image-4.10.0-38-generic 4.10.0-38.42 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 2

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Updating Ubuntu Gnome 16.04 to 17.04 gives me a serious package error
  about "unable to install linux-firmware, linux-image, etc."

  Possibly has broke my installation, not sure.

  lsb_release -rd returns "Ubuntu 17.04" so I think the upgrade worked
  but as this is my work computer I will restart when I have some time
  just in case it has broken the install

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-38-generic 4.10.0-38.42
  ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
  Uname: Linux 4.4.0-98-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  james  2185 F pulseaudio
  Date: Tue Nov  7 10:04:45 2017
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  HibernationDevice: RESUME=UUID=ad5d2d03-d7f8-4ea6-8607-d6dbaeaa24df
  InstallationDate: Installed on 2017-09-11 (56 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  MachineType: LENOVO 20FMS1VA09
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-98-generic 
root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu2.2
  SourcePackage: initramfs-tools
  Title: package linux-image-4.10.0-38-generic 4.10.0-38.42 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/11/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R06ET39W (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FMS1VA09
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias:

[Touch-packages] [Bug 1730630] Re: package linux-image-4.10.0-38-generic 4.10.0-38.42 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2

2017-11-07 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package linux-image-4.10.0-38-generic 4.10.0-38.42 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 2

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Updating Ubuntu Gnome 16.04 to 17.04 gives me a serious package error
  about "unable to install linux-firmware, linux-image, etc."

  Possibly has broke my installation, not sure.

  lsb_release -rd returns "Ubuntu 17.04" so I think the upgrade worked
  but as this is my work computer I will restart when I have some time
  just in case it has broken the install

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-38-generic 4.10.0-38.42
  ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
  Uname: Linux 4.4.0-98-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  james  2185 F pulseaudio
  Date: Tue Nov  7 10:04:45 2017
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  HibernationDevice: RESUME=UUID=ad5d2d03-d7f8-4ea6-8607-d6dbaeaa24df
  InstallationDate: Installed on 2017-09-11 (56 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  MachineType: LENOVO 20FMS1VA09
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-98-generic 
root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu2.2
  SourcePackage: initramfs-tools
  Title: package linux-image-4.10.0-38-generic 4.10.0-38.42 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/11/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R06ET39W (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FMS1VA09
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR06ET39W(1.13):bd07/11/2016:svnLENOVO:pn20FMS1VA09:pvrThinkPadT460:rvnLENOVO:rn20FMS1VA09:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20FMS1VA09
  dmi.product.version: ThinkPad T460
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1730630/+subscriptions

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

[Touch-packages] [Bug 1730419] Re: Audio does not auto-switch to Bluetooth speaker "JBL! GO" when it is turned on

** Summary changed:

- No automatically switch to Bluetooth speaker device
+ Audio does not auto-switch to Bluetooth speaker "JBL! GO" when it is turned on

** Package changed: bluez (Ubuntu) => pulseaudio (Ubuntu)

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

** No longer affects: gnome-bluetooth (Ubuntu)

** Tags added: a2dp

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

Title:
  Audio does not auto-switch to Bluetooth speaker "JBL! GO" when it is
  turned on

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  No automatically switch to Bluetooth speaker device.
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-10-20 (17 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Package: gnome-bluetooth 3.26.1-1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1726017] Re: dnsmasq prematurely returns REFUSED, breaking resolver

2017-11-07 Thread Andy Whitcroft

Hello Martin, or anyone else affected,

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

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

** Changed in: dnsmasq (Ubuntu Xenial)
   Status: In Progress => Fix Committed

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

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

Title:
  dnsmasq prematurely returns REFUSED, breaking resolver

Status in dnsmasq package in Ubuntu:
  Fix Released
Status in dnsmasq source package in Xenial:
  Fix Committed
Status in dnsmasq source package in Zesty:
  Fix Committed

Bug description:
  [Impact]

   * DNS name resolution fails in certain network configurations, where
     different DNS servers are responsible for different domains and one or
     more servers reply REFUSED to queries that regard other domains than
     their own. Without the patch, dnsmasq returns a negative reply to
     if only one such negative answer is received from a forwarder, even
     if other forwarders return valid responses.

     This breaks
     the resolver and practically all internet connectivity, including web
     browsing, email, and receiving updates.

   * This should be backported to stable to fix internet connectivity
     for users.

   * The patch fixes the problem by querying all servers and only returning
     a negative reply to the requestor only if *all* forwarders return negative
     responses.

  [Test Case]

   * It should be possible to test this in a virtual network. One DNS server
     should be responsible for queries to the outside world, and the other one
     could be a DHCP/DNS instance (perhaps dnsmasq, also) that handles internal
     IP addresses and names. It's important that at least one of these servers
     return REFUSED to queries that don't belong into its realm (assuming the
     domain name is "my.net", the server for "my.net" would reply REFUSED to
     "ubuntu.com" and every other domain. I am not sure if this is normally the
     case, all I can say is that my Linux-based ASUS router does it.

     Connect an Ubuntu VM to this network.

     To aggravate the problem, the DHCP server would put the internal DNS
     server first in the nameservers field. If that's the case, the problem
     would also occur if the client used "strict-order" in dnsmasq.conf.

  [Regression Potential]

   * I don't see any. Would there be networks where admins rely upon getting
     NXDOMAIN back if just one server fails for a DNS query? I don't know.

   * [racb] As the behaviour in the area of REFUSED and SERVFAIL is
  being changed, it's probably worth checking during SRU verification
  that dnsmasq correctly passes back successful, REFUSED, SERVFAIL,
  zero-answer and 1+ answer responses in the simple, single upstream DNS
  server case. If there is a regression introduced by these patches, it
  is likely to be in the area of handling SERVFAIL, REFUSED and
  successful replies.

  [Other Info]

  Original bug description follows.

  Seen with dnsmasq 2.75-1ubuntu0.16.04.3, after Trusty->Xenial update.

  In my local network, I have two DNS servers; 192.168.1.1 is the local
  DHCP/DNS server configured to reply to queries inside the local
  network, and 192.168.1.4 is the forwarder in my DSL Router,
  responsible to answer queries about the outside world. THe DHCP server
  returns these in the order 192.168.1.4,192.168.1.1. The internal
  server replies REFUSED to queries about external domains.

  This configuration has worked well with Ubuntu 14.04 and other Linux
  Distros (using Fedora and OpenSUSE internally here), as well as
  various other OSes.

  It does not work with Ubuntu 16.04. NetworkManager's dnsmasq instance
  pushes the REFUSED reply from 192.168.1.1 to applications and ignores
  the successful reply from 2.168.1.4. This causes all DNS queries to
  external servers to fail.

  I believe this is fixed in dnsmasq 2.76 and related to

[Touch-packages] [Bug 1730419] Re: No automatically switch to Bluetooth speaker device

2017-11-07 Thread Dario Figliuzzi

I use a JBL! GO speaker. When I switch on it is synchronized with ubuntu but 
audio stream is still set on laptop speaker.
What I expected: when I switch the JBL on, audio stream is automatically set on 
bluetooth speaker (possibly on High Fidelity quality).

Thank you!

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

Title:
  No automatically switch to Bluetooth speaker device

Status in bluez package in Ubuntu:
  Incomplete
Status in gnome-bluetooth package in Ubuntu:
  Incomplete

Bug description:
  No automatically switch to Bluetooth speaker device.
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-10-20 (17 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Package: gnome-bluetooth 3.26.1-1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1730625] [NEW] Dragging and dropping files into MPV doesn't work in Wayland sessions