date:20160816

[Group.of.nepali.translators] [Bug 1594386] Re: opencryptoki does not create logging directories

2016-08-16 Thread Launchpad Bug Tracker

This bug was fixed in the package opencryptoki - 3.5+dfsg-2

---
opencryptoki (3.5+dfsg-2) unstable; urgency=medium

  * QA upload.
  * Updated systemd-tmpfiles debian/opencryptoki.tmpfiles snippet to
create TOK_OBJ per-token subdirectories with correct
permissions. Upstream should probably ship tmpfiles snippet. LP:
#1595192.
  * Import upstream patches to create/validate lock & lib directories for
all tokens. LP: #1594386

 -- Dimitri John Ledkov   Tue, 16 Aug 2016 09:55:02
+0100

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

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1594386

Title:
  opencryptoki does not create logging directories

Status in Ubuntu on IBM z Systems:
  Triaged
Status in opencryptoki package in Ubuntu:
  Fix Released
Status in opencryptoki source package in Xenial:
  New
Status in opencryptoki source package in Yakkety:
  Fix Released

Bug description:
  == Comment: #0 - Benedikt Klotz  - 2016-06-17 
09:37:07 ==
  The logging directory is not created by opencryptoki by default. This makes 
it difficult to debug opencryptoki errors.

  A patch is at
  
https://sourceforge.net/p/opencryptoki/opencryptoki/ci/8962d298d98df0331d3870e2a490e1781a33a872/

  The patch adds also some more directories (locking and Token object
  directories) when they are missing and adds sanity checks for access
  rights.

  Could you please include this patch into 16.04.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1595192] Re: OpenCryptoki: change group permission to pkcs11 for all /var/lib/opencryptoki token subdirs

2016-08-16 Thread Launchpad Bug Tracker

This bug was fixed in the package opencryptoki - 3.5+dfsg-2

---
opencryptoki (3.5+dfsg-2) unstable; urgency=medium

  * QA upload.
  * Updated systemd-tmpfiles debian/opencryptoki.tmpfiles snippet to
create TOK_OBJ per-token subdirectories with correct
permissions. Upstream should probably ship tmpfiles snippet. LP:
#1595192.
  * Import upstream patches to create/validate lock & lib directories for
all tokens. LP: #1594386

 -- Dimitri John Ledkov   Tue, 16 Aug 2016 09:55:02
+0100

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

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1595192

Title:
  OpenCryptoki: change group permission to pkcs11 for all
  /var/lib/opencryptoki token subdirs

Status in Ubuntu on IBM z Systems:
  Triaged
Status in opencryptoki package in Ubuntu:
  Fix Released
Status in opencryptoki source package in Xenial:
  New
Status in opencryptoki source package in Yakkety:
  Fix Released

Bug description:
  == Comment: #0 - Christian Rund  - 2016-06-20 
06:43:40 ==
  Problem description
  ==
  The ownerships for the token (sub)directories in /var/lib/opencryptoki/ are 
set to root,root in the current version of the 'opencryptoki 
3.4.1+dfsg-1ubuntu3 package'.

  They need to be recursively set to root,pkcs11. Especially the TOK_OBJ
  subdirectories need to have pkcs11 group ownership, as the access
  concept is to permit pkcs11 group members creating persistent token
  objects.

  
  Console output
  ===
  strace output of a failing scenario for testuser uid=1000(testuser) 
gid=1000(testuser) groups=1000(testuser),27(sudo),116(pkcs11) :

  open("/var/lib/opencryptoki/lite/TOK_OBJ/", O_WRONLY|O_CREAT|O_TRUNC, 
0666) = -1 EACCES (Permission denied)
  flock(6, LOCK_UN)   = 0
  write(1, "Error creating key object: 0x6\n", 31Error creating key object: 0x6
  _
  ls -l ls -l /var/lib/
  ...
  drwxrwxr-x 8 root pkcs11 4096 Jun 17 14:29 opencryptoki
  ...
  ls -la /var/lib/opencryptoki/
  root@s8314002:/var/lib/opencryptoki# ll
  total 32
  drwxrwxr-x  8 root pkcs11 4096 Jun 20 12:26 ./
  drwxr-xr-x 40 root root   4096 Jun 20 12:26 ../
  drwxr-xr-x  3 root root   4096 Jun 20 12:26 ccatok/
  drwxr-xr-x  3 root root   4096 Jun 20 12:26 ep11tok/
  drwxr-xr-x  2 root root   4096 Apr 13 22:31 icsf/
  drwxr-xr-x  3 root root   4096 Jun 20 12:26 lite/
  drwxr-xr-x  3 root root   4096 Jun 20 12:26 swtok/
  drwxr-xr-x  2 root root   4096 Apr 13 22:31 tpm/
  _
  The /var/lib/opencryptoki subdirectory structure is provided by the 
opencryptoki package:
   dpkg -L opencryptoki
  /var/lib/opencryptoki/tpm
  /var/lib/opencryptoki/swtok
  /var/lib/opencryptoki/swtok/TOK_OBJ
  /var/lib/opencryptoki/icsf
  /var/lib/opencryptoki/ep11tok
  /var/lib/opencryptoki/ep11tok/TOK_OBJ
  /var/lib/opencryptoki/ccatok
  /var/lib/opencryptoki/ccatok/TOK_OBJ
  /var/lib/opencryptoki/lite
  /var/lib/opencryptoki/lite/TOK_OBJ

  == Comment: #4 - VINEETHA PISHARATH HARI PAI  - 
2016-06-21 11:16:26 ==
  The issue is described in problem description. 

  Please create

  /var/lib/opencryptoki/
  /var/lib/opencryptoki/ where token=ccatok, ep11tok, icsf, lite, swtok, 
tpm
  /var/lib/opencryptoki//TOK_OBJ  with permissions 770,  root ownership 
and pkcs11 group ownership. 

  The directory structure and permissions should look like this 
  :~ # ls -la /var/lib/opencryptoki/
  total 32
  drwxr-xr-x  8 root pkcs11 4096 Jun 13 21:13 .
  drwxr-xr-x 37 root root   4096 Jun 20 21:30 ..
  drwxrwx---  3 root pkcs11 4096 Jun 13 21:13 ccatok
  drwxrwx---  3 root pkcs11 4096 Jun 13 21:13 ep11tok
  drwxrwx---  2 root pkcs11 4096 Sep 23  2014 icsf
  drwxrwx---  3 root pkcs11 4096 Jun 13 21:13 lite
  drwxrwx---  3 root pkcs11 4096 Jun 13 21:13 swtok
  drwxrwx---  3 root pkcs11 4096 Sep 23  2014 tpm

  
  Currently the directories are created with 'root' ownership and group,  
because of which a normal user (who is a member of pkcs11 group) cannot create 
persistent token objects on disk. The rpm spec should be modified to change the 
group and permissions as shown above.

  == Comment: #7 - Heinz-Werner Seeck  - 
2016-06-22 07:09:11 ==
  Canonical please SRU this fix to 16.04. Thx

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   :

[Group.of.nepali.translators] [Bug 1571402] Re: icingaweb2 2.1.0 fails to run with PHP7

2016-08-16 Thread Launchpad Bug Tracker

This bug was fixed in the package icingaweb2 - 2.1.0-1ubuntu1.1

---
icingaweb2 (2.1.0-1ubuntu1.1) xenial; urgency=medium

  * debian/patches/fix_variables_passed_by_reference.patch: PHP7: Fix
Only variables should be passed by reference exception in
Translator.  Closes LP: #1571402.
  * debian/patches/rename_string_to_stringhelper.patch: PHP7: Rename
String to StringHelper.  Closes LP: #1571402.
  * debian/patches/fix_zend_autoload.patch: PHP7: Fix Zend autoload
issues.  Closes LP: #1571402.
  * debian/patches/fix_mysql_postgresql_pdo_checks.patch: PHP7: Fix
MySQL and PostgreSQL PDO extension checks.  Closes LP: #1571402.

 -- Nishanth Aravamudan   Tue, 28 Jun
2016 17:00:23 -0700

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

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1571402

Title:
  icingaweb2 2.1.0 fails to run with PHP7

Status in icingaweb2 package in Ubuntu:
  Fix Released
Status in icingaweb2 source package in Xenial:
  Fix Released

Bug description:
  [Impact]

   * icingaweb2 web interface fails to display, indicating exceptions
  with variables being passed by reference.

   * Upstream icingaweb2 has fixed this via 4 patches in
  https://dev.icinga.org/issues/10251.

  [Test Case]

   * Install icingaweb2 and attempt to navigate to
  http:///icingaweb2. Successful page load is a positive test.

  [Regression Potential]

   * As currently packaged, icingaweb2 is non-functional, so the
  regression potential is low. Additionally, the patches applied are the
  same (with adjustment for context) to those applied upstream to fix
  the same issue.

  https://dev.icinga.org/issues/10251

  Related PHP7 compatibility issues were fixed in version 2.2.0 but
  Xenial ships with 2.1.0. Essentially the software is unusable, setup
  crashes right off the bat with:

  Fatal error: Uncaught ErrorException: Only variables should be passed
  by reference in /usr/share/php/Icinga/Util/Translator.php:259 Stack
  trace: #0 /usr/share/php/Icinga/Util/Translator.php(259):
  Icinga\Application\ApplicationBootstrap->Icinga\Application\{closure}(8,
  'Only variables ...', '/usr/share/php/...', 259, Array) #1 [internal
  function]: Icinga\Util\Translator::Icinga\Util\{closure}(Array, Array)
  #2 /usr/share/php/Icinga/Util/Translator.php(261): usort(Array,
  Object(Closure)) #3 /usr/share/php/Icinga/Application/Web.php(527):
  Icinga\Util\Translator::getPreferredLocaleCode('en-US,en;q=0.8,...')
  #4 /usr/share/php/Icinga/Application/ApplicationBootstrap.php(610):
  Icinga\Application\Web->detectLocale() #5
  /usr/share/php/Icinga/Application/Web.php(92):
  Icinga\Application\ApplicationBootstrap->setupInternationalization()
  #6 /usr/share/php/Icinga/Application/ApplicationBootstrap.php(337):
  Icinga\Application\Web->bootstrap() #7
  /usr/share/php/Icinga/Application/webrouter.php(109):
  Icinga\Application\ApplicationBootstrap: in
  /usr/share/php/Icinga/Util/Translator.php on line 259

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1588246] Re: [SRU] librarian-puppet-simple requires ruby-thor in runtime dependencies

2016-08-16 Thread Brian Murray

librarian-puppet-simple (0.0.5-3) unstable; urgency=medium

  * Added runtime Depends: git (it doesn't work without it).

 -- Thomas Goirand   Tue, 21 Jun 2016 20:44:14 +0200

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

** Changed in: librarian-puppet-simple (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1588246

Title:
  [SRU] librarian-puppet-simple requires ruby-thor in runtime
  dependencies

Status in librarian-puppet-simple package in Ubuntu:
  Fix Released
Status in librarian-puppet-simple source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

  librarian-puppet-simple doesn't work out of the box

  [Test Case]

  How to reproduce:

  Setting up librarian-puppet-simple (0.0.5-1) ...
  Processing triggers for libc-bin (2.23-0ubuntu3) ...
  root@b9b4c58e3998:/tmp/a# librarian-puppet
  /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require': 
cannot load such file -- thor (LoadError)
  from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in 
`require'
  from /usr/bin/librarian-puppet:3:in `'
  root@b9b4c58e3998:/tmp/a# apt-get install ruby-thor
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  The following NEW packages will be installed:
    ruby-thor
  0 upgraded, 1 newly installed, 0 to remove and 9 not upgraded.
  Need to get 43.7 kB of archives.
  After this operation, 219 kB of additional disk space will be used.
  Get:1 http://archive.ubuntu.com/ubuntu xenial/universe amd64 ruby-thor all 
0.19.1-2 [43.7 kB]
  Fetched 43.7 kB in 0s (207 kB/s)
  debconf: delaying package configuration, since apt-utils is not installed
  Selecting previously unselected package ruby-thor.
  (Reading database ... 18492 files and directories currently installed.)
  Preparing to unpack .../ruby-thor_0.19.1-2_all.deb ...
  Unpacking ruby-thor (0.19.1-2) ...
  Setting up ruby-thor (0.19.1-2) ...
  root@b9b4c58e3998:/tmp/a# librarian-puppet
  Commands:
    librarian-puppet clean# clean modules directory
    librarian-puppet compare_repos# compares the specified upstream and 
downstream repos
    librarian-puppet dev_setup# adds development r/w remotes to 
each repo (assumes remote has the same name as current repo)
    librarian-puppet generate_puppetfile  # generates a static version of the 
Puppetfile
    librarian-puppet git_status   # determine the current status of 
checked out git repos
    librarian-puppet help [COMMAND]   # Describe available commands or one 
specific command
    librarian-puppet install  # installs all git sources from your 
Puppetfile
    librarian-puppet update   # updates all git sources from your 
Puppetfile

  Debian should have already updated debian/control for 0.0.5-2 where
  the issue has been fixed.

  [Regression Potential]

  Very little. The fix just adds a new dependency to debian/control.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/librarian-puppet-simple/+bug/1588246/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1591115] Re: Gnome Software catalog entry missing for FlightGear

2016-08-16 Thread Launchpad Bug Tracker

This bug was fixed in the package flightgear - 3.4.0-3ubuntu1

---
flightgear (3.4.0-3ubuntu1) xenial; urgency=medium

  * Fix icon install to fix FlightGear missing from the Software
app. This also improves the resolution of Flightgear's app icon
(LP: #1591115)

 -- Jeremy Bicha   Thu, 28 Jul 2016 23:49:43 -0400

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

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1591115

Title:
  Gnome Software catalog entry missing for FlightGear

Status in flightgear package in Ubuntu:
  Fix Released
Status in flightgear source package in Xenial:
  Fix Released
Status in flightgear package in Debian:
  Fix Released

Bug description:
  Impact
  ==
  The FlightGear package cannot be installed using the Gnome Software 
application.

  Because the app icons were being installed to a non-standard location,
  the .xpm icon was being used instead by the .desktop. That's a low-
  resolution icon and is invalid for appstream.

  This was fixed in Debian and in yakkety by correcting the icon install
  locations and dropping the obsolete .xpm and Debian menu, but for
  xenial a more minimal fix of just correcting the icon install is
  provided in case someone uses the .xpm or Debian menu.

  https://launchpad.net/ubuntu/+source/flightgear/1:2016.2.1+dfsg-6

  Test Case
  =
  1. Open the Software app in Ubuntu 16.04 LTS.
  2. Search for "flight" or "flightgear"
  3. Do you see the FlightGear app?

  Regression Potential
  
  The only thing changed is the icon install locations. They were being 
installed to the top level directory /usr/share/icons/ instead of to the 
standard /usr/share/icons/hicolor/ . A bonus is that the 128x128 high 
resolution app icons are being installed now too.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1570093] Re: multipath-tools update introduced syslog messages about partx

2016-08-16 Thread Launchpad Bug Tracker

This bug was fixed in the package multipath-tools -
0.5.0+git1.656f8865-5ubuntu2.2

---
multipath-tools (0.5.0+git1.656f8865-5ubuntu2.2) xenial; urgency=medium

  * multipath-tools: fix dm- device filtering
   - Allow filtering of DEV_UEVENT dev_type
   - Resolves LP: #1570093

 -- Dragan Stancevic   Thu, 21 Jul 2016
11:16:44 +0200

** Changed in: multipath-tools (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1570093

Title:
  multipath-tools update introduced syslog messages about partx

Status in multipath-tools package in Ubuntu:
  Fix Released
Status in multipath-tools source package in Xenial:
  Fix Released
Status in multipath-tools package in Debian:
  Fix Released

Bug description:
  [Impact]

   * During "service multipath-tools start" /sbin/multipath is
 called on dm- devices that are filtered but due to a condition
 conf->dev_type == DEV_DEVNODE in filtering code multipath
 binary wasn't dropping out when hitting a dm- device. This
 was due to the fact that in this case conf->dev_type is
 set to DEV_UEVENT. It also happens during a fail-over event.

 This is causing the logs to be filled with following
 messages:

 multipath: dm-6: failed to get udev uid: Invalid argument
 multipath: dm-6: failed to get sysfs uid: Invalid argument
 multipath: dm-6: failed to get sgio uid: No such file or directory

   * Fix should be backported to xenial to avoid more support
 issues being filed.

   * This change alows the filtering to happen.

  [Test Case]

   * install multipath-tools, create a basic multipath.conf with
 dm- filtering rule. Run: "service multipath-tools start"
 and check the log

  [Regression Potential]

   * There should be no regression potential with this change, the filtering
 only allows the code to not traverse the error path.

  
  [Original Description]

  During a path loss event, the syslog is showing these messages where
  prior to the recent upgrade to multipath-tools I didn't see anything
  like this. To me this seems like either a problem or it seems like a
  print message that should go into a different log file.

  Apr 13 11:21:00 ICTM1618S01H4 systemd-udevd[14861]: Process '/usr/bin/partx 
-d --nr 1-1024 /dev/sdam' failed with exit code 1.
  ...
  Apr 13 11:21:00 ICTM1618S01H4 multipath: dm-15: failed to get udev uid: 
Invalid argument
  Apr 13 11:21:00 ICTM1618S01H4 multipath: dm-15: failed to get sysfs uid: 
Invalid argument
  Apr 13 11:21:00 ICTM1618S01H4 multipath: dm-15: failed to get sgio uid: No 
such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: multipath-tools 0.5.0+git1.656f8865-5ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  Date: Wed Apr 13 15:29:36 2016
  SourcePackage: multipath-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1595192] Re: OpenCryptoki: change group permission to pkcs11 for all /var/lib/opencryptoki token subdirs

2016-08-16 Thread Frank Heimes

** No longer affects: opencryptoki

** Changed in: ubuntu-z-systems
   Status: New => Triaged

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1595192

Title:
  OpenCryptoki: change group permission to pkcs11 for all
  /var/lib/opencryptoki token subdirs

Status in Ubuntu on IBM z Systems:
  Triaged
Status in opencryptoki package in Ubuntu:
  In Progress
Status in opencryptoki source package in Xenial:
  New
Status in opencryptoki source package in Yakkety:
  In Progress

Bug description:
  == Comment: #0 - Christian Rund  - 2016-06-20 
06:43:40 ==
  Problem description
  ==
  The ownerships for the token (sub)directories in /var/lib/opencryptoki/ are 
set to root,root in the current version of the 'opencryptoki 
3.4.1+dfsg-1ubuntu3 package'.

  They need to be recursively set to root,pkcs11. Especially the TOK_OBJ
  subdirectories need to have pkcs11 group ownership, as the access
  concept is to permit pkcs11 group members creating persistent token
  objects.

  
  Console output
  ===
  strace output of a failing scenario for testuser uid=1000(testuser) 
gid=1000(testuser) groups=1000(testuser),27(sudo),116(pkcs11) :

  open("/var/lib/opencryptoki/lite/TOK_OBJ/", O_WRONLY|O_CREAT|O_TRUNC, 
0666) = -1 EACCES (Permission denied)
  flock(6, LOCK_UN)   = 0
  write(1, "Error creating key object: 0x6\n", 31Error creating key object: 0x6
  _
  ls -l ls -l /var/lib/
  ...
  drwxrwxr-x 8 root pkcs11 4096 Jun 17 14:29 opencryptoki
  ...
  ls -la /var/lib/opencryptoki/
  root@s8314002:/var/lib/opencryptoki# ll
  total 32
  drwxrwxr-x  8 root pkcs11 4096 Jun 20 12:26 ./
  drwxr-xr-x 40 root root   4096 Jun 20 12:26 ../
  drwxr-xr-x  3 root root   4096 Jun 20 12:26 ccatok/
  drwxr-xr-x  3 root root   4096 Jun 20 12:26 ep11tok/
  drwxr-xr-x  2 root root   4096 Apr 13 22:31 icsf/
  drwxr-xr-x  3 root root   4096 Jun 20 12:26 lite/
  drwxr-xr-x  3 root root   4096 Jun 20 12:26 swtok/
  drwxr-xr-x  2 root root   4096 Apr 13 22:31 tpm/
  _
  The /var/lib/opencryptoki subdirectory structure is provided by the 
opencryptoki package:
   dpkg -L opencryptoki
  /var/lib/opencryptoki/tpm
  /var/lib/opencryptoki/swtok
  /var/lib/opencryptoki/swtok/TOK_OBJ
  /var/lib/opencryptoki/icsf
  /var/lib/opencryptoki/ep11tok
  /var/lib/opencryptoki/ep11tok/TOK_OBJ
  /var/lib/opencryptoki/ccatok
  /var/lib/opencryptoki/ccatok/TOK_OBJ
  /var/lib/opencryptoki/lite
  /var/lib/opencryptoki/lite/TOK_OBJ

  == Comment: #4 - VINEETHA PISHARATH HARI PAI  - 
2016-06-21 11:16:26 ==
  The issue is described in problem description. 

  Please create

  /var/lib/opencryptoki/
  /var/lib/opencryptoki/ where token=ccatok, ep11tok, icsf, lite, swtok, 
tpm
  /var/lib/opencryptoki//TOK_OBJ  with permissions 770,  root ownership 
and pkcs11 group ownership. 

  The directory structure and permissions should look like this 
  :~ # ls -la /var/lib/opencryptoki/
  total 32
  drwxr-xr-x  8 root pkcs11 4096 Jun 13 21:13 .
  drwxr-xr-x 37 root root   4096 Jun 20 21:30 ..
  drwxrwx---  3 root pkcs11 4096 Jun 13 21:13 ccatok
  drwxrwx---  3 root pkcs11 4096 Jun 13 21:13 ep11tok
  drwxrwx---  2 root pkcs11 4096 Sep 23  2014 icsf
  drwxrwx---  3 root pkcs11 4096 Jun 13 21:13 lite
  drwxrwx---  3 root pkcs11 4096 Jun 13 21:13 swtok
  drwxrwx---  3 root pkcs11 4096 Sep 23  2014 tpm

  
  Currently the directories are created with 'root' ownership and group,  
because of which a normal user (who is a member of pkcs11 group) cannot create 
persistent token objects on disk. The rpm spec should be modified to change the 
group and permissions as shown above.

  == Comment: #7 - Heinz-Werner Seeck  - 
2016-06-22 07:09:11 ==
  Canonical please SRU this fix to 16.04. Thx

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1594386] Re: opencryptoki does not create logging directories

2016-08-16 Thread Frank Heimes

** No longer affects: opencryptoki

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1594386

Title:
  opencryptoki does not create logging directories

Status in Ubuntu on IBM z Systems:
  Triaged
Status in opencryptoki package in Ubuntu:
  In Progress
Status in opencryptoki source package in Xenial:
  New
Status in opencryptoki source package in Yakkety:
  In Progress

Bug description:
  == Comment: #0 - Benedikt Klotz  - 2016-06-17 
09:37:07 ==
  The logging directory is not created by opencryptoki by default. This makes 
it difficult to debug opencryptoki errors.

  A patch is at
  
https://sourceforge.net/p/opencryptoki/opencryptoki/ci/8962d298d98df0331d3870e2a490e1781a33a872/

  The patch adds also some more directories (locking and Token object
  directories) when they are missing and adds sanity checks for access
  rights.

  Could you please include this patch into 16.04.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1611855] Re: [SRU] Juju 1.25.6

2016-08-16 Thread Steve Langasek

** Changed in: juju-core (Ubuntu)
   Status: Fix Committed => Invalid

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1611855

Title:
  [SRU] Juju 1.25.6

Status in juju-core package in Ubuntu:
  Invalid
Status in juju-core-1 package in Ubuntu:
  Fix Committed
Status in juju-core source package in Trusty:
  Fix Committed
Status in juju-core-1 source package in Trusty:
  Invalid
Status in juju-core source package in Xenial:
  Invalid
Status in juju-core-1 source package in Xenial:
  Fix Committed

Bug description:
  Juju 1.25.6 is a stable update containing critical bug fixes,
  including MAAS compatibility, for the 1.25 series.

  [SRU Information]

  juju-core has a stable release exception, including for major version
  updates, https://wiki.ubuntu.com/JujuUpdates.

  [Impact]
  This update brings critical fixes and enhancements in comparison to the 
current 1.25.5 release.

  A full list of targeted bugs can be seen against the milestone:

  https://launchpad.net/juju-core/+milestone/1.25.6

  [QA/Testing]
  Juju practices continuous integration and testing of the juju source tree. 
The results for this release can be seen here.

  http://reports.vapour.ws/releases/4134

  In addition, juju has adt test coverage for all supported archs:

  http://autopkgtest.ubuntu.com/packages/j/juju-core/
  http://autopkgtest.ubuntu.com/packages/j/juju-core-1/

  Finally, manual verification and testing of the package has been done
  per https://wiki.ubuntu.com/JujuUpdates

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1595901] Re: Missing dependency on dbus

2016-08-16 Thread Launchpad Bug Tracker

This bug was fixed in the package pacemaker - 1.1.14-2ubuntu1.1

---
pacemaker (1.1.14-2ubuntu1.1) xenial; urgency=medium

  * add missing dependency to dbus (LP: #1595901)

 -- Christian Ehrhardt   Thu, 04 Aug
2016 15:24:08 +0200

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

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1595901

Title:
  Missing dependency on dbus

Status in pacemaker package in Ubuntu:
  Fix Released
Status in pacemaker source package in Xenial:
  Fix Released

Bug description:
  [Impact]

   * Pacemaker can be disfunctional and uninstallable if dbus is not
  around

  [Test Case]

   * lxc launch images:ubuntu/yenial/amd64 xenial-pacemaker-bug1595901
 lxc exec xenial-pacemaker-bug1595901 /bin/bash
 apt-get remove --purge dbus # should not be installed anyway yet
 # for proposed verification enable proposed before the next step
 apt-get install pacemaker # should pull in dbus and work

  [Regression Potential]

   * since this is not a change to source or build of the code the 
 regression potential should be low.

   * if dbus is causing trouble somewhere it will now do so wherever 
 pacemaker is installed, but as reported in the bug pacemaker just 
 requires dbus, so there is no doubt in adding the dependency.

  ---

  
  The systemd unit pacemaker.service depends on dbus.service, but the package 
has no Dependency on the dbus package, so on a system without dbus you get:

  Setting up pacemaker (1.1.14-2ubuntu1) ...
  Installing new version of config file /etc/init.d/pacemaker ...
  insserv: warning: current start runlevel(s) (2 3 4 5) of script `pacemaker' 
overrides LSB defaults (empty).
  insserv: warning: current stop runlevel(s) (0 1 6) of script `pacemaker' 
overrides LSB defaults (empty).
  Failed to start pacemaker.service: Unit dbus.service not found.
  invoke-rc.d: initscript pacemaker, action "start" failed.
  dpkg: error processing package pacemaker (--configure):
   subprocess installed post-installation script returned error exit status 5
  dpkg: dependency problems prevent configuration of pacemaker-cli-utils:
   pacemaker-cli-utils depends on pacemaker | pacemaker-remote; however:
    Package pacemaker is not configured yet.
    Package pacemaker-remote is not installed.

  Cheers
  Wolfgang

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1611855] Re: [SRU] Juju 1.25.6

2016-08-16 Thread Nicholas Skaggs

** Changed in: juju-core-1 (Ubuntu)
   Status: Incomplete => Fix Committed

** Changed in: juju-core (Ubuntu)
   Status: Invalid => Fix Committed

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1611855

Title:
  [SRU] Juju 1.25.6

Status in juju-core package in Ubuntu:
  Fix Committed
Status in juju-core-1 package in Ubuntu:
  Fix Committed
Status in juju-core source package in Trusty:
  Fix Committed
Status in juju-core-1 source package in Trusty:
  Invalid
Status in juju-core source package in Xenial:
  Invalid
Status in juju-core-1 source package in Xenial:
  Fix Committed

Bug description:
  Juju 1.25.6 is a stable update containing critical bug fixes,
  including MAAS compatibility, for the 1.25 series.

  [SRU Information]

  juju-core has a stable release exception, including for major version
  updates, https://wiki.ubuntu.com/JujuUpdates.

  [Impact]
  This update brings critical fixes and enhancements in comparison to the 
current 1.25.5 release.

  A full list of targeted bugs can be seen against the milestone:

  https://launchpad.net/juju-core/+milestone/1.25.6

  [QA/Testing]
  Juju practices continuous integration and testing of the juju source tree. 
The results for this release can be seen here.

  http://reports.vapour.ws/releases/4134

  In addition, juju has adt test coverage for all supported archs:

  http://autopkgtest.ubuntu.com/packages/j/juju-core/
  http://autopkgtest.ubuntu.com/packages/j/juju-core-1/

  Finally, manual verification and testing of the package has been done
  per https://wiki.ubuntu.com/JujuUpdates

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1582374] Re: Log contains unknown mode senw

2016-08-16 Thread Launchpad Bug Tracker

This bug was fixed in the package apparmor - 2.10.95-0ubuntu2.2

---
apparmor (2.10.95-0ubuntu2.2) xenial; urgency=medium

  * r3498-r3499-ignore-net-events-that-look-like-file-events.patch: Prevent an
aa-logprof crash by ignoring file events that contains send *and* receive
in the request mask. This is an improvement to the previous fix that only
addressed events that contained send *or* receive.
(LP: #1577051, LP: #1582374)
- debian/rules: Create a new empty file, needed for the test added by this
  patch, since quilt is unable to do so.

 -- Tyler Hicks   Mon, 01 Aug 2016 18:03:36 -0500

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

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1582374

Title:
  Log contains unknown mode senw

Status in AppArmor:
  Fix Committed
Status in apparmor package in Ubuntu:
  Fix Released
Status in apparmor source package in Xenial:
  Fix Released

Bug description:
  [Impact]

  AppArmor policy developers cannot use aa-logprof without it exiting
  with a traceback on certain denial messages.

  [Test Case]

  $ echo 'type=AVC msg=audit(1463403689.381:267599): apparmor="ALLOWED" \
  operation="file_perm" profile="foo" pid=13215 comm="apache2" \
  laddr=:::192.168.1.100 lport=80 faddr=:::192.168.1.100 fport=45658 \
  family="inet6" sock_type="stream" protocol=6 requested_mask="send" \
  denied_mask="send"' > /tmp/log
  $ mkdir -p /tmp/profiles && printf "profile foo {\n}" > /tmp/profiles/foo
  $ aa-logprof -f /tmp/log -d /tmp/profiles

  Expected output of the last command is:

  Reading log entries from /tmp/log.
  Updating AppArmor profiles in /tmp/profiles.

  [Regression Potential]

  There is little potential for regression. This "hotfix" could result
  in some slight confusion because the problematic denial messages will
  simply be ignored but it allows aa-logprof to do its intended job
  without unexpectedly exiting.

  [Original Report]

  Ref #1243932.  Same title but appears to be different cause.

  Ubuntu 16.04.  Error thrown on 'sudo aa-logprof'

  Python 3.5.1+: /usr/bin/python3
  Mon May 16 20:13:30 2016

  A problem occurred in a Python script.  Here is the sequence of
  function calls leading up to the error, in the order they occurred.

   /usr/sbin/aa-logprof in ()
     42
     43 if profiledir:
     44 apparmor.profile_dir = apparmor.get_full_path(profiledir)
     45 if not os.path.isdir(apparmor.profile_dir):
     46 raise apparmor.AppArmorException("%s is not a 
directory."%profiledir)
     47
     48 apparmor.loadincludes()
     49
     50 apparmor.do_logprof_pass(logmark)
     51
  apparmor = 
  apparmor.do_logprof_pass = 
  logmark = ''

   /usr/lib/python3/dist-packages/apparmor/aa.py in do_logprof_pass(logmark='', 
passno=0, pid={13215: [['unknown_hat', 13215, '/usr/sbin/apache2', 
'null-www.xx.co.uk', 'PERMITTING', 'null-www.xx.co.uk'], 
['path', 13215, 'null-complain-profile', 'null-complain-profile', 'HINT', 
'PERMITTING', {'::r', 'r'}, '/proc/13215/attr/current', '']], 13697: [['path', 
13697, 'null-complain-profile', 'null-complain-profile', 'HINT', 'PERMITTING', 
{'::a', '::w', 'a', 'w'}, '/proc/13697/attr/current', '']]})
   2184 ##repo_cfg = read_config('repository.conf')
   2185 ##if not repo_cfg['repository'].get('enabled', False) or 
repo_cfg['repository]['enabled'] not in ['yes', 'no']:
   2186 ##UI_ask_to_enable_repo()
   2187
   2188 log_reader = apparmor.logparser.ReadLog(pid, logfile, 
existing_profiles, profile_dir, log)
   2189 log = log_reader.read_log(logmark)
   2190 #read_log(logmark)
   2191
   2192 for root in log:
   2193 handle_children('', '', root)
  global log = [[['path', 13697, 'null-complain-profile', 
'null-complain-profile', 'HINT', 'PERMITTING', {'::a', '::w', 'a', 'w'}, 
'/proc/13697/attr/current', '']], [['unknown_hat', 13215, '/usr/sbin/apache2', 
'null-www.po4management.co.uk', 'PERMITTING', 'null-www.xx.co.uk'], 
['path', 13215, 'null-complain-profile', 'null-complain-profile', 'HINT', 
'PERMITTING', {'::r', 'r'}, '/proc/13215/attr/current', '']]]
  log_reader = 
  log_reader.read_log = >
  logmark = ''

   /usr/lib/python3/dist-packages/apparmor/logparser.py in 
read_log(self=, logmark='')
    402 self.add_event_to_tree(event)
    403 except AppArmorException as e:
    404 ex_msg = ('%(msg)s\n\nThis error was caused by the 
log line:\n%(logline)s' %
    405 {'msg': e.value, 'logline': line})
    406 # when py3 only: Drop the original 
AppArmorException by passing None as the parent exception
    407 raise AppArmorBug(ex_msg)  # py3-only: from

[Group.of.nepali.translators] [Bug 1577051] Re: aa-logprof fails with unknown mode "reweive"

2016-08-16 Thread Launchpad Bug Tracker

This bug was fixed in the package apparmor - 2.10.95-0ubuntu2.2

---
apparmor (2.10.95-0ubuntu2.2) xenial; urgency=medium

  * r3498-r3499-ignore-net-events-that-look-like-file-events.patch: Prevent an
aa-logprof crash by ignoring file events that contains send *and* receive
in the request mask. This is an improvement to the previous fix that only
addressed events that contained send *or* receive.
(LP: #1577051, LP: #1582374)
- debian/rules: Create a new empty file, needed for the test added by this
  patch, since quilt is unable to do so.

 -- Tyler Hicks   Mon, 01 Aug 2016 18:03:36 -0500

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

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1577051

Title:
  aa-logprof fails with unknown mode "reweive"

Status in AppArmor:
  Fix Committed
Status in apparmor package in Ubuntu:
  Fix Released
Status in apparmor source package in Xenial:
  Fix Released

Bug description:
  [Impact]

  AppArmor policy developers cannot use aa-logprof without it exiting
  with a traceback on certain denial messages.

  [Test Case]

  $ echo 'Apr 30 21:53:05 nova kernel: [24668.960760] audit: \
  type=1400 audit(1462045985.636:2154): apparmor="DENIED" \
  operation="file_perm" profile="foo" pid=12529 comm="java" \
  laddr=:::127.0.0.1 lport=8080 faddr=:::127.0.0.1 fport=52308 \
  family="inet6" sock_type="stream" ^Cotocol=6 requested_mask="receive"  \
  denied_mask="receive"' > /tmp/log
  $ mkdir -p /tmp/profiles && printf "profile foo {\n}" > /tmp/profiles/foo
  $ aa-logprof -f /tmp/log -d /tmp/profiles

  Expected output of the last command is:

  Reading log entries from /tmp/log.
  Updating AppArmor profiles in /tmp/profiles.

  [Regression Potential]

  There is little potential for regression. This "hotfix" could result
  in some slight confusion because the problematic denial messages will
  simply be ignored but it allows aa-logprof to do its intended job
  without unexpectedly exiting.

  [Original Report]

  Ubuntu 16.04.

  Profiling apache tomcat.

  1) aa-genprof on the catalina.sh script that is used to start and stop tomcat.
  2) Start and stop tomcat.
  3) Scan and save the profile.
  4) aa-complain on the tomcat profile
  5) Start tomcat again and this time also send a http request to tomcat.
  6) Run aa-logprof which fails with this message

  Reading log entries from /var/log/syslog.
  Updating AppArmor profiles in /etc/apparmor.d.
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 402, in 
read_log
  self.add_event_to_tree(event)
    File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 206, in 
add_event_to_tree
  e = self.parse_event_for_tree(e)
    File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 303, in 
parse_event_for_tree
  raise AppArmorException(_('Log contains unknown mode %s') % rmask)
  apparmor.common.AppArmorException: 'Log contains unknown mode reweive'

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
    File "/usr/sbin/aa-logprof", line 50, in 
  apparmor.do_logprof_pass(logmark)
    File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 2189, in 
do_logprof_pass
  log = log_reader.read_log(logmark)
    File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 407, in 
read_log
  raise AppArmorBug(ex_msg)  # py3-only: from None
  apparmor.common.AppArmorBug: Log contains unknown mode reweive

  This error was caused by the log line:
  Apr 30 21:53:05 nova kernel: [24668.960760] audit: type=1400 
audit(1462045985.636:2154): apparmor="ALLOWED" operation="file_perm" 
profile="/usr/local/apache-tomcat-8.0.33/bin/catalina.sh///usr/local/jdk1.8.0_92/bin/java"
 pid=12529 comm="java" laddr=:::127.0.0.1 lport=8080 faddr=:::127.0.0.1 
fport=52308 family="inet6" sock_type="stream" protocol=6 
requested_mask="receive" denied_mask="receive"

  An unexpected error occoured!

  For details, see /tmp/apparmor-bugreport-wj6gamog.txt
  Please consider reporting a bug at https://bugs.launchpad.net/apparmor/
  and attach this file.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1589549] Re: [SRU] htop crashes when setting cpu affinity

2016-08-16 Thread Launchpad Bug Tracker

This bug was fixed in the package htop - 2.0.1-1ubuntu1

---
htop (2.0.1-1ubuntu1) xenial; urgency=medium

  * SRU patch segfault with -fPIE when setting cpu affinity
(LP: #1589549)

 -- Daniel Lange   Tue, 02 Aug 2016 19:28:25 +0200

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

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1589549

Title:
  [SRU] htop crashes when setting cpu affinity

Status in htop package in Ubuntu:
  Fix Released
Status in htop source package in Xenial:
  Fix Released

Bug description:
  [Impact]

   * htop 2.0.1 segfaults drawing a panel on screen when compiled with -fPIE
 (default on Xenial)
   * justification: severe functionality loss for users and easy to trigger
 by accident
   * remedy: apply fix from upstream commit 4758f028

  [Test Case]

   * start htop
   * press key 
   * press key 

  [Regression Potential]

   * two line fix: s/int/size_t/
   * rdeps are freedombox-setup and hollywood

  [Other Info]
   
   * Fixed in htop 2.0.2-1 in Yakkety Yak

  -

  See the resolved Bug: https://github.com/hishamhm/htop/issues/493

  when trying to set the cpu affinity (with "a") htop crashes.
  System: Ubuntu 16.04/amd64

  htop:
    Installed: 2.0.1-1
    Candidate: 2.0.1-1
    Version table:
   *** 2.0.1-1 500
  500 http://at.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1597875] Re: Networking issues with the SmartOS datasource under Xenial

2016-08-16 Thread Scott Moser

i marked this fix-released as the SRU bug brought the initial changes
back to xenial.


** Changed in: cloud-init (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1597875

Title:
  Networking issues with the SmartOS datasource under Xenial

Status in cloud-init:
  Fix Released
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Fix Released

Bug description:
  Under xenial (16.04) on a VM with more than one IP/interface cloud-
  init fails to setup additional IPS. So for instance if I provision and
  VM with two IPs, cloud-init only sets up one IP (which is typcially
  the main/public IP). I believe the underlying issue has to do with
  changes in systemd and how interfaces are now named in the new world.
  Specifically, you can no longer assume "eth" prefixed interface names.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1604007] Re: [SRU] mitaka point releases

2016-08-16 Thread Launchpad Bug Tracker

This bug was fixed in the package aodh - 2.0.2-0ubuntu1

---
aodh (2.0.2-0ubuntu1) xenial; urgency=medium

  [ Corey Bryant ]
  * New upstream version.
  * d/aodh-common.install: Install new aodh-data-migration tool.

  [ David Della Vecchia ]
  * New upstream point release for OpenStack Mitaka (LP: #1604007).

 -- David Della Vecchia   Mon, 18 Jul 2016 09:52:09
-0400

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

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1604007

Title:
  [SRU] mitaka point releases

Status in Ubuntu Cloud Archive:
  Invalid
Status in Ubuntu Cloud Archive mitaka series:
  Fix Committed
Status in aodh package in Ubuntu:
  Fix Released
Status in ceilometer package in Ubuntu:
  Invalid
Status in openstack-trove package in Ubuntu:
  Invalid
Status in aodh source package in Xenial:
  Fix Released
Status in ceilometer source package in Xenial:
  Fix Released
Status in openstack-trove source package in Xenial:
  Fix Committed

Bug description:
  New point releases for misc openstack components for the mitaka
  release:

  aodh 2.0.2
  ceilometer 6.1.3
  trove 5.1.0

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1604007] Re: [SRU] mitaka point releases

2016-08-16 Thread Launchpad Bug Tracker

This bug was fixed in the package ceilometer - 1:6.1.3-0ubuntu1

---
ceilometer (1:6.1.3-0ubuntu1) xenial; urgency=medium

  * New upstream point release for OpenStack Mitaka (LP: #1604007).
  * d/p/fix-fallback-meter-path.patch: Rebased.
  * d/control: Align (build-)depends with upstream.

 -- David Della Vecchia   Thu, 21 Jul 2016 11:34:17
-0400

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

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1604007

Title:
  [SRU] mitaka point releases

Status in Ubuntu Cloud Archive:
  Invalid
Status in Ubuntu Cloud Archive mitaka series:
  Fix Committed
Status in aodh package in Ubuntu:
  Fix Released
Status in ceilometer package in Ubuntu:
  Invalid
Status in openstack-trove package in Ubuntu:
  Invalid
Status in aodh source package in Xenial:
  Fix Committed
Status in ceilometer source package in Xenial:
  Fix Released
Status in openstack-trove source package in Xenial:
  Fix Committed

Bug description:
  New point releases for misc openstack components for the mitaka
  release:

  aodh 2.0.2
  ceilometer 6.1.3
  trove 5.1.0

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1613787] Re: xfrm: ipsec crash when updating spd thresholds

2016-08-16 Thread Joseph Salisbury

I built a Xenial test kernel with the patch from:
http://patchwork.ozlabs.org/patch/654026/

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1613787/

Can you test this kernel and confirm it resolves this bug?

Also, do any other releases besides Xenial and Yakkety require this
patch?

** Also affects: linux (Ubuntu Yakkety)
   Importance: Medium
 Assignee: Joseph Salisbury (jsalisbury)
   Status: In Progress

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1613787

Title:
  xfrm: ipsec crash when updating spd thresholds

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  Fixed upstream by this commit (only in IPsec tree for now):

  
https://git.kernel.org/cgit/linux/kernel/git/klassert/ipsec.git/commit/?id=6916fb3b10b3cbe3b1f9f5b680675f53e4e299eb
  http://patchwork.ozlabs.org/patch/654026/

  To update the thresholds: 'ip xfrm policy set hthresh4 24 32'

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1613787] Re: xfrm: ipsec crash when updating spd thresholds

2016-08-16 Thread Joseph Salisbury

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

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

** Changed in: linux (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: linux (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

** Tags added: patch xenial

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1613787

Title:
  xfrm: ipsec crash when updating spd thresholds

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress

Bug description:
  Fixed upstream by this commit (only in IPsec tree for now):

  
https://git.kernel.org/cgit/linux/kernel/git/klassert/ipsec.git/commit/?id=6916fb3b10b3cbe3b1f9f5b680675f53e4e299eb
  http://patchwork.ozlabs.org/patch/654026/

  To update the thresholds: 'ip xfrm policy set hthresh4 24 32'

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1498059] Re: hwe-support-status should be included in newer releases

2016-08-16 Thread Launchpad Bug Tracker

This bug was fixed in the package update-manager - 1:0.196.19

---
update-manager (1:0.196.19) trusty-proposed; urgency=medium

  * hwe-support-status: utilize a virtualbox metapackage set.  (LP:
#1498059)

 -- Brian Murray   Mon, 15 Aug 2016 11:14:48 -0700

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

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1498059

Title:
  hwe-support-status should be included in newer releases

Status in update-manager package in Ubuntu:
  Fix Released
Status in update-notifier package in Ubuntu:
  Fix Released
Status in update-manager source package in Trusty:
  Fix Released
Status in update-notifier source package in Trusty:
  Fix Released
Status in update-manager source package in Xenial:
  Triaged
Status in update-notifier source package in Xenial:
  Confirmed

Bug description:
  Test Case (for update-notifier)
  ---
  1) Install an End of Life HWE stack (utopic/vivid/wily)
  2) Install the version of update-notifier and update-manager from Trusty 
-proposed
  3) Force an motd update via 'sudo 
/usr/lib/update-notifier/update-motd-hwe-eol'
  4) Observe a message regarding your HWE stack being End of Life.
  5) ssh localhost - confirm same HWE EoL message appears

  
  Right now hwe-support-status is only in 12.04.  14.04 users might want that 
information for their release as well.

  Alternatively the functionality could be merged into ubuntu-support-
  status.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1498059] Re: hwe-support-status should be included in newer releases

2016-08-16 Thread Launchpad Bug Tracker

This bug was fixed in the package update-notifier - 0.154.1ubuntu2

---
update-notifier (0.154.1ubuntu2) trusty-proposed; urgency=medium

  * Add support for the HWE End-of-Life notification via
motd. (LP: #1498059)

 -- Brian Murray   Fri, 05 Aug 2016 15:19:06 -0700

** Changed in: update-notifier (Ubuntu Trusty)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1498059

Title:
  hwe-support-status should be included in newer releases

Status in update-manager package in Ubuntu:
  Fix Released
Status in update-notifier package in Ubuntu:
  Fix Released
Status in update-manager source package in Trusty:
  Fix Committed
Status in update-notifier source package in Trusty:
  Fix Released
Status in update-manager source package in Xenial:
  Triaged
Status in update-notifier source package in Xenial:
  Confirmed

Bug description:
  Test Case (for update-notifier)
  ---
  1) Install an End of Life HWE stack (utopic/vivid/wily)
  2) Install the version of update-notifier and update-manager from Trusty 
-proposed
  3) Force an motd update via 'sudo 
/usr/lib/update-notifier/update-motd-hwe-eol'
  4) Observe a message regarding your HWE stack being End of Life.
  5) ssh localhost - confirm same HWE EoL message appears

  
  Right now hwe-support-status is only in 12.04.  14.04 users might want that 
information for their release as well.

  Alternatively the functionality could be merged into ubuntu-support-
  status.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1610784] Re: cloud-init openstack.py code does not recognize network type 'tap'

2016-08-16 Thread Scott Moser

** Also affects: cloud-init (Ubuntu Xenial)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1610784

Title:
  cloud-init openstack.py code does not recognize network type 'tap'

Status in cloud-init:
  Fix Committed
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  New

Bug description:
  == System info ==
  Xenial 16.04.1, Mitaka, MAAS 2.0 (RC2 currently), JuJu 2.0 (beta7 currently - 
awaiting beta14), 16.07 Charms, neutron-calico-11 (awaiting fix for another 
bug).

  == Config drive link ==

  https://gist.github.com/anonymous/ce20298b9e12e7fe77851552c2a91243

  == Error log ==
  From line 574 in 
https://git.launchpad.net/cloud-init/tree/cloudinit/sources/helpers/openstack.py:

  if link['type'] in ['ethernet', 'vif', 'ovs', 'phy', 'bridge']:

  Jul 28 10:31:38 ubuntu cloud-init[1209]: failed run of stage init-local
  Jul 28 10:31:38 ubuntu cloud-init[1209]: 

  Jul 28 10:31:38 ubuntu cloud-init[1209]: Traceback (most recent call last):
  Jul 28 10:31:38 ubuntu cloud-init[1209]: File 
"/usr/lib/python3/dist-packages/cloudinit/cmd/main.py", line 530, in 
status_wrapper
  Jul 28 10:31:38 ubuntu cloud-init[1209]: ret = functor(name, args)
  Jul 28 10:31:38 ubuntu cloud-init[1209]: File 
"/usr/lib/python3/dist-packages/cloudinit/cmd/main.py", line 277, in main_init
  Jul 28 10:31:38 ubuntu cloud-init[1209]: 
init.apply_network_config(bring_up=bool(mode != sources.DSMODE_LOCAL))
  Jul 28 10:31:38 ubuntu cloud-init[1209]: File 
"/usr/lib/python3/dist-packages/cloudinit/stages.py", line 631, in 
apply_network_config
  Jul 28 10:31:38 ubuntu cloud-init[1209]: netcfg, src = 
self._find_networking_config()
  Jul 28 10:31:38 ubuntu cloud-init[1209]: File 
"/usr/lib/python3/dist-packages/cloudinit/stages.py", line 618, in 
_find_networking_config
  Jul 28 10:31:38 ubuntu cloud-init[1209]: if self.datasource and 
hasattr(self.datasource, 'network_config'):
  Jul 28 10:31:38 ubuntu cloud-init[1209]: File 
"/usr/lib/python3/dist-packages/cloudinit/sources/DataSourceConfigDrive.py", 
line 159, in network_config
  Jul 28 10:31:38 ubuntu cloud-init[1209]: self.network_json, 
known_macs=self.known_macs)
  Jul 28 10:31:38 ubuntu cloud-init[1209]: File 
"/usr/lib/python3/dist-packages/cloudinit/sources/helpers/openstack.py", line 
599, in convert_net_json
  Jul 28 10:31:38 ubuntu cloud-init[1209]: 'Unknown network_data link type: %s' 
% link['type'])
  Jul 28 10:31:38 ubuntu cloud-init[1209]: ValueError: Unknown network_data 
link type: tap
  Jul 28 10:31:38 ubuntu cloud-init[1209]: 


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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1586933] Re: gpu-manager's drm output detection affects boot time

2016-08-16 Thread Launchpad Bug Tracker

This bug was fixed in the package ubuntu-drivers-common - 1:0.4.20

---
ubuntu-drivers-common (1:0.4.20) yakkety; urgency=medium

  * Remove PackageKit plugin. This stopped working with packagekit 1.0 as its
apt backend is gone and aptcc does not support plugins.
  * debian/control: Drop obsolete XS-Testsuite:.
  * Bump Standards-Version to 3.9.8.

 -- Martin Pitt   Tue, 16 Aug 2016 11:46:36
+0200

** Changed in: ubuntu-drivers-common (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1586933

Title:
  gpu-manager's drm output detection affects boot time

Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common source package in Xenial:
  In Progress

Bug description:
  SRU request:

  [Impact]
  The current drm code to probe the connected outputs is too resource 
intensive, and slow down the boot process.

  [Test Case]
  1) Boot Ubuntu and run the following command, looking for gpu-manager:
  systemd-analize blame

  This will show how long gpu-manager took. Write down the number

  2) Install the package from -proposed, and run systemd-analize blame.
  See if the number has become smaller.

  [Regression Potential]
  Low, all the changes are already included in Yakkety.

  
  _
  Rather than calling drm directly, gpu-manager should simply check the outputs 
connector status by using the sysfs filesystem (e.g. 
/sys/class/drm/card0-HDMI-A-1/status, etc.), thus relying on data that is 
already available.

  This should make gpu-manager a bit less resource intensive, especially
  on boot.

  The attached perf shows the problem in gpu-manager.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1591411] Re: systemd-logind must be restarted every ~1000 SSH logins to prevent a ~25 second delay

2016-08-16 Thread Łukasz Zemczak

Ok, with everyone confirming that the systemd patch is not required, I
am closing the systemd part of the bug as 'Invalid' - let's only
concentrate on the dbus part here. That being said, I would not like to
release a new patch for dbus downstream if the patch hasn't been fully
reviewed and approved upstream.

In this case I would propose to wait a bit and see if a finalized patch
will be available.

** Tags removed: patch

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

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

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

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1591411

Title:
  systemd-logind must be restarted every ~1000 SSH logins to prevent a
  ~25 second delay

Status in D-Bus:
  Unknown
Status in dbus package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Released
Status in dbus source package in Xenial:
  Confirmed
Status in systemd source package in Xenial:
  Invalid

Bug description:
  I noticed on a system that accepts large numbers of SSH connections
  that after awhile, SSH sessions were taking ~25 seconds to complete.

  Looking in /var/log/auth.log, systemd-logind starts failing with the
  following:

  Jun 10 23:55:28 test sshd[3666]: pam_unix(sshd:session): session opened for 
user ubuntu by (uid=0)
  Jun 10 23:55:28 test systemd-logind[105]: New session c1052 of user ubuntu.
  Jun 10 23:55:28 test systemd-logind[105]: Failed to abandon session scope: 
Transport endpoint is not connected
  Jun 10 23:55:28 test sshd[3666]: pam_systemd(sshd:session): Failed to create 
session: Message recipient disconnected from message bus without replying

  I reproduced this in an LXD container by doing something like:

  lxc launch ubuntu:x test
  lxc exec test -- login -f ubuntu
  ssh-import-id 

  Then ran a script as follows (passing in ubuntu@):

  while [ 1 ]; do
  (time ssh $1 "echo OK > /dev/null") 2>&1 | grep ^real >> log
  done

  In my case, after 1052 logins, the 1053rd and thereafter were taking
  25+ seconds to complete. Here are some snippets from the log file:

  $ cat log | grep 0m0 | wc -l
  1052

  $ cat log | grep 0m25 | wc -l
  4

  $ tail -5 log
  real  0m0.222s
  real  0m25.232s
  real  0m25.235s
  real  0m25.236s
  real  0m25.239s

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu5
  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
  Date: Sat Jun 11 00:09:34 2016
  MachineType: Notebook W230SS
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf

   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W230SS
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/15/2014:svnNotebook:pnW230SS:pvrNotApplicable:rvnNotebook:rnW230SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.name: W230SS
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1595558] Re: sudo doesn't have /snap/bin in PATH

2016-08-16 Thread Launchpad Bug Tracker

This bug was fixed in the package sudo - 1.8.16-0ubuntu3

---
sudo (1.8.16-0ubuntu3) yakkety; urgency=medium

  * debian/sudoers:
- include /snap/bin in the secure_path (LP: #1595558)

 -- Michael Vogt   Mon, 15 Aug 2016 18:08:34
+0200

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

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1595558

Title:
  sudo doesn't have /snap/bin in PATH

Status in snapd package in Ubuntu:
  Won't Fix
Status in sudo package in Ubuntu:
  Fix Released
Status in snapd source package in Xenial:
  Won't Fix
Status in sudo source package in Xenial:
  New

Bug description:
  [ SRU Justification ]
  Snap may contain sysadmin tools as well. They are currently hard to invoke
  because /snap/bin is not in the PATH when sudo is used because the default
  secure_path of sudoers does not have it.

  [ SRU Test Case ]
  1. sudo snap install hello-world
  2. sudo hello-world
  3. verify that this fails with "command not found"
  4. install sudo from xenial-proposed
  5. verify that sudo hello-world now works

  [ Regression Potential ]
  - may trigger conffile prompts on upgrade

  [Original report]
  $ nextcloud.occ
  # prints output

  $ sudo nextcloud.occ
  sudo: nextcloud.occ: command not found

  I need to do `sudo /snap/bin/nextcloud.occ` if I want it to run.

  $ sudo env | grep PATH
  PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1594386] Re: opencryptoki does not create logging directories

[Group.of.nepali.translators] [Bug 1595192] Re: OpenCryptoki: change group permission to pkcs11 for all /var/lib/opencryptoki token subdirs

[Group.of.nepali.translators] [Bug 1571402] Re: icingaweb2 2.1.0 fails to run with PHP7

[Group.of.nepali.translators] [Bug 1588246] Re: [SRU] librarian-puppet-simple requires ruby-thor in runtime dependencies

[Group.of.nepali.translators] [Bug 1591115] Re: Gnome Software catalog entry missing for FlightGear

[Group.of.nepali.translators] [Bug 1570093] Re: multipath-tools update introduced syslog messages about partx

[Group.of.nepali.translators] [Bug 1595192] Re: OpenCryptoki: change group permission to pkcs11 for all /var/lib/opencryptoki token subdirs

[Group.of.nepali.translators] [Bug 1594386] Re: opencryptoki does not create logging directories

[Group.of.nepali.translators] [Bug 1611855] Re: [SRU] Juju 1.25.6

[Group.of.nepali.translators] [Bug 1595901] Re: Missing dependency on dbus

[Group.of.nepali.translators] [Bug 1611855] Re: [SRU] Juju 1.25.6

[Group.of.nepali.translators] [Bug 1582374] Re: Log contains unknown mode senw

[Group.of.nepali.translators] [Bug 1577051] Re: aa-logprof fails with unknown mode "reweive"

[Group.of.nepali.translators] [Bug 1589549] Re: [SRU] htop crashes when setting cpu affinity

[Group.of.nepali.translators] [Bug 1597875] Re: Networking issues with the SmartOS datasource under Xenial

[Group.of.nepali.translators] [Bug 1604007] Re: [SRU] mitaka point releases

[Group.of.nepali.translators] [Bug 1604007] Re: [SRU] mitaka point releases

[Group.of.nepali.translators] [Bug 1613787] Re: xfrm: ipsec crash when updating spd thresholds

[Group.of.nepali.translators] [Bug 1613787] Re: xfrm: ipsec crash when updating spd thresholds

[Group.of.nepali.translators] [Bug 1498059] Re: hwe-support-status should be included in newer releases

[Group.of.nepali.translators] [Bug 1498059] Re: hwe-support-status should be included in newer releases

[Group.of.nepali.translators] [Bug 1610784] Re: cloud-init openstack.py code does not recognize network type 'tap'

[Group.of.nepali.translators] [Bug 1586933] Re: gpu-manager's drm output detection affects boot time

[Group.of.nepali.translators] [Bug 1591411] Re: systemd-logind must be restarted every ~1000 SSH logins to prevent a ~25 second delay

[Group.of.nepali.translators] [Bug 1595558] Re: sudo doesn't have /snap/bin in PATH

25 matches

Site Navigation

Mail list logo

Footer information